A post on DEV Community looks at the lastmod field in XML sitemaps, which tells search engines when a page last changed. Many CMS platforms and sitemap plugins fill it in automatically. Some use the last database save. Others use the build time, so a site rebuilt nightly reports every page as changed today.
According to the article, Google said in 2023 that it uses lastmod when the value is consistently and verifiably accurate, and that it ignores the priority and changefreq fields. The author ties lastmod to significant changes: main content, structured data or links on the page. A new copyright year in the footer does not count. A rewritten penalties section does.
The recommended setup is a dedicated content date field, kept apart from the CMS's own updated timestamp, which stays as an audit record. Editors set it, or the CMS sets it when a meaningful-change box is ticked. Static sites can keep the date in front matter. Existing sites should backfill it once from revision history, or from the last known review date, or leave it empty.
The sitemap is then built from that field, in W3C Datetime format. Where no trustworthy date exists, the author says to leave lastmod out rather than invent one, and not to use file modification times on a build server. The sitemap should list only canonical, indexable URLs that return a 200 status. The author also suggests a separate review date for pages checked with no changes needed, so editor visits do not move the sitemap date.
To check the result, compare a sample of sitemap dates with real edit history, and watch the Search Console Crawl stats report. The article says it can take months of consistent values for Google to trust the field again after a period of build-date stamping. It adds that a newer lastmod is not a ranking boost, that Google retired its sitemap ping endpoint in 2023, and that IndexNow is accepted by Bing and some others but not Google.
Why it matters
If your sitemap says every page changes every day, search engines have little reason to believe any of it. Honest dates are a small signal, but the article says Google uses them only when they prove reliable. That makes accuracy more useful than frequency.
The fix is mostly about process. Someone has to decide what counts as a real change and keep that rule consistent. The same approach applies to any site with pages that sit still for months and then get an important update, such as policy, pricing or advice pages.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.