Technical audit intake
Locate the public sitemap evidence before reviewing its contents or Search Console state.
Crawling and indexing tool
Sitemap Finder
Check where a website publicly advertises its XML sitemap. The finder reads robots.txt first, then tests only three common locations and shows every response instead of claiming an exhaustive discovery.
FreeNo loginNo data stored
Migration verification
Confirm that an advertised sitemap still resolves after host, protocol, or CMS changes.
CMS handoff
Give a developer the exact public URL and response evidence instead of guessing a default path.
What it checks
Use the result as evidence, not a score.
- Sitemap declarations in the root robots.txt file
- Three bounded common sitemap locations
- Final response, content type, redirects, and XML root evidence
- The exact locations checked during this run
What it cannot check
- Whether an unadvertised sitemap exists at an unusual location
- Whether listed URLs are canonical, valuable, indexable, submitted, or indexed
- Private Search Console submission history or crawl processing
How it works
Input, inspect, improve, verify.
The tool processes what you enter, shows a plain-language result, and gives you a safer next step. Make the change on your website, deploy it, then test the live page again.
Popular use cases
Useful before and after publishing.
Technical audit intake
Locate the public sitemap evidence before reviewing its contents or Search Console state.
Migration verification
Confirm that an advertised sitemap still resolves after host, protocol, or CMS changes.
CMS handoff
Give a developer the exact public URL and response evidence instead of guessing a default path.
Pro tips
Small checks that prevent avoidable mistakes.
- Check robots.txt declarations before assuming /sitemap.xml is the only location.
- Treat a successful response as discovery evidence, not proof that search engines use the file.
- Validate a found sitemap before relying on its URL list.
- Keep sitemap locations stable during migrations or update every declaration and submission deliberately.
Common issues and solutions
What to review when the result looks wrong.
robots.txt is unavailable
Review the response separately. A temporary server error can prevent reliable sitemap discovery even when a sitemap exists.
A common path returns HTML
A branded 404 page can return HTTP 200. Confirm that the response is real sitemap XML before using it.
Several sitemaps are advertised
That can be valid. Check whether they are a deliberate sitemap index or separate content-type sitemaps.
Frequently asked questions
Short answers before you make a change.
Does every website need an XML sitemap?
No. Sitemaps are especially useful for large, new, media-heavy, or frequently changing sites, but a small well-linked site may be discovered without one.
Does finding a sitemap mean its pages are indexed?
No. A sitemap is a discovery signal and does not guarantee crawling, indexing, ranking, or traffic.
Why does the tool check only three common locations?
The bounded list prevents brute-force path probing. Absence from those locations is reported as incomplete evidence, not proof that no sitemap exists.
Read the practical guide
How to find a website’s XML sitemap
Understand the evidence behind this tool, where its result stops, and the safer next steps to verify on a live page.
Read the guideEvidence · Limitations · Verification