Sitemap Finder
This sitemap finder takes a domain, or any page on a site, and finds every sitemap the site publishes: the Sitemap: lines in its robots.txt, the addresses sitemaps usually live at and the sitemap links on its homepage.
Try it on or enter any public domain. A page address works too: the finder checks the site it belongs to.
Reading robots.txt, trying the usual addresses and opening every sitemap found. A large sitemap index can take up to 14 seconds.
robots.txt against the sitemaps that exist
Add to robots.txt, on a line of its own, anywhere in the file:
Why and where: how to add your sitemap to robots.txt.
What we found
Sitemaps found
-
another host
- HTTP status
- URLs listed
- Newest lastmod
- Googlebot
- Content-Type
Validate this sitemap and check its URLs or Extract every URL
Every address we tried
robots.txt:
Found the sitemap. Now check every page in it.
Crawl Cove reads robots.txt and the sitemap on every crawl and raises the same mismatches as findings (sitemap-not-in-robots, sitemap-declared-missing, sitemap-declared-unreadable), then checks the listed URLs against the pages it crawls (sitemap-non-indexable-url).
Download Crawl Cove freeNote
Each file is opened and counted, with its newest lastmod date and whether Googlebot is allowed to fetch it, and a sitemap index is opened one level down. The result starts by comparing what robots.txt declares with what actually exists, and gives you the Sitemap: line to add when the two disagree. No sign-up and no email.
Use this tool often? Bookmark this page, so it is one click away next time.
Email me this result
Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.
Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.
How to find a website's sitemap with this tool
-
Enter the site
Type a domain such as example.com, with or without https://. A page address works too, because the finder always checks the whole site the page belongs to.
-
Read the verdict
The box at the top says whether robots.txt and the sitemaps that exist agree: declared and found, found but not declared, declared but broken, blocked for Googlebot, or nothing found anywhere.
-
Check each file
Every sitemap is listed with how it was found, its HTTP status, its type, the number of URLs it lists, its newest lastmod and whether Googlebot may fetch it. A sitemap index lists its child sitemaps.
-
Fix and validate
Copy the Sitemap: line into robots.txt if one is missing, then open any sitemap in the XML sitemap checker to test the pages it lists.
Where the sitemap finder looks, and in what order
First robots.txt. Every Sitemap: line in the file is listed, and the first ten are opened; the line can sit anywhere in the file and a site may have several. Then eight addresses sitemaps are often published at: /sitemap.xml, /sitemap_index.xml, /wp-sitemap.xml, /sitemap-index.xml, /sitemap.xml.gz, /sitemap.txt, /sitemaps.xml and /news-sitemap.xml. Last, the homepage: a <link rel="sitemap"> in its head and any link on the page whose address contains the word sitemap. Every address is followed through its redirects, so a /sitemap.xml that redirects to /sitemap_index.xml shows up once, as one file found two ways. A sitemap index is opened one level down, up to 50 child sitemaps, and each child is counted. The check stops after 14 seconds, and as soon as the site answers HTTP 429, so it never hammers a site that asks it to slow down.
Reading the results
The verdict at the top compares robots.txt with what exists. Declared and found is the healthy state. Found but not declared means the sitemap works but only crawlers you submitted it to know where it is, so the result gives you the exact Sitemap: line to paste into robots.txt. Declared but missing, declared but an HTML page and declared but unreachable mean robots.txt points crawlers at something that is not a sitemap. Blocked for Googlebot means a Disallow rule in robots.txt covers the sitemap address itself, and Google says it respects robots.txt when it fetches sitemaps. Under the verdict, each file shows its final address after redirects, its status code, its type (an XML sitemap, a sitemap index, a plain-text list of URLs, gzipped or not), how many URLs it lists, the newest lastmod date in it and a note when it sits on another host. HTML sitemap pages are listed separately, because they are pages for visitors and not files search engines read as sitemaps.
Why no sitemap was found
The site may simply have none, because the CMS feature is switched off or the site was built by hand and nobody made one. The sitemap lives at a custom address and robots.txt does not mention it; then only the site owner, or Search Console, knows where it is. A firewall or bot protection refuses automated requests, which shows up here as 403 errors or a challenge page on every address. The site rate limited the check, in which case the result says so and a second run a minute later usually gets further. Or the sitemap sits in a subfolder, such as /blog/sitemap.xml, that only a robots.txt line would reveal. The list of every address tried, with its status, tells you which of these you are looking at.
Where sitemaps live on common platforms
WordPress has generated its own sitemap index at /wp-sitemap.xml since version 5.5. The Yoast SEO and Rank Math plugins publish theirs at /sitemap_index.xml. Shopify generates /sitemap.xml for every store automatically, and it links to separate sitemaps for products, collections, blogs and pages. Wix keeps a sitemap index at /sitemap.xml that updates itself, and Squarespace generates /sitemap.xml automatically too. We checked each of these against the platform's own help pages in November 2026. A WordPress site can end up with two sitemaps when a plugin and core both publish one, which this finder shows as two files.
How to find a sitemap by hand
Open the site's robots.txt in a browser, for example https://example.com/robots.txt, and look for lines that start with Sitemap:. Google requires each one to be a full URL, and the sitemap does not have to be on the same host as robots.txt. If there is none, try /sitemap.xml and /sitemap_index.xml directly. For a site you own, Search Console's Sitemaps report lists the sitemaps submitted through that report and their status, such as Success or Couldn't fetch. It does not list sitemaps Google found through robots.txt, so an empty report does not mean the site has no sitemap. Searching the homepage source for the word sitemap finds any link to an HTML or XML sitemap.
What to do once you have found it
Validate it: a sitemap that exists can still list redirects, 404s and noindexed pages, and the XML sitemap checker opens one and tests the URLs in it. If robots.txt does not list it, add the Sitemap: line the result gives you. If robots.txt names a sitemap that answers 404, point the line at the real file or remove it. If Googlebot is blocked from the sitemap, add an Allow rule for its path or narrow the Disallow rule that covers it. Then submit the sitemap in Search Console's Sitemaps report, so you can see whether Google could read it. If the finder found nothing, generate a sitemap first.
robots.txt points at a sitemap that 404s · Search Console indexing issues explained
Frequently asked questions
- Does every website have a sitemap?
- No. A sitemap is optional, and plenty of small sites never publish one. WordPress, Shopify, Wix and Squarespace all generate one automatically, so on those platforms a missing sitemap usually means the feature was switched off or replaced by a plugin that publishes its own at a different address.
- How do I find the sitemap of any website?
- Enter the domain in the sitemap finder above. It reads the site's robots.txt for Sitemap: lines, tries the addresses sitemaps are usually published at and checks the homepage for sitemap links, then lists every file it found and how. By hand, open /robots.txt on the site and look for a Sitemap: line, then try /sitemap.xml and /sitemap_index.xml.
- Where should my sitemap be located?
- At the root of the site, such as https://example.com/sitemap.xml, unless your platform picks the address for you. Google says a sitemap only covers the URLs in the folder it sits in and below, so a sitemap in /blog/ cannot list your product pages unless you submit it in Search Console. Wherever it lives, name it on a Sitemap: line in robots.txt with its full URL.
- Why did it not find a sitemap?
- Most often the site has none, or it sits at a custom address that robots.txt does not mention. A firewall that blocks automated requests, or a site that rate limits the check, can also hide it; the list of addresses tried shows the status of each one, so you can tell which it was.
- What does sitemap index mean?
- A sitemap index is a sitemap of sitemaps: an XML file that lists other sitemap files instead of pages. Large sites use one to split their URLs, because a single sitemap may hold at most 50,000 URLs or 50 MB uncompressed. Google accepts up to 50,000 sitemaps in one index. This finder opens up to 50 of them and counts the URLs in each.
- What is the difference between an XML sitemap and an HTML sitemap?
- An XML sitemap is a file for search engines that lists URLs, and optionally when each changed. An HTML sitemap is an ordinary web page of links for visitors. Google accepts sitemaps as XML, RSS, mRSS, Atom 1.0 or a plain text list of URLs; an HTML page is not one of them, so this finder reports HTML sitemaps as pages, not as sitemaps.
- How do I submit my sitemap to Google?
- In Search Console, open the Sitemaps report for your property, enter the sitemap address and submit it. Add a Sitemap: line to robots.txt as well: Search Console tells Google only, while the robots.txt line is read by any crawler that supports sitemaps.
From one page to your whole site
This finds the sitemaps on one site and counts what they list. Crawl Cove reads robots.txt and the sitemap on every crawl, raises the same mismatches as findings, and compares the sitemap with the pages it actually crawls, including indexable pages the sitemap leaves out. See audit an XML sitemap across your whole site or how to add your sitemap to robots.txt.
More free tools
More technical SEO tools →-
Website SEO Checker
Open tool → -
HTTP Header Checker
Open tool → -
Canonical Checker
Open tool →