How to validate an XML sitemap
A practical XML sitemap validation workflow covering discovery, syntax, indexes, URL eligibility, redirects, noindex directives, and canonical conflicts.
Direct answer
Validate a sitemap in two layers. First confirm that robots.txt or the conventional sitemap path exposes a successful XML urlset or sitemap index. Then inspect submitted URLs for successful responses, indexability, redirect-free delivery, and canonical consistency. Valid XML alone does not prove that the URL inventory is suitable for search.
Confirm discovery and HTTP delivery
Check the Sitemap directives in robots.txt, then request each declared file directly. A sitemap should return a successful response without authentication, cookies, or a browser-only challenge. If no declaration exists, test the conventional /sitemap.xml location.
Record the final URL and redirect chain. Redirecting the sitemap file can work, but publishing and declaring its final location removes an avoidable dependency.
- The response is HTTP 200.
- The body contains a urlset, sitemapindex, or valid text sitemap.
- Nested sitemap files are reachable.
- Every loc value is an absolute public URL.
Validate structure and protocol limits
Parse the document as XML rather than looking for URL-shaped strings. A sitemap index should contain sitemap entries, while a URL sitemap should contain URL entries. Image, video, and news extensions can add child elements but do not change the root document type.
Each sitemap file is limited to 50,000 URLs and 50 MB uncompressed. Split larger inventories into child sitemaps and list them in a sitemap index.
Test whether submitted URLs belong in the sitemap
Sample URLs from across the inventory, not only the first file or first template. Fetch each URL and compare its response, robots directives, and canonical target with the submitted location.
Prioritize failed responses and noindex URLs first, followed by redirects and canonical conflicts. Duplicate locations and optional formatting cleanup are lower priority unless they indicate a broken generator.
- The URL returns a successful response directly.
- The page does not declare noindex.
- The submitted URL matches the final canonical form.
- The content represents a page the site actually wants indexed.
Verify the fix with the same evidence
After updating the sitemap generator, fetch the live file again and rerun the URL sample. Submit the final sitemap URL in Search Console when needed, but do not treat submission as proof that every URL will be indexed.
Implementation checklist
- ✓robots.txt declares the final sitemap URL where appropriate.
- ✓Every sitemap document returns HTTP 200 and parses correctly.
- ✓Sitemap indexes reference valid child sitemap files.
- ✓Files remain within the published URL and size limits.
- ✓Sampled URLs return successful, indexable responses.
- ✓Redirects, noindex URLs, and canonical conflicts are removed.
Frequently asked questions
Is an HTTP 200 response enough to validate a sitemap?
No. The body can still contain malformed XML, HTML, an invalid root element, or URLs that should not be submitted.
Does a valid sitemap guarantee indexing?
No. A sitemap helps discovery and communicates preferred URLs. Search engines still evaluate crawlability, canonicalization, content quality, and index eligibility.
Should a validator fetch every submitted URL?
A full crawl can do that. A free public check should state its limits and use a representative URL sample rather than pretending that unmeasured URLs were verified.
Primary sources
These references support the standards and product behavior described above. They do not imply endorsement of Index Instrument.