Sitemap lastmod: how Google uses it, and when to change the date
Google reads the lastmod date in your sitemap to decide when to recrawl a page, but only while your dates stay accurate. What counts as a change worth a new date, the format, and how to check Google actually came back.
<lastmod> is the date in your XML sitemap that says when a page last changed. Google uses it to decide when to recrawl a page it already knows about, and it is the only one of the three optional sitemap tags Google reads at all: <priority> and <changefreq> are ignored. The catch is trust. Google uses your dates only while they keep matching what it finds on the page, so a sitemap that stamps every URL with today's date on every build teaches Google to stop reading your dates.
TL;DR:
- Google uses
lastmod"as a signal for scheduling crawls to URLs that we previously discovered." It does not get a new page indexed and does not rank anything. - Google ignores
<priority>and<changefreq>. - Change the date when the main content, the structured data or the links on that page change. A new copyright year or a footer tweak does not count.
- Use W3C Datetime:
2026-11-10is enough, a time is optional. - After a change, check the page's last crawl date in URL Inspection. A new
lastmodis a request, not a guarantee.
What does lastmod do in a sitemap?
It tells Google when a URL last changed, so Google can decide whether to fetch it again. Google's own wording, from the post retiring the sitemap ping endpoint in 2023: it uses lastmod "as a signal for scheduling crawls to URLs that we previously discovered."
Two limits sit inside that sentence. It is a signal for scheduling, so it changes when Google comes back, not what Google thinks of the page. And it applies to URLs Google previously discovered, so a date on a brand-new URL does nothing that listing the URL in the sitemap does not already do.
Does Google use lastmod, priority and changefreq?
Only lastmod. Google's sitemap documentation says it plainly: "Google ignores <priority> and <changefreq> values." You can leave both out of your sitemap and lose nothing in Google.
lastmod comes with a condition. The same page says "Google uses the <lastmod> value if it's consistently and verifiably (for example by comparing to the last modification of the page) accurate." Google checks your dates against what it sees when it crawls. If the dates keep moving while the pages do not, it stops trusting them, for the whole site rather than one URL.
When should you update the lastmod date?
When something on that page changed that a reader or a crawler would notice. Google's documentation: "an update to the main content, the structured data, or links on the page is generally considered significant, however an update to the copyright date is not." The 2023 post adds that minor changes to sidebar or footer text do not need a new date.
In practice, give the page a new date when you:
- rewrote a section, added a paragraph or fixed a wrong fact
- changed the page's structured data
- added or changed links in the page's own content
- changed the title tag or meta description (our reading: Google's list does not name it, but it is part of what Google reads on the page)
Keep the old date when:
- a shared footer, nav or copyright year changed
- a link to this page was added on another page, because this page did not change
- the site was rebuilt and redeployed with no content change
That last case is the common failure. A static site generator or a framework that writes lastmod from the build time, or from the file's modified time after a fresh checkout, puts today's date on every URL on every deploy. To Google that looks exactly like dates that do not match reality.
The fix is to store the date with the content: a field in the front matter or the database row, set when the content changes, not when the site is built. If you cannot date a page reliably (a homepage or a category listing that changes with what sits under it), Google's 2023 post says you can leave lastmod off that URL.
Try it
Point an SEO agent at your own site, not just an essay about one.
QueryScope holds the plan for your site, reads your real Search Console, and hands the coding agent you already have one change at a time to rank for the searches you decided to win. From $49/month, everything included.
What format does lastmod use?
W3C Datetime. The sitemaps.org protocol says the format "allows you to omit the time portion, if desired, and use YYYY-MM-DD." Both of these are valid:
<url>
<loc>https://example.com/pricing</loc>
<lastmod>2026-11-10</lastmod>
</url>
<url>
<loc>https://example.com/blog/launch</loc>
<lastmod>2026-11-10T14:30:00+00:00</lastmod>
</url>
A date alone is enough for almost every site. If you add a time, include the timezone. Search Console reports a date it cannot parse after you submit the sitemap.
While you are in the file: a single sitemap holds at most 50,000 URLs or 50MB uncompressed. Past that, split it into several sitemaps under a sitemap index.
How do you know Google re-read the page?
Open the page in URL Inspection in Search Console and read Last crawl. If that date is after your change, Google has the new version. If it is still before, Google has not come back yet, however fresh your lastmod is.
Do not ping. Google retired the sitemap ping endpoint in 2023; requests to it now return a 404 and do nothing. Submitting the sitemap in Search Console or listing it in robots.txt is how Google finds it, and it re-reads a sitemap it knows about on its own schedule.
If a page stays unread for weeks after a real change, another date will not fix it. A link from a page Google crawls often gives Google a second way back to it. A page that was crawled and then left out of the index is a different case: Google has read it and decided against it, and a new lastmod will not change that decision. Finding the pages Google has not indexed covers how to list them and what each status means.
Keeping track of what Google has read
lastmod says when you changed a page. URL Inspection says when Google last read it. The gap between the two is what decides whether a change can have done anything yet, and nothing in Search Console puts them side by side.
QueryScope does. For every change your agent records on a page, it reads the sitemap's lastmod and the page's last crawl, starts the measurement only once Google has read the new version, and lists the changed pages Google has not read in two weeks or more. The same check runs through your coding agent over MCP, so the agent that edited the page can see whether Google has caught up. It reads your own Search Console over a read-only grant.
Sources
- Google Search Central, Build and submit a sitemap ("Google ignores
<priority>and<changefreq>values"; lastmod used if "consistently and verifiably" accurate; what counts as significant; 50MB and 50,000 URL limits). - Google Search Central Blog, Sitemaps ping endpoint is going away, June 2023 (lastmod as "a signal for scheduling crawls to URLs that we previously discovered"; minor sidebar or footer changes need no update; lastmod can be omitted where a page cannot be dated; ping endpoint retired).
- sitemaps.org, Sitemaps XML format (lastmod in W3C Datetime; YYYY-MM-DD allowed).
Try it
Put an SEO agent in your editor.
Ask your coding agent what to work on. QueryScope reads your real Search Console, holds the searches you decided to win, and hands back one move at a time with the proof it worked. From $49/month, everything included. 1, 3 or 10 sites.