A sitemap

Does the site have a valid sitemap, and does robots.txt say where it is?

Coverage · 20 of 100 in Coverage · yours to do · sitemap

What we look for

A sitemap is an XML file listing the pages of your site. We look for one named in robots.txt with a Sitemap: line, and at the usual address, /sitemap.xml.

A valid sitemap passes in full, named in robots.txt or found at the usual address; naming it is optional, and the sentence says when you haven’t. A sitemap that’s there but broken (not XML, or not a list of pages) scores lower still, and no sitemap at all scores nothing. A one-page site needs none: the home page is the map, and it passes. If robots.txt names the sitemap through an unresolved CMS alias (@proxy/…, @web/…), we look for the file at the path that follows the alias and name the alias as the problem, since no crawler can follow it.

A sitemap whose addresses mostly fail earns only the share that load, whatever those addresses answer with; when they fail alike under one prefix, the sentence names the prefix they all share and how many of your addresses are under it (“1,416 addresses under /homepage/ answer 404”). When your sitemap is an index and we couldn’t read the lists of pages it names, the sentence says so; that is never scored. An address your firewall refused our bot says nothing of the map and isn’t counted (the AI crawlers get the pages browsers get criterion charges the firewall, once). No sitemap, but a feed and an archive page linked from your home page (a page called Archive or All posts, or a page your home page links that itself links nearly every post your feed carries)? That maps your site too, and passes, whether or not robots.txt declares a sitemap. But a sitemap that robots.txt declares and that doesn’t answer is a flaw of its own: beside a feed and an archive page it costs a fifth and the criterion warns; without them it fails. The fix is to remove the Sitemap: line or publish a sitemap at that address. A Sitemap: line must be a full address (https://…): a relative one (Sitemap: /sitemap.xml) isn’t valid; we read the file it points at all the same, and say so.

Why it matters

Crawlers find pages two ways: by following links, and by reading the list you hand them. A sitemap is that list. Without one, the pages nobody links to — an old post, a product page reached only through search — may never be found, and an AI assistant can’t mention a page that isn’t in its index.

Naming the sitemap in robots.txt matters because robots.txt is the first thing every well-behaved crawler reads. It saves them guessing, and not every crawler guesses.

How to pass

  1. Publish a sitemap listing the pages you want found, with the date each one last changed:
    <?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/about</loc><lastmod>2026-09-12</lastmod></url>
    </urlset>
  2. Add one line to robots.txt saying where it is:
    Sitemap: https://example.com/sitemap.xml
  3. Keep it current. Most platforms (WordPress, Shopify, Squarespace, Webflow) and site generators make one automatically; turn that on rather than writing it by hand.

Last changed .

The whole rubric