Sitemap lastmod dates: mistakes that make Google ignore them
Short answer: The <lastmod> date in your XML sitemap tells search engines when a page last changed in a meaningful way. Google says it uses the value only if it is consistently and verifiably accurate, and that it should reflect the last significant update: main content, structured data or links, not a new copyright year. The most common mistake is a sitemap that stamps every URL with today's date, which teaches search engines to ignore the field. Fix the source of the date, not the sitemap file.
A sitemap is one of the few direct hints you can give search engines about your pages. The <lastmod> field is the part of that hint that says "this has changed, have another look". When it is accurate, new prices, updated service pages and corrected opening hours can be picked up sooner. When it is wrong, it is noise. Below are the mistakes we see most often on UK small-business sites, with what to do instead.
How lastmod is supposed to work
The sitemaps.org protocol defines <lastmod> as an optional tag holding the date the page was last modified, in W3C Datetime format; you can use just the date (YYYY-MM-DD) and omit the time. The protocol is explicit on one point that many generators get wrong: the date must be set to when the linked page was last modified, not when the sitemap was generated.
Google's documentation on building sitemaps adds three practical rules:
- Google ignores the
<priority>and<changefreq>values. - Google uses
<lastmod>if it is consistently and verifiably accurate, for example when it matches the page's actual last modification. - The value should reflect the last significant update. Changes to the main content, structured data or links on the page generally count; an update to the copyright date does not.
That is the whole contract. Everything below is a way of breaking it.
Mistake 1: Every URL shows today's date
This is the classic. A plugin, a static-site build or a custom script writes the current date into every <lastmod> each time the sitemap is generated. To a crawler, it looks as if all 300 pages changed overnight, every night. Since Google checks lastmod against reality, a sitemap that cries wolf daily is easy to discount.
Instead: take the date from the page's own record, such as the post's modified timestamp in the database or the file's last commit date in a static build, and never from the build time.
Mistake 2: Site-wide template changes bump every page
You change the footer, add a menu item or update the cookie banner, and the CMS marks every page as modified. Technically the HTML changed; meaningfully, the content did not. By Google's definition, small boilerplate edits like a copyright year are not significant updates.
Instead: let lastmod follow changes to the page's own content. Most CMSs already separate "content edited" from "template changed"; check that your sitemap reads the former.
Mistake 3: Spending effort on changefreq and priority
Many sitemap plugins still offer fields like "change frequency: weekly" and "priority: 0.8", and owners spend time tuning them. Google states that it ignores both. Other search engines may treat them differently, but none of this is a substitute for an accurate date.
Instead: leave them at defaults or remove them, and put the effort into lastmod being true.
Mistake 4: Assuming your CMS outputs lastmod at all
WordPress has shipped built-in XML sitemaps since version 5.5. The announcement post on make.wordpress.org explains that the core sitemap lists only the URL itself by default, and that developers can add tags such as lastmod through filters like wp_sitemaps_posts_entry; the post includes an example that uses the post's modified date. In other words, a WordPress site using only the core sitemap may not be sending lastmod at all, while an SEO plugin sitemap usually does. Both are fine choices; just know which one is live.
Instead: open your sitemap URL in a browser (often /wp-sitemap.xml for WordPress core, or /sitemap_index.xml for some plugins) and look. If you have two sitemaps from two systems, choose one and turn the other off.
Mistake 5: Faking freshness by editing dates
Some sites change a page's "updated" date, in the sitemap or on the page, without changing anything else, hoping it will look fresh. Since Google compares the claimed date against the page, this mostly undermines trust in your sitemap.
Instead: update the date when you have actually improved the page: new information, corrected details, added FAQs, new internal links. If nothing changed, the old date is the honest one.
Mistake 6: Wrong format or timezone confusion
A lastmod of "05/11/2026" is ambiguous and not valid W3C Datetime. Full timestamps without a timezone offset can also be misread.
Instead: use 2026-11-05 or a full timestamp with an offset such as 2026-11-05T09:30:00+00:00. For most small sites, the date alone is plenty.
Mistake 7: Dates for URLs that redirect or no longer exist
Sitemaps that still list redirected or deleted pages, sometimes with fresh dates, send mixed signals. This often happens after a redesign when the old sitemap generator keeps running.
Instead: list only canonical, live URLs that return a normal page. After any migration, regenerate the sitemap and spot-check a handful of entries.
A ten-minute check
- Open your sitemap and pick five URLs you know well.
- Compare each lastmod with when you last really changed that page.
- Edit one page's footer only, regenerate, and see whether its lastmod moves. If it does, template changes are leaking into the date.
- Edit one page's main text and confirm its lastmod does move.
- Make sure only one sitemap is submitted in Search Console and listed in robots.txt.
FAQ
Do I need lastmod for every URL?
It is optional in the protocol. Including it is helpful when it is accurate; leaving it out is better than filling it with wrong dates.
Will an accurate lastmod make Google crawl my pages immediately?
No guarantee. It is a hint that helps search engines prioritise recrawling, not a command. Accurate dates make the hint worth listening to.
Should lastmod change when I fix a typo?
Use judgement. Google describes significant updates as changes to main content, structured data or links. A small typo fix is borderline; a corrected price or phone number is clearly worth flagging.
Does an RSS feed replace a sitemap?
Google accepts RSS and Atom feeds as sitemaps, but a feed usually only lists recent URLs, so it works best alongside a full sitemap.
If your sitemap stamps every page with today's date and you are not sure where that comes from, show us the sitemap URL and we will trace the date back to its source.