Free XML Sitemap Checker & Validator
Find redirects, broken URLs, noindex directives and canonical conflicts in your sitemap. Export the findings and recheck the URLs you fix.
Check up to 200 URLs per run. For larger sitemaps, the checker spreads the sample across readable files.
How to use the checkerCheck a sitemap
Sitemap health
Sitemap files
| Select | Original URL | HTTP | Finding | Evidence |
|---|
How to use the sitemap checker
- Enter a public domain or sitemap URL. A domain starts discovery with robots.txt, followed by common sitemap paths. Paste an exact URL to check a specific file.
- Open a finding to see the evidence. For example, a sitemap URL returning a 301 may need to be replaced with its final address. Verify that the destination is the intended indexable page before editing the sitemap.
- Export the report and apply your fixes. Use Recheck Failed URLs to revisit the affected addresses or select individual rows. Start a new scan after changing the sitemap itself.
What sitemap problems does it detect?
- Redirects, broken URLs and server errors. See the first status, redirect hops and final response when available.
- Noindex and conflicting directives. Check generic and Googlebot-scoped meta robots and X-Robots-Tag directives in the fetched response.
- Canonical mismatch. Compare the final URL with HTML and HTTP Link canonicals. A missing canonical is shown in the details. Multiple distinct targets are flagged.
- Unable to verify. Robots restrictions, timeouts, refusals and failed connections leave the affected signals unverified.
Sitemap checker FAQ
Does a healthy result mean Google indexed the page?
Healthy describes the signals observed by this checker. To see Google's stored indexing status or selected canonical for a URL you own, use URL Inspection in Search Console.
How are large sitemaps sampled?
The checker distributes up to 200 slots across readable child maps and selects evenly spaced URLs from each map. It lists any discovery limits reached so you can check a particular child map separately.
Why was a test incomplete?
Discovery is limited to 16 XML files and 20,000 unique same-site URLs. Robots rules, unresponsive servers, invalid XML and request limits can reduce coverage. Slow scans continue in up to four batches of 45 seconds each.
Can I compare results after changing the sitemap?
Recheck tests the same page URLs against their current responses. Run a fresh check on the sitemap to discover new or removed entries. The browser holds your current results until you leave or reload.