3 weeks after submitting a sitemap for a client's e-commerce site, I checked Google Search Console. 70% of the pages weren't indexed. 70%. The content was solid. The site was fast. The backlinks were there.
What was the problem?
A single malformed date in the sitemap. One wrong date format caused Google's crawler to reject the entire sitemap — silently. No warning. No error message in Search Console. Just ... nothing.
I spent 4 hours manually parsing the XML before I found it. That's when I realized: sitemap validation isn't optional — it's essential.
That frustration led me to build a proper sitemap checker — the kind I wish I'd had that day.
What it does:
Structural validation — checks XML syntax, namespace declarations, and sitemaps.org schema compliance
URL validation — verifies each URL is well-formed and accessible
Metadata checks — validates lastmod format, changefreq values, and priority ranges
Limit enforcement — checks against the 50,000 URL and 50MB file size limits
Sitemap index support — recursively validates sitemap index files and all sub-sitemaps
100% browser-based — your data never leaves your machine
Under the hood, the checker first validates the sitemap's XML structure against the official sitemaps.org XSD schema. It then parses each entry, extracting the , , , and tags. Each URL is checked for accessibility with status code validation. Metadata is validated against allowed values — lastmod must be in W3C datetime format, changefreq must be one of always|hourly|daily|weekly|monthly|yearly|never, and priority must be between 0.0 and 1.0.
In this guide, I break down how sitemap validation works mechanically — from XSD schema validation to URL health checks to sitemap index recursion — so you understand exactly what's happening when you hit that Check button.
Top comments (0)