Sitemap validator
Check an XML sitemap the way a search engine reads it: protocol errors, limits, lastmod trust, hosts, and a live spot check of the URLs inside.
Loading the validator…
Errors, warnings and info, explained
Errors break the rules in the sitemaps.org protocol: XML that doesn't parse, a missing namespace, relative URLs, invalid dates, more than 50,000 URLs or 50 MB in one file. Google Search Console reports these as "Sitemap could not be read" or per-entry errors.
Warnings are legal but costly. Duplicate URLs, mixed www and bare hosts, tracking parameters and a lastmod that is identical everywhere don't stop Google reading the file, but they dilute what the sitemap tells it.
Info notes flag things that look alarming but aren't, like priority and changefreq, which are valid XML that Google has said it ignores.
Why a valid sitemap can still be a bad one
The XML only proves the list is readable. Search Console's "Submitted URL has crawl issue", "Submitted URL marked noindex" and "Page with redirect" reports come from what's behind each URL. That is why the validator can fetch a spread-out sample of 25 URLs and test each one for a 200 status, indexability and a self-referencing canonical.