CRAWL TRUST
XML Sitemap lastmod Hygiene for Evidence-Based Agent Review Pages
A conservative change-date policy: publish lastmod only when a comparison, source record, methodology note, or substantive conclusion has actually changed.
What changed
Search Engine Roundtable reported Gary Illyes guidance that unreliable XML sitemap lastmod values can be worse than omitting them. For a technical review site, a date should communicate a real change in evidence, not a deployment or copyright refresh.
Scope note: This is publishing and measurement guidance, not a claim that any one URL will rank or be indexed. The right decision depends on the page’s evidence, query fit, and technical accessibility.
Review-page operating matrix
| Signal | What to inspect | Practical response |
|---|---|---|
| Benchmark revision | Measured result, test condition, or methodology changed | Update lastmod and log the changed metric or protocol. |
| Source evidence change | Issue status, release note, primary source, or citation materially changed | Update lastmod and preserve the prior claim where useful in the changelog. |
| Substantive editorial change | Verdict, limitation, comparison table, or decision guidance changed | Update lastmod with a short human-readable change note. |
| Mechanical publish | Navigation, whitespace, footer year, or deployment-only change | Do not advance lastmod solely for this event. |
Four-step implementation protocol
- Treat lastmod as a claim about meaningful content change, with one source of truth in the publishing workflow.
- Require a page-level change reason before emitting a new date.
- Omit lastmod where the system cannot reliably distinguish editorial changes from mechanical edits.
- Audit a sample of sitemap entries against page changelogs each month and fix any mismatch before it becomes systemic.
Source evidence
Search Engine Roundtable, July 16, 2026
Use the linked report for the underlying industry update. This page translates that signal into a cautious, review-site-specific operating checklist.