To find the sitemap of a website, open its robots.txt file (example.com/robots.txt) and look for a line that starts with Sitemap:. If there is none, try example.com/sitemap.xml, then /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml.
On November 16, 2026 we ran those checks on 22 well-known sites. robots.txt named the sitemap on 19 of them, /sitemap.xml led to one on 18, and the two steps together found a sitemap on all 22. The table further down shows where each one lives and where the guesses went wrong.
We build ContextBolt SEO, which audits a site from your AI agent, so weigh the bias. Everything below works in a browser.
- Start with robots.txt: open the domain followed by /robots.txt and look for
Sitemap:lines. It named the sitemap on 19 of the 22 sites we checked. - Then guess: /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml. /sitemap.xml led to a sitemap on 18 of 22, four of them through a redirect.
- Your own site: your SEO plugin or platform settings show the address, and Search Console’s Sitemaps report lists every sitemap you submitted through it.
- Check what you find: the free sitemap checker tries robots.txt and the four common addresses for you, then reads the file the way Google does.
Check robots.txt first
robots.txt is the file a site uses to tell crawlers what they may fetch, and it is where a site announces its sitemap to them. It always sits at the root: example.com/robots.txt.
Open it and read every line that starts with Sitemap:. Google’s sitemap documentation describes the line as Sitemap: https://example.com/my_sitemap.xml and says “you can specify multiple sitemap lines, and there’s no limit to the number of sitemaps you can include in your robots.txt file.”
What we found in those lines on November 16:
- One line: 13 of the 22 sites. contextbolt.com names
/sitemap-index.xml, Yoast names/sitemap_index.xml, Shopify names/sitemaps_list.xml. - Many lines: bbc.com listed 20 or more, one per language service and archive. Notion listed 12, some on a separate host, sitemaps.notion.com.
- Odd but readable: The Guardian names two addresses on
http://, which redirect to https. Gymshark repeats the same line three times. - No line at all: nextjs.org (its robots.txt returned 404) and hubspot.com. wpbeginner.com’s robots.txt refused our request with a 403, which is a firewall’s answer to a data center, not a statement about the file.
Stripe’s line points at /sitemap/sitemap.xml and Notion’s at another host. No guess would find either.
Try the common addresses
When robots.txt names nothing, guess. Each platform writes its sitemap to a predictable place. These addresses come from each platform’s own documentation, read on November 16, 2026.
| Platform | Address | Note |
|---|---|---|
| WordPress, no SEO plugin | /wp-sitemap.xml | Built in since WordPress 5.5 |
| Yoast SEO | /sitemap_index.xml | Yoast’s spec has /sitemap.xml redirect here |
| Rank Math | /sitemap_index.xml | From Rank Math’s own sitemap guide |
| Shopify | /sitemap.xml | Generated automatically at the domain root |
| Squarespace | /sitemap.xml | On your own domain, or the squarespace.com one |
| Next.js (App Router) | /sitemap.xml | Served from app/sitemap.ts or app/sitemap.xml |
| Astro with @astrojs/sitemap | /sitemap-index.xml | Also writes sitemap-0.xml |
Watch the address bar as each one loads. A redirect is the site telling you where the real file is. On contextbolt.com, /sitemap.xml redirects to /sitemap-index.xml. On yoast.com it redirects to /sitemap_index.xml, and on vercel.com to /crawled-sitemap.xml.
A file that opens is a sitemap if its first tag, after the <?xml line, is <urlset> (a list of pages) or <sitemapindex> (a list of other sitemaps). Some sites style the file as a table with a stylesheet, so view the page source if you are unsure. A web page at that address, a “page not found” screen or a login means the guess missed.
We checked 22 sites
On November 16, 2026 we requested robots.txt and the four common addresses from 22 public sites, once each, with a browser user agent, and recorded what came back. “Runs on” is what each homepage gave away: a generator tag or the asset paths a platform uses.
| Site | Runs on | Sitemap line in robots.txt | /sitemap.xml | Found first by |
|---|---|---|---|---|
| contextbolt.com | Astro | Yes, 1 | 301 to /sitemap-index.xml | robots.txt |
| astro.build | Astro | Yes, 1 | 404 | robots.txt |
| wordpress.org | WordPress | Yes, 9 | 200, an index | robots.txt |
| techcrunch.com | WordPress | Yes, 2 | 200, an index | robots.txt |
| yoast.com | WordPress | Yes, 1 | 301 to /sitemap_index.xml | robots.txt |
| wpbeginner.com | WordPress | Refused us (403) | 200, an index | /sitemap.xml |
| allbirds.com | Shopify | Yes, 1 | 200, an index | robots.txt |
| gymshark.com | Next.js, Shopify assets | Yes, the same line 3 times | 200, an index | robots.txt |
| squarespace.com | Squarespace | Yes, 1 | 200 | robots.txt |
| wix.com | Wix | Yes, 1 | 200 | robots.txt |
| webflow.com | Webflow | Yes, 1 | 302 to a CloudFront address | robots.txt |
| vercel.com | No signal | Yes, 1 | 301 to /crawled-sitemap.xml | robots.txt |
| nextjs.org | Next.js | No, robots.txt is a 404 | 200 | /sitemap.xml |
| theguardian.com | No signal | Yes, 2 on http | 404 | robots.txt |
| bbc.com | Next.js | Yes, 20 or more | 200 | robots.txt |
| developer.mozilla.org | No signal | Yes, 1 | 200, an index | robots.txt |
| stripe.com | Next.js | Yes, 1 | 404 | robots.txt |
| github.com | No signal | Yes, 1 | 406 | robots.txt |
| notion.com | Next.js | Yes, 12 | 200, an index | robots.txt |
| ghost.org | Hugo | Yes, 1 | 200, an index | robots.txt |
| hubspot.com | HubSpot CMS | No | 200 | /sitemap.xml |
| shopify.com | Shopify | Yes, 1 | 200, a different file | robots.txt |
robots.txt named the sitemap on 19 of 22 sites. /sitemap.xml answered 200 with a sitemap on 14 and redirected to one on 4 more, so it worked on 18. It was a dead end on four: astro.build, The Guardian and Stripe returned 404, and GitHub returned 406. Their sitemaps live at /sitemap-index.xml, /sitemaps/news.xml, /sitemap/sitemap.xml and /sitemap_marketing.xml, and robots.txt named every one.
The other three addresses added nothing that robots.txt or /sitemap.xml had not already found. On notion.com, all three redirected to app.notion.com and ended in a 404. On shopify.com, /sitemap.xml opened a real sitemap, but a different file from the index robots.txt names: it is one of the 653 files that index lists. A guess can land on part of a sitemap and look like all of it.
So start with robots.txt, and guess only when it names nothing.
Search Google for the file
Google indexes some sitemap files like pages. URL Inspection in our Search Console reports contextbolt.com’s sitemap index as “Submitted and indexed”, so a search such as site:example.com filetype:xml can turn one up. We could not test that search from our own server on November 16: Google answered it with its unusual-traffic check. Treat it as a last resort after the two methods above.
Find the sitemap on your own site
On a site you run, you can skip the guessing.
- Start from your platform. The table above gives the address each one uses. Shopify’s help says every store “automatically” generates /sitemap.xml, and Google’s help says hosts such as Squarespace or Wix “probably manage your sitemap for you”.
- Open Search Console’s Sitemaps report. It lists every sitemap submitted through the report or the API. Google’s Sitemaps report help adds a limit: “It does not show any sitemaps discovered through a robots.txt reference or other discovery methods.”
- Check WordPress’s reading setting. WordPress’s 5.5 announcement says that if Site Visibility is set to discourage search engines, “sitemaps will be disabled”. If /wp-sitemap.xml shows “Page not found” on a live site, check that box first.
If the report says the file you submitted “Couldn’t fetch”, the address is the first thing to check: sitemap could not be read walks through the rest.
When a site has no sitemap
Some sites do not have one, and some do not need one. Google’s Sitemaps report help says a site of “about 500 pages or fewer” where every page can be reached by links from the homepage “probably” does not need a sitemap, and that hosts such as Squarespace or Wix “probably manage your sitemap for you”.
For your own site, if you want one:
- Turn on the sitemap your platform or SEO plugin already offers. The table above lists the address each one uses.
- Add a
Sitemap:line with the full address to robots.txt. Google says it will “find it the next time we crawl your robots.txt file”. - Submit the address in Search Console’s Sitemaps report, so you can see when Google last read it and any errors.
Check the sitemap you found
Finding the file is half the job. A sitemap can sit at the right address and still be unreadable to Google: blocked by robots.txt, redirecting, full of URLs on the wrong host, or broken XML.
Our free sitemap checker does both halves. Paste a domain and it looks where Google would: the Sitemap: lines in robots.txt, then /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml and /wp-sitemap.xml. It fetches the file the way a crawler does, shows any redirect, checks it against robots.txt, and reads the XML for errors, with the line number when there is one. It also checks a sample of the pages the sitemap lists for 404s, redirects and noindex. It is free and needs no account.
The pages a sitemap lists are the next job. ContextBolt SEO gives your AI agent a site audit that starts from the same place: it finds the sitemap from robots.txt and the usual addresses, follows one level of sitemap index, and audits the most important pages first, 25 by default at 1 credit a page. A listed page that errors or redirects comes back flagged with its fix, and if the audit finds no sitemap it says so. For the full workflow, read a site audit with Claude.
Your next step: open your own site’s robots.txt and check that its Sitemap: line names the address you submitted in Search Console.