Part of the Crawling & Indexing series. For the full picture, start with Crawling and indexing: how search engines find your pages, and what stops them.
<lastmod> is the date or time of the last significant update to a page listed in an XML sitemap. It is not the time the sitemap file was rebuilt. A site that stamps every product and article with today’s date after every deployment gives Google no useful way to distinguish changed pages from unchanged ones.
This guide focuses on sitemap lastmod accuracy, not the broader checks for indexability, redirects and orphan URLs in the XML sitemap audit.
When should sitemap lastmod change?
Change it when that page changes significantly. Google’s sitemap documentation gives updates to main content, structured data and links on the page as examples. It says a copyright-date change is not significant. The test is whether the page Google could fetch has materially changed, not whether a database row or deployment timestamp changed.
| Change | Update lastmod? | Why |
|---|---|---|
| Rewrite a guide’s main section | Yes | Search-visible content changed |
| Correct product availability and its markup | Yes | The offer and structured data changed |
| Add substantive links within the page | Usually | Page links are part of its content |
| Rebuild the sitemap with unchanged pages | No | Only the file changed |
| Update a sitewide copyright year | No | Not a meaningful page update |
| Change a hidden internal inventory field | No, unless output changes | The fetched page remains the same |
For a frequently changing catalogue, establish a documented definition of a significant page change and apply it consistently. The exact rule can differ by template, but it should be derived from published content or page output, not simply now() in the sitemap generator.
How do you audit sitemap lastmod at scale?
Sample URLs from each template and compare three things: the sitemap value, the page’s actual published changes and the generator’s source field. This is a timestamp audit, not a claim that a crawler can infer editorial history from HTML alone.
- Export sitemap URLs with their
<lastmod>values. If you have a sitemap index, include every child file; the large sitemap guide covers that inventory. - Group values by template and date. A sudden identical timestamp across thousands of unrelated URLs is a reason to investigate, not automatic proof of an error.
- Pick pages that supposedly changed and compare the live page with a version history, stored content hash, deployment diff or another reliable record.
- Pick pages whose content definitely changed but whose lastmod did not. Missing updates are as important as false updates.
- Trace the wrong values to the CMS field or build step and fix the generator. Recheck a sample on the next release.
The audit should also confirm that the sitemap lists your preferred canonical, indexable URLs. A perfectly accurate timestamp on a redirected or noindex URL does not fix a bad sitemap. Google’s build-a-sitemap guide treats sitemap submission as a hint, not a promise that every URL will be crawled.
What should the generator use as its source of truth?
Use a published-page modification time or another field tied to meaningful page output. If your CMS updates modified_at for every administrative change, derive a separate publication timestamp or compare the fields that affect the rendered page. For static sites, track the last substantive content change per route rather than the latest site build.
The tag accepts a supported date or date-time format. If you provide a time, include its timezone and make sure it is the moment the changed page became public, not a future scheduled edit. Google’s sitemap guidance says it may verify a lastmod against the page, so consistency matters more than precision you cannot defend.
Does an accurate lastmod make Google recrawl faster?
It can provide a useful change signal, but it cannot force a recrawl or indexing. Google says it uses lastmod only when consistently accurate, and its crawling troubleshooting guide warns against expecting every sitemap URL to be crawled immediately. Keep internal links, canonical signals and server responses sound as well.
If an updated URL is not indexed, check its actual crawl and index status rather than changing lastmod repeatedly. The crawling and indexing guide explains those separate stages.
Sitemap lastmod audit checklist
- Lastmod comes from significant published page changes, not sitemap generation time.
- Unchanged pages retain their previous value after a release.
- Main-content, structured-data and meaningful link updates advance the value.
- Sample dates match version history or another reliable record.
- Sitemap URLs are canonical and indexable.
- The generator is fixed when values drift; the XML is not patched by hand.
Frequently asked questions
Does Google use sitemap lastmod?
Google says it uses lastmod when the value is consistently and verifiably accurate. A timestamp alone does not guarantee a recrawl or indexing.
Should lastmod change when the footer changes?
Usually not for a routine copyright or shared-footer update. Google describes meaningful changes to main content, structured data or links on the page as significant examples.
Can every URL have today's lastmod date?
Only if every listed page really changed significantly today. Regenerating an unchanged sitemap is not a page update, so a build timestamp for every URL is misleading.
Do changefreq and priority help instead?
No. Google says it ignores both changefreq and priority in XML sitemaps. Maintain accurate canonical URLs and lastmod values instead.