XML Sitemap Validator

Practical guide: what validation does (and does not) prove

What this is

This validator checks that your sitemap XML is well-formed, follows common sitemap protocol constraints, and—when enabled—may probe listed URLs for obvious HTTP failures. It is a preflight step before or after you submit to Search Console, not a substitute for crawl stats, index coverage reports, or log analysis. Valid XML can still list the wrong URLs.

When to validate a sitemap

• After generating or regenerating sitemaps from a CMS plugin or custom script.
• Before submitting a new sitemap index in Search Console or Bing Webmaster Tools.
• When coverage reports show “Submitted URL not found” or sitemap processing errors.
• After migrations that change hosts, paths, or which templates are indexable.
• As a recurring check in your Search Console weekly routine.

When validation is not enough

• Do not treat “valid” as “good SEO”—you can still list thin, duplicate, or noindex URLs.
• Avoid stuffing every faceted combination into the sitemap because the file parses cleanly.
• Skip relying on validators alone after WAF changes; bot checks can differ from Googlebot.
• Do not leave staging or parameterized URLs in production sitemaps just because XML is well-formed.
• Never assume lastmod accuracy without confirming your CMS actually updates it meaningfully.

How to use this validator

Submit the public URL of the sitemap your robots.txt references. Enable URL checks when you want a spot audit of reachability; expect slower runs on huge lists. Fix structural errors first (malformed XML, invalid lastmod, out-of-range priority), then re-run. After fixes, resubmit in Search Console and watch for processing errors over the next days. Pair results with include/exclude policy from XML sitemaps: what to include and leave out.

Worked example

An ecommerce sitemap index points to products, categories, and blog child sitemaps. Validation finds: one child file over the URL count comfort zone, twelve product URLs returning 404 after a catalog purge, and several lastmod values in the future from a timezone bug. Fixes: split the oversized child sitemap, remove or 301 the dead products and regenerate, correct lastmod to real UTC publish times, and ensure robots.txt still lists the index URL. Search Console previously warned about sitemap errors; after resubmit, processing succeeds and “submitted but not indexed” concentrates on thin tags you intentionally keep out of the next regenerate. Decision rule: sitemaps list preferred, indexable URLs only—canonicals and noindex handle the rest (robots / noindex / canonical).

How to read the results

Separate protocol issues from business decisions: a valid URL that returns noindex is “reachable” but may be the wrong inclusion. Warnings about optional fields are not always urgent. Cross-check high-error segments against recent deploys or CDN rules—mass 403s often trace to WAF rules, not SEO typos. Priority and changefreq are weak signals in modern Google usage; clean locs matter more than decorative fields.

Common mistakes

• Assuming valid XML equals good SEO while listing low-value or duplicate URLs.
• Running validators only once per year while the CMS auto-generates broken hrefs.
• Ignoring sitemap index vs child sitemap boundaries and size limits.
• Forgetting that CORS or bot blocking can make remote checks flaky—confirm anomalies manually.
• Listing HTTP or non-canonical hosts while the site lives on HTTPS www.
• Leaving retired URLs in the sitemap instead of updating redirects and regenerating.

QA checklist after validation

1. XML well-formed; index and child files within size/URL guidelines.
2. Sampled locs return 200 on the preferred host; no mass 404/soft-404 clusters.
3. Noindex, login, cart, and thank-you URLs are excluded by policy.
4. robots.txt Sitemap: line matches the file you validated.
5. Search Console accepts the sitemap without processing errors.
6. Document include/exclude rules so the next regenerate stays clean (hygiene checklist).

Related reading

SEO guide · XML sitemaps include/exclude · Search Console checklist · Robots / noindex / canonical · Technical hygiene. Related tools: XML sitemap generator, robots.txt generator, sitemap tools hub.

Before / after: “valid” sitemap full of junk

Before: A plugin sitemap validated as perfect XML yet listed tag archives, filtered category combinations, and thank-you pages. Coverage reports looked noisy; crawl budget chased low-value URLs.

After: Include/exclude rules limited the sitemap to canonical products, categories, and editorial URLs. Thank-you and account pages were removed; thin tags were noindexed and dropped from the feed. Validation still passed—and Search Console discovery became far more useful. Policy doc linked from the regenerate job so the junk could not creep back.

Sitemap index hygiene

When you outgrow a single file, use a sitemap index and keep child files themed (products, posts, videos). Validate the index and a sample of children after each regenerate. Point robots.txt at the index only. If a child fails validation, Search Console may ignore that segment while others succeed—fix the broken child rather than deleting the whole index.