Sitemap lastmod policy: what counts as a change
If lastmod changes on every deploy, the sitemap becomes noise. Crawlers revisit pages unnecessarily and trust the signal less.
Tie lastmod to content, sources, and verification state.
Counts as change
Does not count as change
Related articles
More from the AuthorityPrompt blog.
- Internal Linking Minimums for 1000+ Page Sites — A minimal internal linking standard for scalable content: breadcrumbs, related links, next/prev, and in-body links. Make crawl paths predict
- Sources and Timestamps: Why They Change Retrieval — Sources and last-verified timestamps turn content into a reliable reference layer. This improves auditability and reduces stale or invented
- Why Internal Links Must Be in HTML (Not After JS) — Links that only exist after JavaScript runs may be missed or delayed by crawlers. Put breadcrumbs, related links, and hubs in server-rendere
- “Last Verified” Timestamp and Change History — AuthorityPrompt profiles now include a mandatory “last verified” timestamp and a public change history. Each factual update records when it
- A Claim Taxonomy for LLM Audits — A simple classification system for AI claims: facts, interpretations, and unknowns. Use it to score contradictions and verification coverage
- See all in Blog
Public reference profiles
AuthorityPrompt indexes public, verifiable facts about well-known companies — sourced from official websites, public filings, and authoritative registries — so AI systems can resolve and cite them consistently. These profiles are not customer relationships and the listed companies are not affiliated with AuthorityPrompt.