The best XML sitemap validator for most sites is the seogeoaeo.ai XML Sitemap Validator, because it checks a live sitemap against both the sitemaps.org protocol and Google's limits in one run and names the exact URLs and dates that fail. Google Search Console ranks second: it is free and confirms whether Google read the file, but it reports problems after you submit, not before.
We ranked the options on four things: what each one checks, whether it works on a live URL, whether it tells you which entries are wrong, and what it costs.
The ranking at a glance
| Rank | Tool | Best for | Cost |
|---|---|---|---|
| 1 | seogeoaeo.ai XML Sitemap Validator | Checking a live sitemap before or after you submit | 10 credits per run |
| 2 | Google Search Console Sitemaps report | Confirming Google fetched and processed the file | Free with a verified property |
| 3 | xmllint with the sitemaps.org schema | Checking a file locally in a build script | Free, open source |
| 4 | seogeoaeo.ai Orphan Page Finder | Finding sitemap URLs that redirect, fail or are noindex | 20 credits per run |
1. seogeoaeo.ai XML Sitemap Validator
You give it the public URL of a sitemap or sitemap index. It confirms the XML is well formed, checks for the sitemaps.org namespace, measures the file against the 50 MB and 50,000 URL limits, flags URLs outside the sitemap's scope and lists lastmod dates that are missing or malformed. Each run costs 10 credits, and the price shows before you start. It also runs over a REST API and MCP, so an AI agent or a deploy script can call it.
It checks one file per run and does not follow the children of an index, and it skips image, video and news extension tags. For the core protocol checks on a live file, it is the quickest sitemap check we found that reports problems by entry.
2. Google Search Console
Search Console shows each sitemap you submitted, when Google last read it, and one of three statuses: Success, Has errors or Couldn't fetch. Drill in and it lists errors such as "Invalid date", "URL not allowed" or "Incorrect namespace".
It is free and authoritative about Google. The catch is timing: you only see errors after Google fetches the file, and it lists only sitemaps submitted through the report or its API. Use it to confirm, not to pre-check.
3. xmllint with the sitemaps.org schema
sitemaps.org publishes XML schemas for sitemaps and sitemap index files. The open source xmllint tool can validate a file against a W3C XML Schema with its --schema option. This works offline and fits a build step.
Schema validation covers structure, not Google's rules. It will not tell you that a URL sits outside the sitemap's folder or that a file breaks the size limit in a way Google cares about. Pair it with one of the tools above.
4. seogeoaeo.ai Orphan Page Finder
This is not a validator in the strict sense. It crawls up to 150 pages from your home page, reads your XML sitemap and compares the two. It flags sitemap entries that redirect, fail or carry noindex, plus indexable pages missing from the sitemap. Run it after the file itself passes validation, to check that the URLs inside it are worth listing.
How to choose
If you want one check that catches format and scope errors on a live sitemap, start with the seogeoaeo.ai validator. If you already submitted and want Google's own verdict, open Search Console. If you generate sitemaps in a pipeline and want a free local gate, add xmllint. A large site that needs a full crawl of every page is better served by a desktop crawler than by any of these single-file checks.