XML sitemap exists: what the check tests and how to fix it

Passes when /sitemap.xml returns 200 with a body containing <urlset> or <sitemapindex>. A sitemap served only at another path is not found by this check.

Bot Accessibility · Weight 1.5 in the w2agent Score

How common is it?

67% of 1223 measured sites where this check applied pass.

Latest audit of each site under rubric v3.1. Sites where the check did not apply or could not be measured (for example, no llms.txt for the llms.txt checks) are left out. A partial result does not count as a pass.

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.xml announced 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.xml to 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.xml to it so this check finds it. A redirect is fine as long as the final response is a 200 with the XML. Related: HTTPS.

Examples from measured sites

Up to 10 of the highest-scoring sites in each group, from recent audits. Failing includes partial results.

Passing

Failing or partial

Sources

Verified against these sources on

Does your site pass this check?

Check your own site →