- Class
- C1 Mechanism
- Weight
- 8
- Severity on fail
- critical
- Applies to
- Google and Bing
Test this rule on a live site with the XML sitemap checker. Free, no account needed.
Scope and evidence
Evaluated on each sitemap file found. The book marks this requirement STANDARD (the Sitemaps protocol defines the mechanism, §2.1).
Fail conditions
Each condition has a stable code and a reason template. The evaluator fills the placeholders from observed values only; no sentence in a report is generated.
not_okThe sitemap {sitemap} returned {outcome}, so the URLs it lists cannot be read from it.
not_well_formedThe sitemap {sitemap} is not well-formed XML ({error} at line {line}, column {column}). The Sitemaps protocol requires a UTF-8 XML file with every data value entity-escaped.
wrong_rootThe sitemap {sitemap} has the root element <{root}>. The Sitemaps protocol requires <urlset> (or <sitemapindex> for an index) in the sitemap namespace.
The documented fix
Generate sitemaps with an XML serializer, not string concatenation, and serve them with a 200.
Sources, quoted
These are the passages the rule rests on, stored once in the knowledge base and emitted exactly as written. A citation marked for specific conditions appears only on findings with those codes.
“All data values in a Sitemap must be entity-escaped. The file itself must be UTF-8 encoded.”
[SITEMAPS-ORG] Sitemaps XML format (protocol) · Sitemaps XML format · last updated 2016-11-21
https://www.sitemaps.org/protocol.html“Begin with an opening <urlset> tag and end with a closing </urlset> tag.”
[SITEMAPS-ORG] Sitemaps XML format (protocol) · Sitemaps XML format · last updated 2016-11-21
https://www.sitemaps.org/protocol.html