Free XML sitemap checker with a health score
The file against the protocol, then its URLs for real, in one score
A bare domain is enough, /sitemap.xml will be tried.
The URL pass covers a sample taken from the start of the file: a clean result is solid evidence, not proof across the whole thing.
Everything is computed in your browser. Nothing is stored.
A sitemap fails in two unrelated ways, and most tools only look for one. The file itself can be broken: wrong namespace, relative addresses, a date Google refuses to read. Or the file can be flawless and its addresses can be the problem. A validator that only looks at the first case misses the second, which is the more common one.
How to use it
How it works
Paste your sitemap
A file, an index, or a bare domain whose conventional location will be tried.
Read the file pass
Namespace, absolute same-host addresses, dates, and the limits of the protocol.
Run the URL pass
A sample is queried, and the two passes combine into a single score.
Worth knowing
Four things to keep in mind
The URLs weigh more than the file
The score counts the file for 40% and the addresses for 60%, deliberately: Google tolerates a formatting warning far better than a file that sends it to dead pages.
A file that will not parse is discarded whole
It is not partially read. While the file pass fails, fixing addresses achieves nothing, because none of them will be read.
The score covers a sample
The first entries are queried, not all of them. A clean result is evidence rather than proof, and that is already what you came for.
Resubmit after fixing
Once the score has moved, redeclare the sitemap in Search Console so Google refetches it promptly rather than on its own schedule.
FAQ
Frequently asked questions
The crawler is the detailed report, address by address, with the nature of each problem. This checker is the quick pass you run first: file validation plus a sample of addresses, summed into one score. If the score is low, the crawler gives you the list to work through.
Because the address sample failed, not the file. Immaculate XML listing pages that 404, redirect or carry a noindex loses most of its points there. A valid file is the entry ticket, not the goal.
90 and above means the file is valid and the tested addresses answer cleanly. 70 to 89 means the sitemap works but is carrying problems, most often redirects left by a migration. Below 70, Google is being sent to enough broken addresses that the file is working against you.
Yes. The index is validated, then its child sitemaps are expanded to gather their addresses, within a deliberately low limit: expanding without a bound would send our server out dozens of times for a single submission.
Also
Other tools in the same family
Also
What Lokvi does for you
Now imagine all of it running without you
Review collection, replies, posts and loyalty, on your Google Business listing, automatically.
No credit card required: create your account and explore your real data.
14 days free, then 29 €/month, no commitment.