SitemapScan Blog

Sitemap lastmod: Correct Date Format, Common Mistakes, and SEO Impact

The lastmod field is one of the few sitemap hints search engines still care about. But malformed or noisy lastmod values can make the signal useless. Here is how to audit it properly.

Why lastmod still matters

Search engines have repeatedly downplayed fields like priority and changefreq, but lastmod still matters because it helps describe freshness. On large or frequently updated sites, accurate lastmod values can improve how search engines understand where recent change is happening.

Correct formats to use

A valid lastmod should use a W3C-compliant date, typically YYYY-MM-DD or a full ISO 8601 timestamp with timezone. Anything loosely human-readable, locale-specific, or inconsistently formatted risks becoming noise instead of a useful signal.

Common mistakes

Typical problems include invalid date strings, mixed formats inside one sitemap estate, timestamps that change on every deploy whether or not content changed, and lastmod values attached to URLs that are clearly stale, redirected, or broken.

About this article

This article is part of the SitemapScan blog and covers XML sitemap, robots.txt, crawlability, or related technical SEO topics.

FAQ

What is the correct sitemap lastmod format?

Use a W3C-compliant date such as YYYY-MM-DD or a full ISO 8601 timestamp with timezone.

Does Google still care about lastmod?

It remains one of the more useful sitemap freshness hints, especially when it accurately reflects real content change.

Related pages

Open the full article