Sitemap lastmod accuracy
The lastmod element in a sitemap reports when a URL's content last changed. Google uses lastmod to prioritize recrawling only when the value is consistently accurate; if every URL shows the generation date or the homepage date, Google learns to distrust and ignore it. This page explains correct lastmod semantics, format, and the consequences of inaccuracy.
What this means
The lastmod element records the date (and optionally time) a URL's content last meaningfully changed, in W3C datetime format (for example a full date, or a date with time and timezone). It is a per-URL freshness signal in the sitemap.
Google has stated it uses lastmod for scheduling recrawls, but only if it trusts the value. Trust comes from consistency: lastmod must correspond to real changes across your sitemap.
How Google uses it and when it is ignored
When lastmod is accurate and consistent, Google can use it to prioritize recrawling recently changed URLs. When it is unreliable, Google ignores it entirely.
Common ways to make it unreliable: stamping every URL with the sitemap generation timestamp, copying the homepage's lastmod to all URLs, or updating lastmod when nothing on the page actually changed (such as a template tweak with no content change). All of these destroy the field's value.
- lastmod = date the content last meaningfully changed
- W3C datetime format (date, or date + time + timezone)
- Accurate and consistent → Google can use it for recrawl scheduling
- Always-today or all-same dates → Google ignores it
Getting it right
Derive lastmod from a real content-modified timestamp in your CMS or data store, not from the moment you generated the sitemap. Only bump it when the page's main content actually changes — not for unrelated boilerplate or analytics tweaks.
Keep the format valid and consistent. If you cannot reliably produce accurate lastmod values, it is better to omit the field than to fill it with misleading dates that lead Google to discount your sitemap's freshness signal.
How it appears in analytics and logs
An accurate lastmod helps Google decide which URLs to recrawl sooner. An inaccurate lastmod — the same date everywhere, or always today — gives no useful signal, so Google discounts the field. lastmod is a hint about freshness, not a command to recrawl.
Diagnostic use case
Set lastmod to reflect genuine content changes so Google can prioritize recrawling updated pages, and fix the inaccurate-lastmod patterns that make Google ignore the field.
What WebmasterID can help detect
WebmasterID shows when crawlers actually refetch URLs, which you can compare against your lastmod values to see whether updated pages are being recrawled and whether your freshness signals are being acted on.
Common mistakes
- Setting lastmod to the sitemap generation time for every URL.
- Copying one date (like the homepage's) across all URLs.
- Bumping lastmod when the main content did not actually change.
- Using an invalid datetime format that the parser rejects.
Privacy and accuracy notes
lastmod is a content-change timestamp, not visitor data. WebmasterID records crawler fetches and responses as bot events and stores no user information.
Frequently asked questions
- Does Google use the lastmod value?
- Yes, when it is consistently accurate — Google can use it to prioritize recrawling changed URLs. If lastmod is unreliable (all the same date, or always today), Google ignores it.
- Should I update lastmod for any page change?
- Only for meaningful changes to the page's main content. Updating it for unrelated template or boilerplate changes makes the signal noisy and untrustworthy, which leads Google to discount it.
Related pages
- XML sitemap best practices
An XML sitemap lists URLs you want crawled, helping search engines discover pages they might miss through links alone. The format has firm limits — 50,000 URLs and 50MB uncompressed per file — and works best when it contains only canonical, indexable, 200-status URLs with accurate lastmod values. This page covers the documented rules and the common quality problems that make a sitemap less useful.
- Sitemap index files
A sitemap index file is a sitemap that lists other sitemaps, letting large sites stay within the 50,000-URL and 50MB-per-file limits while exposing all URLs through one submitted entry point. This page explains the sitemapindex format, the same per-file limits that apply to the index itself, and best practices for organizing and submitting multiple sitemaps.
- Monitoring crawl errors over time
Monitoring crawl errors means watching, over time, the rate and type of failures crawlers encounter: rising 404s, new 5xx spikes, redirect chains, robots.txt fetch failures, and host-status problems. Caught early through Search Console reports, server logs, and uptime checks, these are cheap to fix; caught late, after pages drop from the index, they are costly. The goal is trend detection, not one-off checks.
- Website observability
Compare your lastmod values against when crawlers actually refetch URLs.
Sources and verification notes
- Google Search Central — Sitemaps best practices (lastmod)How Google treats lastmod and when it is ignored.
- sitemaps.org — lastmod
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.