Sitemap Finder: Find any site's sitemap.

Where to find a website’s sitemap: the short answer

Check three places, in this order. First, open /robots.txt on the domain and look for a line that starts with Sitemap: — that line exists to tell search engines exactly where the sitemap lives. Second, try /sitemap.xml, the most common location. Third, try the default for the site’s platform from the table below, such as /sitemap_index.xml on WordPress with Yoast or Rank Math. The finder above runs all three steps for you.

What the finder checks, step by step

1. robots.txt. We fetch /robots.txt and collect every Sitemap: line. When it lists several sitemaps, we read them together. News, video and image sitemaps and RSS feeds are set aside while a regular sitemap works, because they repeat pages that are already in it.
2. Seven standard locations. If robots.txt lists no regular sitemap that works, we try /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml, /sitemap/sitemap.xml, /wp-sitemap.xml and /sitemap1.xml, in that order, and use the first one that works. A news, video or image sitemap — from robots.txt, or at /news-sitemap.xml — is the last resort.
3. A real-sitemap test. A file only counts if it contains a <urlset> or <sitemapindex> element. An HTML error page sent with status 200 does not count.
4. Up to five sitemap files. For a sitemap index, we read the first five child sitemaps it lists. When there are several sitemaps, indexes come first, taking one child from each in turn, and plain sitemaps fill any room left. A child can be an index itself: on some Jetpack sites, such as wordpress.com/blog, sitemap.xml lists only sitemap-index-1.xml, and that file lists the page sitemaps. We open such an index and read the sitemaps it lists, regular ones before image and video ones, up to the limit of five. A file with no URLs in it, such as that inner index or a file that fails to load, doesn’t count toward the five. A URL that appears in more than one file is counted once.
5. 30 live page checks. We pick 30 URLs spread evenly across the sitemap and request each one. The report flags 404s, redirects, server errors, pages marked noindex, canonical tags that point somewhere else, URLs your robots.txt blocks, and responses slower than three seconds.

Each request waits up to eight seconds. If the domain doesn’t answer at all, the report says the domain is unreachable, instead of wrongly saying it has no sitemap.

Where each platform puts its sitemap

We checked one live site per platform on September 25, 2026. “In robots.txt” describes that example site on that day, not a platform rule.

What those 15 checks show

• 12 of the 14 sites on their own domain list the sitemap in robots.txt. The other two, gohugo.io and docusaurus.io, rely on /sitemap.xml alone.
• Every one of the 15 sitemaps was at a standard path or listed in robots.txt, so the finder located all of them.
• Some sites list several sitemaps. aioseo.com lists four: news, video, main and RSS. The finder sets the news and video sitemaps and the feed aside and reads the main index, /sitemap.xml: five of the 12 child sitemaps it lists.

When the finder says “no sitemap found”

• The site has no sitemap. Hosted builders such as Shopify, Wix, Squarespace, Webflow, Blogger and Ghost create one automatically; hand-built sites and many frameworks don’t.
• The sitemap uses a custom path that robots.txt doesn’t mention. Fix it by adding Sitemap: https://yourdomain.com/your-sitemap.xml to robots.txt. Google and Bing both read that line.
• The file is blocked for automated requests by a login wall, a firewall, or bot protection.
• The server returns HTML instead of XML, often a “page not found” template sent with status 200.

If you own the site, the Sitemaps report in Google Search Console lists every sitemap you have submitted and when Google last read it. For the manual method, see how to find a sitemap; if the site truly has none, start with how to create a sitemap.

Limits to know before you trust a clean result

• URLs are read from at most five sitemap files: the first five child sitemaps of an index, or five shared between the sitemaps robots.txt lists. make.wordpress.org lists 43 sitemaps covering 21 team sites (September 2026); a scan reads five of those team sites.
• We open an index inside an index in one extra round of requests. An index that first shows up in that round is not opened, so a third level is not read.
• A news, video or image sitemap or an RSS feed that robots.txt lists is skipped while a regular sitemap works. Errors that exist only in it are not reported.
• The live checks cover 30 sampled URLs, not every URL.
• Noindex is read from the robots and googlebot meta tags in each page’s <head> and from the X-Robots-Tag HTTP header. Canonical is read from the <head>. Only the first 1.5 MB of each page is read.
• robots.txt rules are matched as plain path prefixes in the User-agent: * group. Wildcards (*, $) and groups for named crawlers such as Googlebot are not evaluated.

After you find it

Submit the sitemap in Google Search Console and Bing Webmaster Tools, then use the report above: it shows how the sitemap is organised, which URLs look stale, and what the 30 live checks found. For a deeper structural read of the same scan, see the sitemap checker.