← All package files
Standards-backed • sitemaps.org protocol

sitemap.xml

The map agents follow to discover all your content, generated only if you don't already have one, and never overwritten if you do.

What is sitemap.xml?

An XML file listing the URLs on your website, following the sitemaps.org protocol, referenced from your robots.txt via a Sitemap: line. It's the oldest discovery file in the package after robots.txt itself, and one of the two files agents check first when they land on a domain.

Why AI agents need it

A sitemap is essentially a map agents can follow to discover all your content without crawling every link. Crawl-budget economics matter even more for AI agents than for search engines: an agent answering a live question doesn't have time to spider your whole site, so a complete URL inventory at a known path directly improves what it can find.

The business value for you

Complete discoverability, for search crawlers and AI agents alike. In the Agent Readiness Score, your sitemap is scored on a published rubric under Discoverability: validity (40 points), coverage of your actual pages (30), whether robots.txt references it (15), lastmod freshness (10), and hygiene (5). It's one of the most fixable low scores in the whole model.

How it came to be

Google introduced Sitemaps in 2005; Google, Yahoo, and Microsoft jointly adopted the shared protocol in 2006, published at sitemaps.org. Two decades on, it remains the standard way to declare your URL inventory, and the pattern the newer agent files (like llms.txt) consciously imitate: a simple file at a known path that tells machines where to look.

Source: sitemaps.org protocol specification

Adoption

Mature and widespread, this is the least exotic file in the package. The gaps in practice are quality gaps: sitemaps that are stale, incomplete, unreferenced from robots.txt, or syntactically invalid. Cloudflare's agent-readiness model checks the same pair we do, robots.txt plus sitemap.xml, as the foundation of agent discoverability.

Source: Cloudflare, Introducing the Agent Readiness score (2026)

The technical reality

Our policy is create-if-absent, never-clobber: if your site already has a sitemap (most CMS platforms generate one), we leave it alone and score it; if you have none, we generate one from the analyzed URL inventory. Either way, /sitemap.xml is present and counted as the 13th canonical file of the package. The same never-clobber rule protects your robots.txt and existing structured data.

What happens if you skip it

Agents and crawlers discover your content only by following links, so orphaned pages, deep pages, and anything your navigation doesn't surface may simply never be found. For an AI agent on a time budget, an unmapped site is a partially invisible one.

How does your sitemap score?

The free Pre-Check grades your sitemap on the published rubric, along with the rest of your Agent Readiness Score.

Run My Free Pre-Check