TS14Sitemaps and links
Sitemaps and linksDoes lastmod reflect an actual change?
lastmod reflects a significant change to the page.
Prepare evidence
- In the app
- Evidence import
- You provide
- Sitemap and change history
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
One date. A real change.
lastmod reflects a significant change to the page.
According to Google
Google expects the date of the last significant modification, such as main content, structured data or links, rather than a date refreshed with every generation.
Check
The stated date. The actual change.
In TSEP Control
You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.
Your contribution
Define the scope and expectations before collection. Gather the items below and supply the requested reviews.
With your own tools
With your own toolsChoose recently edited pages and unchanged ones. Compare lastmod with CMS or deployment history and check date formatting.
Evidence to retain
ISO 8601 timestamp tied to an actual change, not file generation.
What this result covers
Matching date and supplied review do not prove an actual change or its significance. UTC-day or zoned-instant precision; no complete CMS history, ideal freshness or engine processing inferred.
Act
Fix the calculation. Not just the date.
Tie lastmod to a significant page modification using a valid date.
Recheck
A real change. A date that follows.
After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.
To go further.
Statuses, sources and method.
Understand the statusesC · NC · NT · NA
The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.
- C · Verified
- The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
- NC · To correct
- Tie lastmod to a significant page modification using a valid date.
- NT · Not established
- Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
- NA · Not applicable
- The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.
Sources and references1 reference
Detailed method and rules1 rule
Control method and criteria
Method
Read each native page lastmod; compare its UTC date or zoned instant with an attributed original JSON event, then check the bound significance review.
Acceptance criteria
Each tested date maps to a traceable significant change; file generation alone is insufficient.
Non-applicability
No lastmod declared; its absence is not itself a defect.
Detailed rules
TS14-A01 · lastmod linked to a documented significant change.
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Page entries carrying lastmod in the prior population; supplied-sitemap-lastmod-v1 profile. Index lastmod is outside scope.
Evidence
Dated/fingerprinted XML original, file URL and entry position, original UTF8 JSON event with SHA-256, change_id, URL, changed_at, kind and description; attributed bound review.
Method
Read each native page lastmod; compare its UTC date or zoned instant with an attributed original JSON event, then check the bound significance review.
Acceptance criteria
Pass requires matching nonfuture dates, attributed content event and supported review. Invalid/future date, traceable mismatch, file generation alone or contradicted review fails. Insufficient history/review is inconclusive. Complete native absence of lastmod is an atomic exemption, never a defect.
When the result remains inconclusive
Missing, ambiguous or out-of-profile plan, document, child, binding, capture or review; exceeded bound. Retain every independent fail and other unknowns. Missing timezone or out-of-profile lastmod precision is inconclusive, never a fabricated defect.
Non-applicability
Atomic not-applicable only for absence read from a complete native entry. All-exempt entries produce neither C nor automatic whole-control NA.
Assumptions
Prior plan, literal URLs, supplied window of at most24hours and original integrity. Declared dates, context and judgments, without authentication.
Limitations
Matching date and supplied review do not prove an actual change or its significance. UTC-day or zoned-instant precision; no complete CMS history, ideal freshness or engine processing inferred.
Rule version 0.3.0-draft.1 · Public protocol reference · Versioned source
Put it into practice
The sitemap and change history.