What this check tests
The audit requests exactly /sitemap.xml on your host. It passes when the response is a 200 and the body contains the text <urlset (a sitemap) or <sitemapindex (an index of sitemaps). Anything else is a fail.
What it does not do:
- It does not read the
Sitemap:line in your robots.txt. A sitemap at/sitemaps/main.xmlannounced only there will fail this check even though search engines can find it. - It does not validate the XML, count URLs, or check that the listed pages exist.
Why it matters to agents
The sitemaps.org protocol defines a sitemap as an XML list of URLs, with optional last-modified dates, that crawlers can read to find your pages. Google's documentation says search engines read the file to crawl a site more efficiently, and that it helps discovery but does not guarantee every listed URL is crawled or indexed. It also says a site might not need one if it has about 500 pages or fewer that matter and is well linked internally.
For agents that discover content by crawling, a sitemap is a ready-made list of what is on the site and how recently it changed. This audit also uses it to choose the extra pages it samples.
How to fix it
Serve an XML file at https://example.com/sitemap.xml, UTF-8 encoded:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-10-01</lastmod>
</url>
<url>
<loc>https://example.com/pricing</loc>
</url>
</urlset>
- The protocol limits each sitemap file to 50,000 URLs and 50 MB uncompressed. Past that, split it and list the parts in a sitemap index (a
<sitemapindex>file) served at/sitemap.xml. - Entity-escape special characters in URLs, and use full absolute URLs.
- Add
Sitemap: https://example.com/sitemap.xmlto robots.txt so crawlers that read robots.txt find it too. - If your CMS or framework can generate this file, use that instead of maintaining it by hand. Platform pages exist for WordPress, Next.js, Shopify, Docusaurus, Nuxt and Astro.
- If your generator writes a different path, also serve or redirect
/sitemap.xmlto it so this check finds it. A redirect is fine as long as the final response is a 200 with the XML. Related: HTTPS.