Technical guide · Standard or specification
XML sitemaps and public URL discovery
What a sitemap actually tells automated systems, why it is useful for discovery, and why it does not replace navigation, canonicalization, or page accessibility.
- Published
- Updated
Scope: this guide explains a technical signal observed by AI Web Check. It does not claim that the signal causes ranking, indexing, citation or inclusion in AI answers.
What sitemap.xml contributes
A sitemap is a standardized list of URLs that a site owner exposes for crawler discovery. In the base XML protocol, loc identifies each URL; optional fields may be interpreted differently by individual consumers.
A sitemap makes the intended public URL set more explicit, but it does not prove page quality, indexability, canonical selection, ranking, or future citation by an AI system.
What AI Web Check evaluates
The checker verifies the base sitemap.xml response and separately checks whether robots.txt publishes a Sitemap: discovery line. These are distinct signals: the XML resource must be readable, while robots.txt provides a conventional discovery location.
AI Web Check does not recursively fetch every sitemap index or crawl every URL listed in a sitemap. The goal is bounded verification of the discovery surface rather than expansion into a site-wide crawler.
A minimal sitemap
robots.txt can also publish `Sitemap: https://example.com/sitemap.xml`. Prefer canonical public URLs rather than tracking variants, internal parameters, error pages, or URLs that immediately redirect elsewhere.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://example.com/</loc></url>
<url><loc>https://example.com/about</loc></url>
</urlset>Common failure modes
- sitemap.xml returns an HTML error page, challenge, or redirect loop instead of XML.
- Noindex pages, technical URLs, or non-canonical duplicates are included in the map.
- robots.txt points to a stale or unavailable sitemap.
- Teams expect sitemap inclusion by itself to guarantee indexing.
Implementation and verification
Generate the sitemap from the same source of truth that determines canonical public URLs. Remove URLs that should not participate in discovery and verify the final HTTP response after infrastructure or routing changes.
Large sites can use sitemap indexes and purpose-specific maps, but the relationship between robots.txt, the index, child sitemaps, and canonical URLs should remain predictable.