Sitemap Finder & Checker

How this tool computes its result

Calls a backend API route that checks robots.txt for declared Sitemap: directives first, then separately probes a set of conventional sitemap paths directly. Each discovered sitemap is tagged with its source (robots vs probe), its detected type (urlset, sitemapindex, or unknown), and its own URL count; per-sitemap fetch or parse failures are attached to that individual entry rather than aborting the whole scan. The summary separately reports whether robots.txt declared any sitemap at all and links directly to it for manual inspection.

Worked example

Scanning a site whose robots.txt declares one sitemap, plus a second undeclared sitemap that happens to sit at a conventional path, returns two entries -- one tagged source: "robots", one tagged source: "probe" -- both counted in "Sitemaps found," even though only one was formally declared to crawlers.

When not to use this tool

Probing only checks a fixed list of conventional paths, so a sitemap at a genuinely unconventional URL that is also missing from robots.txt will not be discovered by this tool at all.

Common mistakes

• - Treating "Sitemaps found" as equal to "sitemaps declared in robots.txt" -- probe-discovered sitemaps count toward the same total even though search engines were never formally told about them via robots.txt.
• - Not checking individual entries' error fields -- a sitemap can appear in the results list with a URL but still carry its own parse error, which is easy to miss while only skimming the summary counts.
• - Assuming a "truncated" result means the site has no more sitemaps -- truncation only means the scan stopped early for speed, not that additional sitemaps don't exist.

Related tools