Validate sitemap.xml and indexes for broken locs, lastmod coverage, nesting, and oversized URL inventories.
- Free
- No signup
- Fast
- Privacy-friendly
What is Sitemap XML Validator?
Search engines discover many URLs from XML sitemaps. Relative <loc> values, oversized files (past about 50,000 URLs or 50 MB), broken sitemap indexes, and fake lastmod dates quietly break that pipeline. Sites often advertise a Sitemap line in robots.txt while the XML itself is invalid or empty.
This Sitemap XML Validator discovers sitemaps from robots.txt Sitemap: lines and common paths like /sitemap.xml, classifies urlset vs sitemapindex, validates loc URLs, counts lastmod coverage, samples nested children (up to 5), and grades crawl-load size buckets — with findings and fixes, not a Google crawl-budget claim.
Use it after a site relaunch, when Search Console sitemap reports show errors, after migrating URL structures, or when a large catalog ships a new index.
What are common questions about Sitemap XML Validator?
What problem does sitemap validation solve?
It catches invalid locs, broken indexes, missing lastmod signal quality, and oversized inventories that stop crawlers from trusting your URL list.
Who runs sitemap checks?
SEO engineers, CMS admins, and ecommerce teams run them after migrations, catalog expansions, and Search Console sitemap errors.
What is the URL count limit per sitemap file?
Sitemaps protocol guidance caps about 50,000 URLs per file and about 50 MB uncompressed. Larger sites split via a sitemap index.
What is a sitemap index?
A sitemap index is XML with child <sitemap> loc pointers. Each child points at a urlset that holds a partitioned URL list.
Does missing lastmod block indexing?
No. Missing lastmod does not block indexing by itself. Accurate lastmod supports recrawl priority; fake dates reduce trust in the field.
What is a crawl-load indicator?
It is a size heuristic (low / moderate / high / very high) from URL counts. It describes inventory scale, not Google’s internal crawl budget.
How does robots.txt relate?
Robots.txt Sitemap: lines advertise locations. Parse those lines with the Robots.txt Checker; validate XML structure here.
How many child sitemaps are sampled?
The validator samples up to 5 child sitemaps from an index to bound runtime while still reporting full child counts.
What are the key features of Sitemap XML Validator?
Urlset and index detection
Classifies documents as urlset, sitemapindex, or unknown markup with clear evidence.
Loc validation
Flags missing locs and absolute-URL parse failures that crawlers cannot fetch.
Lastmod coverage
Counts URL entries without lastmod so recrawl completeness is visible.
Nested sitemap sampling
Fetches a capped set of child sitemaps and sums sampled URL counts.
Crawl-load buckets
Maps URL counts into low, moderate, high, and very high inventory buckets.
Robots discovery inputs
Uses Sitemap lines from robots.txt plus common /sitemap.xml paths.
How do you use Sitemap XML Validator?
Enter a site URL
Paste any URL on the origin that owns the sitemap inventory.
Run sitemap validation
Discover endpoints, parse XML, validate locs, and sample nested indexes.
Fix structure and advertise cleanly
Correct invalid locs, split oversized files, and keep Sitemap lines in robots.txt accurate.
Why broken sitemaps waste crawl and launch effort
Sitemaps are the discovery shortcut for large sites. Relative locs (`/page` instead of `https://example.com/page`), 404 child index files, and single files far past protocol size guidance cause crawlers to skip or partially consume the inventory. Teams often fix on-page SEO while the sitemap still lists old hosts or staging URLs.
The Sitemaps XML protocol defines `` for URL lists and `` for child pointers. Loc is required; lastmod, changefreq, and priority are optional. Google Search Central documentation downplays changefreq and priority as strong ranking inputs — accurate lastmod is the optional field that still matters when timestamps are truthful.
Use cases: migrations, catalogs, and Search Console errors
Domain or HTTPS migration — Confirm every loc uses the final absolute host and scheme; catch leftover http:// or old domain strings in sample tables.
Large catalogs — When URL counts approach 50k, verify whether you need a sitemap index and whether nested files stay under size limits.
Search Console “couldn’t fetch” / “invalid” — Reproduce with this validator: missing locs, malformed URLs, and unknown root elements show up as findings with evidence.
Post-robots wiring — After adding Sitemap lines via the Robots.txt Checker, validate that those advertised URLs return real urlsets or indexes.
Crawl-load buckets and honest limits
Buckets: low under 500 URLs, moderate under 5,000, high under 50,000, very high at 50,000+. These are deterministic size heuristics for planning splits and monitoring growth — not claims about Google’s crawl budget allocation.
Limits: child sampling is capped (5 nested files). The tool validates structure and loc quality from fetched XML; it does not prove that Google indexed every URL. Pair with HTTP Status Checker when individual locs return errors.
Free · API · MCPToolYour platform
Use Sitemap XML Validator three ways
The free Sitemap XML Validator on this page works in your browser. The same workflow is available via REST API for apps and via the remote MCP server for Cursor, Claude, and other agents — one API key, one plan, one quota. This tool is part of the seo-apis module under Digital Tools.
- Free in browserUse Sitemap XML Validator here — no account required.
- REST APICall from your server with
X-Api-Key. - Remote MCP serverSame job from Cursor or Claude via the ToolYour remote MCP server — one API key with REST.
- 1. Get an API keySign in and open Dashboard → API Keys (works for REST and MCP).
- 2. Call or connectUse the REST API from your server, or paste the MCP URL into your agent config.
- 3. Same key & creditsREST and MCP share one API key and monthly credit quota with this browser tool when the tool is API-backed.
Which technical SEO tools sit in this cluster?
- Page speed analyzer
Load and performance signals for a URL.
- Robots.txt checker
Crawl allow/deny rules and common mistakes.
- Canonical URL checker
Self-canonical, chains, and conflicts.
- HTTP status checker
Final status codes for publish and crawl hygiene.
- Redirect chain analyzer
Hop graph and crawl latency on redirect paths.
Where does this job fit on ToolYour?
Where do you browse more digital tools tools?
- Digital Tools tools
Browse the full Digital Tools category on ToolYour.
- Developer Tools tools
Format JSON, encode Base64/URL, mint UUIDs, convert timestamps, and test regex in the browser. REST and MCP sh
- Marketing Tools tools
Build UTM links, check ads copy limits, QA email subjects, and calculate ROAS/CPC/CTR — free in the browser; R