Sitemap Finder: Discover XML Sitemaps for Any Site
Find XML sitemaps for any domain: robots.txt, /sitemap.xml, indexes, and common paths. Status, type, URL count, and XML validity. Free, no login.
- Enter a domain or URL
- Run sitemap discovery
- Review and export results
- Browser-based — no install
- Instant results
Paste a domain or URL to discover XML sitemaps from robots.txt, common paths like /sitemap.xml, and one level of sitemap index children. Each row shows how the file was found, HTTP status, index vs urlset type, URL count, and whether the XML parsed. Private hosts blocked; fetches capped per run.
By Faisal YUpdated
You need the XML sitemap before you can audit URLs inside it, submit the right file in Search Console, or compare staging to production. Guessing /sitemap.xml works on many WordPress and Shopify stores — until it does not. The reliable order is: robots.txt , common paths , then sitemap index children . The Sitemap Finder on Scrawl automates that sequence from our servers: it reads Sitemap: lines in robots.txt, probes standard paths ( /sitemap.xml , /sitemap_index.xml , /wp-sitemap.xml , and others), and follows one level of sitemap index files. Each result row shows the URL, how it was found, HTTP status, index vs urlset type, <loc> count, and whether the body parsed as valid sitemap XML. It does not check every page URL inside the file. Start with robots.txt Fetch https://your-domain/robots.txt and look for lines like: Google's robots.txt documentation treats these lines as discovery hints for sitemaps. A site can list multiple sitemap URLs, including files on another host (for example a CDN). Each URL must be absolute. Manual check: If robots.txt is missing or returns an error, continue with common paths — many sites still publish /sitemap.xml without a robots line. Common sitemap paths to probe When robots.txt is silent, these paths are worth a HEAD or GET (Scrawl uses GET with a size cap): | Path | Typical stack | |------|----------------| | /sitemap.xml | Generic default | | /sitemap_index.xml | Yoast, many custom builds | | /sitemap-index.xml | Hyphen variant | | /wp-sitemap.xml | WordPress core sitemaps | | /post-sitemap.xml | Split urlsets (plugins) | | /page-sitemap.xml | Split urlsets (plugins) | | /sitemap/sitemap.xml | Nested folder installs | | /sitemap.xml.gz | Compressed sitemap | A 404 on one path does not mean the site has no sitemap — it may only expose an index under another name.…
Read the full guideWhat this tool does
The Sitemap Finder answers **where a site publishes XML sitemaps** without logging into Search Console or guessing filenames. It fetches **robots.txt** on the input origin, collects every **Sitemap:** line, then requests common locations such as `/sitemap.xml`, `/sitemap_index.xml`, and `/wp-sitemap.xml`. When a file is a **sitemap index**, child sitemap URLs are fetched **one level deep** — nested indexes inside children are not expanded again.
Each row reports the sitemap URL, how it was discovered, HTTP status, whether the file is an **index** or **urlset**, how many `<loc>` entries were counted, and whether the body parsed as valid sitemap XML.
When to use it
- You inherited a site and need the real sitemap URL before an audit. - Search Console lists a sitemap you cannot find in the CMS. - You want to confirm **robots.txt** points at the same index the server actually serves. - You are comparing staging vs production sitemap locations during a migration.
For **validating XML syntax** on a file you already have, use the [XML Sitemap Validator](/tools/xml-sitemap-validator). For **HTTP status on URLs inside a sitemap**, use the [Sitemap Errors Checker](/tools/sitemap-auditor). For **robots.txt path rules**, use the [Robots.txt Tester](/tools/robots-txt-tester).
Honest limits
- Fetches come from Scrawl's servers with timeouts, size caps, and a maximum number of HTTP requests per run. - **Private, loopback, and metadata URLs are blocked** (SSRF protection). - Does not authenticate to password-protected hosts. - Does not execute JavaScript or discover sitemaps referenced only in HTML. - Child sitemaps on a different host are only fetched when listed in robots.txt or a parent index; cross-origin safety checks still apply.
Frequently Asked Questions
How does the Sitemap Finder locate sitemaps?
It reads Sitemap lines in robots.txt, probes eight common sitemap paths on the same origin, and follows sitemap index files one level to fetch listed child sitemaps.
What is the difference between a sitemap index and a urlset?
A sitemap index lists other sitemap files. A urlset lists page URLs. The tool labels each file and counts loc entries inside it.
Does this validate every URL inside the sitemap?
No. It reports file-level metadata only. Use the Sitemap Errors Checker or Bulk Status Checker to test URLs inside the sitemap.
Can it find sitemaps on subdomains?
Discovery uses the origin of the URL you paste. Sitemap lines in robots.txt may point at other hosts; those URLs are fetched only when they pass SSRF-safe validation.
What are the limits?
One domain or URL per run, capped response size, a limited number of HTTP fetches per scan, ten-second timeouts, and blocked private or localhost targets.
Related tools
XML Sitemap Validator
Crawl & AuditAnalyze XML sitemaps for critical errors to guarantee complete and efficient sea…
Sitemap Errors Checker
Crawl & AuditAudit every URL in a sitemap for status codes, indexability, and structural issu…
Google Robots.txt Tester
Crawl & AuditSimulate crawler behavior to verify your site's robots.txt directives and ensure…
Crawl Depth Checker
Crawl & AuditMap your site architecture and identify pages buried too deep for search engines…