How Google Uses Sitemap lastmod
A precise lastmod implementation guide for content, ecommerce, and programmatic pages—without fake freshness signals.
Key takeaways
- lastmod should represent a meaningful change to the indexed page.
- Code deployments, analytics events, and unrelated database writes are not content updates.
- Use one canonical timestamp source per content type.
- Omit lastmod when the source cannot be trusted.
What lastmod communicates
The lastmod element tells a crawler when the page content last changed in a meaningful way. Search engines may use a consistently accurate value when deciding what to recrawl. It is not an instruction and it does not make a page look fresh simply because the date is recent.
Changes that should update the date
Update lastmod when the primary content, structured facts, availability, pricing, documentation, or other information visible to search users changes materially. The exact rule depends on the page type, but it should always map to a user-visible reason to revisit the URL.
- An article receives a substantive correction or new section
- A product's price, availability, or specification changes
- API documentation changes an endpoint or response contract
- A directory profile receives newly collected source data
Changes that should not update the date
Do not update every URL after a deployment, cache purge, analytics event, view count, background job, or unrelated record change. Those events create uniform timestamps that say nothing about individual page freshness.
Choose a trustworthy source
For CMS pages, use the content record's reviewed or updated timestamp. For ecommerce pages, derive a content timestamp from user-visible fields. For data-driven profiles, use the successful data collection time and show that date on the page. Store timestamps in UTC and serialize an ISO 8601 date or datetime.
<url>
<loc>https://example.com/docs/sitemap-api</loc>
<lastmod>2026-07-18T08:30:00Z</lastmod>
</url>Audit lastmod quality
Sample URLs from every sitemap type and compare the XML value with the page's visible update date and source record. Look for impossible future dates, every URL changing together, dates older than the content, and values that change on every request.
If you cannot produce a stable, verifiable value, omit lastmod while you fix the source. Absence creates less noise than a timestamp that routinely misrepresents the page.
Extract URLs and their available lastmod values.
Open the free toolFrequently asked questions
Does a recent lastmod improve ranking?
No. It can help recrawl decisions when accurate, but it does not replace relevance or content quality.
Should a deployment update every lastmod value?
Only if the deployment materially changed every page's user-visible content, which is uncommon. Use page-level content timestamps instead.
Is a date without a time valid?
Yes. ISO 8601 dates such as 2026-07-18 are valid when day-level precision matches the source data.
Primary references
See our technical methodology and editorial policy.