---
title: "How accurate are sitemap lastmod values? Bing's study"
url: https://seomadman.com/research/bing-sitemap-lastmod-accuracy-study
section: research
published: 2026-09-18T00:00:00.000Z
modified: 2026-09-18T00:00:00.000Z
author: Adam Hafez
topics: ["Technical SEO", "Indexing"]
---

# How accurate are sitemap lastmod values? Bing's study

## The short answer

Bing's study found that among hosts with a sitemap, 84% of those sitemaps set lastmod, but 18% set it incorrectly, most often as identical dates equal to the sitemap's generation time. Google states it uses lastmod only when it is consistently and verifiably accurate, so a wrong date is worse than none.

## Key takeaways

- Bing reported that 58% of hosts with at least one indexed URL had a known XML sitemap, and 84% of those sitemaps set a lastmod attribute.
- Bing reported that 79% of lastmod values were correct and 18% were not correctly set, with identical dates across URLs the most common fault.
- After talking to webmasters, Bing concluded most wrong dates were the sitemap generation date, not the date the content was modified.
- Bing said it was rebuilding its crawl scheduling to use lastmod, so accurate dates reduce crawling of unchanged pages and favor recently updated ones.
- Google documents that it uses lastmod only if it is consistently and verifiably accurate, which makes an untrustworthy date a liability.

Most sitemap advice says to include lastmod. The harder question is whether the dates in real sitemaps are worth reading. Bing's webmaster team answered part of that in February 2023 with a short study of how sitemaps set the tag, and the result explains why search engines are cautious about it.

## What did Bing measure about sitemap lastmod?

Bing looked at websites with at least one URL indexed by Bing. It reported that 58% of those hosts had at least one XML sitemap known to Bing. Of those sitemaps, 84% set a lastmod attribute. Of the sitemaps with lastmod, Bing stated that 79% had correct values and 18% had values that were not correctly set.

The post does not describe how Bing decided a value was correct, and it gives no sample size. Treat the percentages as Bing's own reported figures, not as an audit anyone can reproduce.

## Why were so many lastmod values wrong?

Bing named one dominant fault: identical lastmod values across URLs. After consulting webmasters, it found the date on most sitemaps was set to the date the sitemap was generated, not the date the content was modified. A generation timestamp changes every build whether or not a page did, so it tells a crawler nothing about which pages to revisit.

Bing's advice followed from that. Set lastmod to the date the page was last modified, use the W3C Datetime format, and generate sitemaps at least daily so the tag keeps pace with edits.

## Does Google use lastmod?

Google does not publish a study like Bing's. Its sitemap documentation says it uses the lastmod value if it is consistently and verifiably accurate, for example by comparing it to the last modification of the page. That conditional is the practical takeaway: a sitemap that stamps every URL with a build date is the pattern Bing found, and it gives a crawler no reason to trust the field. If you cannot make lastmod track real edits, do not publish it.

## What are the limits of this evidence?

The study is a vendor's summary of its own data, published as a blog post. It shows how often lastmod is set badly, and that Bing changed its crawl scheduling in response. It does not measure how much faster pages are recrawled after a site fixes its dates, and it does not cover Google. Those gaps are why this piece reports the hygiene numbers and stops there.

## Sources

1. [The Importance of Setting the lastmod Tag in Your Sitemap](https://blogs.bing.com/webmaster/february-2023/The-Importance-of-Setting-the-lastmod-Tag-in-Your-Sitemap) - Bing Webmaster Blog (primary)
2. [Build and Submit a Sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) - Google Search Central