Why it matters
lastmodtells Google when a page last changed, so it can crawl changed pages first and leave the rest. Google uses it only if it is consistently and verifiably accurate.- A date in another form (
05/03/2026, Arabic digits, a day the calendar does not have) is not a date to a crawler, which skips it. - A sitemap where every page has the day the file was built tells Google nothing, and teaches it to ignore the date for the whole site.
Example
<url> <loc>https://shop.example/a</loc> <lastmod>05/03/2026</lastmod> </url>
<url> <loc>https://shop.example/a</loc> <lastmod>2026-03-05</lastmod> </url>
How to fix
Write each date as the day the page's content last changed, in the form YYYY-MM-DD, or with a time and a zone:
html
<url>
<loc>https://shop.example/a</loc>
<lastmod>2026-03-05</lastmod>
</url>- Use Western digits and hyphens:
2026-03-05, or2026-03-05T08:30:00+03:00. - Take the date from the page's own record (when it was edited), not from the time the sitemap is built.
- If you cannot give an honest date, leave
lastmodout: no date is better than a false one. - Platforms and plugins that write the sitemap have a setting for this; check that they write the content's date.
How we detect
- We read the sitemaps the scan fetched that are a
urlset, and the first 5,000 of their entries. - A
lastmodis valid when it is a W3C datetime: a dateYYYY-MM-DD, optionally with a time (T08:30:00) and a zone (Zor+03:00), on a day the calendar has. - The
identicalmessage needs ten dated entries or more, all the same. Ten is our threshold, to leave a small site that changed all its pages at once alone. - We do not judge whether a date is true: that needs the page's history.