Sitemap crawler to test the URLs it declares
The file is valid, what it declares may no longer be
A bare domain is enough, /sitemap.xml will be tried.
The sitemap is read on its own, with no crawl of the site: what gets tested is what the file declares, which is exactly the question.
Everything is computed in your browser. Nothing is stored.
A sitemap is almost always generated, and a generator rarely knows what happened to a page after it was published. So the file stays syntactically perfect while its contents quietly rot: a deleted post Google keeps fetching, a migrated address nobody replaced, a page set to noindex without the plugin noticing.
How to use it
How it works
Paste your sitemap
A bare domain is enough, the conventional location is tried on its own.
Run the URL read
Each address is queried, with its status, its redirect, its noindex and its canonical.
Filter by problem
Contradictions first: dead pages and noindex entries cost the most.
Worth knowing
Four things to keep in mind
Fix the generator, not the file
Almost everything that shows up here comes from a plugin or a build step that does not look at page state. Editing the XML by hand lasts until the next deploy.
A redirect in a sitemap is an admission
The file is meant to list final addresses. Leaving a redirect in asks Google to crawl two pages to reach one, and at scale that gets paid for.
Noindex and sitemap contradict each other
The file says index this, the page says absolutely not. Google follows the noindex, and the entry will only have spent a crawl.
There is no penalty, only delay
A file full of contradictions is read as an unmaintained file, so it gets fetched less often. It is not a penalty, it is every new page waiting longer.
FAQ
Frequently asked questions
It expands the sitemap, queries each address, and records its status code, any redirect and its destination, the presence of a noindex in a tag or a header, and whether its canonical names something other than itself.
Twenty per run, taken from the start of the file. That is enough to know whether a sitemap has a systemic problem, which is usually the question: a file whose first twenty entries are one third redirects will not be clean across the next nine thousand.
From the sitemap, yes. Restoring or redirecting the page is a separate decision that depends on what it earned. What is never right is leaving the entry in place: the sitemap is where you say what you stand behind.
Not directly. The cost is slower discovery and rarer recrawling, because Google reduces how often it fetches a file it has learned not to trust.
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.