What Is sitemap.xml? Format, lastmod Rules, and What Google Ignores
sitemap.xml is a file listing the URLs a site wants search engines to consider for crawling and indexing, along with when each one last meaningfully changed. It's a discovery aid, not a ranking factor: Google reads the URL and, when trustworthy, the last-modified date — and explicitly ignores the priority and changefreq fields the specification still defines.
⚡ Key Takeaways
- A sitemap doesn't guarantee crawling or indexing. Google's own documentation states plainly that it doesn't guarantee all listed items will be crawled and indexed.
- Google and Bing both ignore
<priority>and<changefreq>, even though both fields remain valid in the sitemaps.org specification. <lastmod>is the one optional field with a confirmed job, but only when it's consistently and verifiably accurate.- Inaccurate lastmod dates get ignored site-wide, not just for the offending URL — Google has stated it stops trusting the field once it notices a pattern of noise.
- The sitemaps.org protocol hasn't been revised since November 2016, so its documented ping-submission method is now dead at both Google and Bing.
- Only canonical, indexable, 200-status URLs belong in a sitemap — it should not be a dumping ground for every URL a site technically has.
What Is sitemap.xml?
sitemap.xml is an XML file that lists a website's URLs, primarily so search engines can discover pages efficiently, especially ones that might not be easy to find through normal link-following alone. Each entry can include a location, a last-modified date, and two optional fields — priority and change frequency — that the format has defined since its creation but that major search engines no longer act on.
The basic structure wraps a set of <url> elements inside a root <urlset>:
| Element | Purpose |
|---|---|
<loc> | The full, absolute URL of the page. Required. |
<lastmod> | The date the page last meaningfully changed, in W3C datetime format. Optional but the one field Google actually uses. |
<changefreq> | How often the page is expected to change. Optional; ignored by Google and Bing. |
<priority> | A relative importance value from 0.0 to 1.0. Optional; ignored by Google and Bing. |
What Google Actually Reads
Google's own sitemap documentation states plainly that it ignores <priority> and <changefreq> values entirely. Bing published the same position in its webmaster blog in mid-2025. Both tags remain technically valid at the protocol level — the sitemaps.org specification hasn't changed — so a sitemap containing them isn't invalid, but setting them provides no benefit with either major engine.
<lastmod> is the exception: Google uses it to help decide whether a known URL is worth recrawling soon, but only when the date is consistently and verifiably accurate — for instance, when it's checked against the page's actual last content modification rather than generated fresh every time the sitemap file itself is rebuilt. Setting every URL's lastmod to the current date on every generation is a common and counterproductive mistake: once Google notices the pattern, it can stop trusting the field for the entire site, not just the offending URLs.
Building and Maintaining a Sitemap
- Include only canonical, indexable, 200-status URLs — not every URL the site technically serves, and not pages that redirect, 404, or carry a noindex tag.
- Set lastmod from a real content-modification timestamp, such as a database's actual
updated_atfield, not the time the sitemap file happened to be generated. - Keep the file at the site root (
https://example.com/sitemap.xml) and declare it in robots.txt with aSitemap:line so crawlers can find it without a separate submission. - Split large sites into a sitemap index file referencing multiple child sitemaps, typically organized by content type or section.
- Compress sitemaps over roughly 1MB with gzip to reduce transfer size for large catalogs.
Auditing your own sitemap coverage?
Nstdata Crawl can fetch and validate your sitemap's listed URLs at scale, flagging redirects, errors, and stale lastmod patterns before Google does.
Try Nstdata Crawl →sitemap.xml vs. Adjacent Concepts
A sitemap and robots.txt solve different problems and are often confused: robots.txt tells crawlers what they may not request, while a sitemap tells crawlers what the site would like them to consider. A URL can be in the sitemap and still blocked by robots.txt, which is a contradictory signal worth avoiding. Sitemaps also don't replace strong internal linking — if a site's internal link structure is already solid, a sitemap helps only marginally, since crawlers were already going to find those pages through normal link-following.
Limits
A sitemap is a discovery aid, not a guarantee or a ranking signal — listing a URL doesn't force Google to crawl or index it, and it has no direct effect on how a page ranks once it is indexed. The sitemaps.org protocol itself is effectively frozen, last revised in November 2016, and its documented ping-based submission endpoint no longer functions at either Google or Bing, so submission through Search Console or an equivalent webmaster tool is the reliable path now. For sites with genuine crawl budget constraints, an oversized sitemap padded with low-value URLs can even work against the goal by diluting attention across pages that don't matter.
Conclusion
sitemap.xml's job has narrowed to what search engines actually use: <loc> for discovery and <lastmod> for recrawl prioritization, when the date is honest. Priority and changefreq remain valid syntax but do nothing at either major engine — spend that effort on accurate lastmod values and a sitemap that only lists canonical, indexable pages instead.
For teams that want to verify their sitemap's URLs actually return what they claim before submitting it, evaluate Nstdata Crawl for that audit step.
Further Reading
Sources
Try Nstdata Crawl to audit sitemap URLs
Validate status codes, redirects, and content freshness across your entire sitemap at scale.
Try Nstdata for Free →FAQ
Q: Does priority in sitemap.xml affect rankings?
No. Google and Bing both explicitly ignore the priority field. It remains valid in the specification but has no effect on either engine's crawling or ranking decisions.
Q: What format should lastmod use?
W3C datetime format, either a date like 2026-03-04 or a full datetime with a timezone offset. Formats like MM/DD/YYYY are invalid and will cause errors in Search Console.
Q: Why would Google stop trusting my lastmod dates?
If lastmod is set to the current date on every page regardless of whether content actually changed, Google can learn the field is unreliable and stop using it — for the whole site, not just the affected URLs.
Q: Does having a sitemap guarantee my pages get indexed?
No. Google's own documentation states a sitemap doesn't guarantee that all listed items will be crawled and indexed — it's a discovery aid, not a promise.
Q: Should a sitemap and robots.txt ever conflict?
No. Listing a URL in the sitemap while blocking it in robots.txt sends a contradictory signal. Keep the sitemap limited to URLs that are actually crawlable and indexable.
Was this guide helpful?
Your choice is saved on this device.
