XML Sitemap lastmod: Does Google Actually Use It?

Yes, Google uses the lastmod field in XML sitemaps — but only when it trusts that the dates are accurate. Google's own engineers have been unusually direct about this: if your lastmod values aren't reliable, Google ignores them entirely and falls back to its own crawl signals to decide when to revisit pages.

Here's what "reliable" means, how Google builds and loses trust in your dates, and how to set lastmod correctly.

Google's Confirmed Position

Gary Illyes (Google Search Relations) has said in multiple contexts that lastmod is "used if it's accurate." John Mueller has noted that if all pages in your sitemap have the same lastmod date — a common side effect of build-time sitemap generation — Google learns to ignore the field across your entire sitemap.

The mechanism is a trust score: Google compares your declared lastmod against what it finds when it crawls the page. If the page content hasn't meaningfully changed but the lastmod moved, that's a signal the dates aren't reliable. Enough mismatches and Google stops treating lastmod as a useful hint.

This is why the field is simultaneously useful and commonly misused.

The "Trust Score" Mechanic

Google doesn't publish its exact algorithm, but the observable behavior is:

1. Google crawls a URL and records what it finds — content hash, internal link changes, date signals from the page itself (like <meta name="article:modified_time">).
2. It compares this to your declared lastmod. If you said the page was updated yesterday but the content is identical to three months ago, that's a mismatch.
3. Repeated mismatches lower trust for your sitemap's lastmod values overall.
4. With low trust, Google crawls on its own schedule based on PageRank, inbound links, and historical crawl frequency — not your lastmod hints.

The inverse is also true: if your lastmod values consistently match real content changes, Google learns to trust them and may crawl updated pages faster.

What "Meaningfully Changed" Actually Means

Not every edit justifies a lastmod update. Google is looking for changes that affect a page's relevance to search queries — updated statistics, added sections, revised conclusions, refreshed examples.

Changes that don't warrant a lastmod update:

• Fixed a typo
• Updated a meta description only
• Changed a footer link
• Modified CSS or layout
• Added a product image without changing the product description

Changes that do warrant a lastmod update:

• Updated a factual claim (new statistics, corrected information)
• Added or rewrote a substantial section
• Changed the target keyword focus
• Refreshed examples or case studies
• Significant product information change (price, availability, specs)

The practical approach: track your content's actual last-meaningful-edit date separately from your CMS's default "updated_at" timestamp, and use that date for lastmod.

The W3C Datetime Format

The lastmod field requires a date in W3C datetime format, which is a subset of ISO 8601. Google accepts the following precision levels:

<!-- Date only (acceptable) -->
<lastmod>2026-05-24</lastmod>

<!-- Date with time and UTC offset (preferred for frequently updated content) -->
<lastmod>2026-05-24T14:30:00+00:00</lastmod>

<!-- Date with time in UTC using Z notation -->
<lastmod>2026-05-24T14:30:00Z</lastmod>

Common mistakes:

<!-- Wrong: American date format -->
<lastmod>05/24/2026</lastmod>

<!-- Wrong: Missing timezone (ambiguous) -->
<lastmod>2026-05-24T14:30:00</lastmod>

<!-- Wrong: Inconsistent format across URLs in same sitemap -->

If you're unsure what format your sitemap generator outputs, fetch your sitemap and check a few entries manually.

How to Set lastmod Correctly

For a CMS with a published/modified date: Use the CMS's updated_at or equivalent field — but only update that field when you make meaningful content changes, not on every save. Most CMSes update modified_at on every save, which defeats the purpose.

For a static site generator: Don't use build time. Instead, maintain a data file or use git commit timestamps for the file as a proxy. Some static site generators support this natively:

# Get the last git commit date for a specific file
git log -1 --format="%aI" -- content/posts/my-article.md

Use the output of this command as your lastmod value. It's accurate to when the content file actually changed.

For a dynamic CMS (WordPress, Shopify): Check your sitemap plugin settings. In Yoast SEO, for example, the sitemap uses the post's modified date — which WordPress updates on every revision, including autosaves and metadata-only changes. Consider filtering this so only substantial edits trigger a modified_at change.

A Minimal Correct Sitemap Entry

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/blog/my-article</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Note on changefreq and priority: these fields are documented but largely ignored by Google. Google has confirmed it doesn't use changefreq to schedule crawls. priority is only relative within your own sitemap and doesn't affect how Google weighs your pages against competitors. Focus your effort on lastmod accuracy.

Debugging "Google Ignored My lastmod"

If you've set lastmod correctly but Search Console shows your pages haven't been recrawled despite updates:

Step 1. Use URL Inspection to check the "Last crawl" date for a specific URL. If the crawl date predates your lastmod, Google either hasn't gotten to it yet or doesn't trust the date.

Step 2. Check whether your sitemap is submitted and returning a 200:

curl -I https://example.com/sitemap.xml

Step 3. In Search Console, go to Sitemaps and check the last read date and any errors. An error in parsing your sitemap means Google may not be reading your lastmod values at all.

Step 4. Look at a sample of your lastmod values. If many URLs share the same timestamp or if the dates don't match the actual content dates, Google has likely already deprioritized your lastmod signal.

Step 5. Request indexing for the specific URLs through URL Inspection. This forces a crawl regardless of schedule and bypasses the lastmod trust question temporarily.

Sitemap Structure and lastmod

If you're using a sitemap index file (multiple sitemap files managed by an index), lastmod can also appear on the sitemap entries within the index — not just on the URL entries within each sitemap. This tells Google which sitemap files have been updated, helping it prioritize which sub-sitemaps to re-fetch first.

For details on structuring a sitemap index, see sitemap index file.

The Bigger Picture

lastmod is a small but meaningful part of technical SEO. It sits in the sitemap layer, which is one of the earlier things to get right. Once your sitemap is submitting accurate URLs with reliable dates, combine that with correct crawl controls (see robots.txt syntax rules) and you've covered the discovery and scheduling side of how Google processes your site.