The lastmod value in an XML sitemap tells crawlers when a URL was last significantly updated. It looks like a small detail, but it can affect how search engines interpret freshness signals inside a sitemap. For static blogs, lastmod is especially useful because pages are generated from files. The build process can track publication dates, edited dates, or source file changes and then write them into the sitemap. The challenge is to use lastmod honestly, not as a fake freshness signal.
Google’s sitemap documentation says lastmod should reflect the date and time of the last significant update to the page. A meaningful change can include the main content, structured data, or links. A minor template change, footer update, or copyright year adjustment is not the same thing. This matters because Google says it uses lastmod if it is consistently and verifiably accurate: Google sitemap guidance. In plain terms, reliability is part of the signal.
The best setup for a static blog is to store two dates for each post: the original publication date and the last meaningful content update date. The publication date tells readers when the article first appeared. The lastmod date tells crawlers and technical tools when the content changed. If the article has never been updated, these dates can match. If the article receives a real update, such as new examples or corrected instructions, lastmod should change. If only the layout changes sitewide, the article’s lastmod should usually stay the same.
Do not set every lastmod value to the current build date. Static site generators can accidentally do this if they use the file generation time instead of the content update time. That creates a sitemap where every page looks freshly updated after each deployment. For a small site, this may not cause a visible penalty, but it makes the signal noisy and less useful. It also makes debugging harder because you can no longer tell which content actually changed.
The Sitemaps protocol allows lastmod dates in a valid date format, and Google’s documentation refers to W3C datetime format for sitemap index files. For most blogs, a simple YYYY-MM-DD date is enough if the site does not need precise time stamps. Use full datetime values only if your publishing system handles time zones correctly. A wrong future date, missing time zone, or inconsistent format can create avoidable validation issues. Simple and accurate is better than detailed and wrong.
Lastmod also helps with content maintenance. A site owner can sort the sitemap by age and find older posts that may need review. This is useful for technical SEO topics because documentation changes. For example, an article about robots.txt should remain aligned with the current robots.txt basics and official references. A post about sitemaps should match the principles explained in XML sitemap basics. The sitemap becomes a maintenance map, not just a crawler file.
The main rule is simple: change lastmod when the page meaningfully changes. Do not change it to create the appearance of freshness. Search engines and readers both benefit from honest maintenance. A static blog that uses lastmod well sends a clear signal that its technical content is stable, reviewed, and updated for real reasons.