The 44 controls / TS14
TS14 · Sitemaps and freshness
lastmod reflects a significant change to the page.
Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.
Control rule version : 0.1.0-draft.19
Reading guide: start with applicability and required evidence, then read expectations together with their limitations. Understand C, NC, NT and NA outcomes · Prepare a dossier
Expectations and evidence
- Required inputs (protocol identifiers)
- sitemap, change-history
- When it applies
- Sitemaps containing lastmod.
- How to check
- Compare lastmod with editorial history or a significant content deployment.
- Expectation
- Each tested date maps to a traceable significant change; file generation alone is insufficient.
- Evidence to retain
- ISO 8601 timestamp tied to an actual change, not file generation.
- Non-applicability
- No lastmod declared; its absence is not itself a defect.
- Limitations
- The engine may ignore a lastmod it considers unreliable.
- Outcome clarification
- C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
- Reference scope
- Technical reference; the TSEP acceptance rule remains an editorial proposal.
Atomic rules
This control is documented in the protocol. This version does not yet attach executable atomic rules to it.