How to Find the Sitemap of a Website (7 Ways)

You need a site’s sitemap for a dozen reasons: auditing your own site, scoping a competitor’s content, planning a migration, or simply checking that Google can find every page. Yet there is no single standard location. A sitemap can live at /sitemap.xml, /sitemap_index.xml, /wp-sitemap.xml, /sitemap-index.xml or a path nobody would guess.

Here are seven methods, in the order we use them, plus how to test that the sitemap you find is actually valid.

1. Check robots.txt First

The fastest and most reliable method is to open the site’s robots.txt:

https://example.com/robots.txt

Look for lines starting with Sitemap::

User-agent: *
Disallow: /admin/

Sitemap: https://example.com/sitemap-index.xml

The sitemaps protocol allows site owners to declare sitemaps in robots.txt, and Google, Bing and other search engines read this line. A site can list several Sitemap: lines, for example one for pages and one for images. If the line is there, you are done.

This is also why “sitemap xml robots txt” go together in so many audits: declaring the sitemap in robots.txt is the only discovery method that works for every search engine without logging into a webmaster tool. If your own robots.txt does not reference your sitemap, add it. See our robots.txt best practices for the full file.

2. Try the Common Sitemap URLs

If robots.txt has nothing, try the usual locations directly in your browser:

URL	Typically used by
/sitemap.xml	Many custom sites and frameworks, Shopify, Wix, Squarespace
/sitemap_index.xml	WordPress with Yoast SEO or Rank Math
/wp-sitemap.xml	WordPress core sitemap (no SEO plugin)
/sitemap-index.xml	Astro, some static site generators
/sitemap-0.xml	Astro and Next.js sitemap packages (child sitemap)
/sitemap/sitemap.xml	Some enterprise CMS setups
/sitemap.xml.gz	Older or very large sites (compressed)

A useful trick: many sites redirect /sitemap.xml to their real index. Watch the address bar after the page loads.

3. Use the CMS Default

If you know the platform, you usually know the sitemap:

• WordPress: /wp-sitemap.xml by default, or /sitemap_index.xml if Yoast or Rank Math is active. Our WordPress robots.txt guide explains how plugins swap the sitemap line.
• Shopify: /sitemap.xml, which links to child sitemaps for products, collections, pages and blogs.
• Wix and Squarespace: /sitemap.xml.
• Webflow: /sitemap.xml once auto-generation is enabled in site settings.

To identify the platform, view the page source and look for telltale paths (/wp-content/, cdn.shopify.com) or a generator meta tag.

4. Search Google With Operators

Google sometimes indexes sitemap files. Try:

site:example.com filetype:xml
site:example.com inurl:sitemap

Results are hit and miss, but this occasionally surfaces sitemaps at unusual paths, such as a news sitemap or a sitemap for a subfolder.

5. Look in Google Search Console (Your Own Site)

For a site you own, open Search Console → Indexing → Sitemaps. You will see every sitemap submitted for the property, when Google last read it, its status, and how many URLs it discovered.

This is the most authoritative view of your sitemaps, because it shows what Google actually processed, not just what exists on the server. Bing Webmaster Tools has an equivalent Sitemaps report.

6. Check the Page Source and Footer

Some sites link an HTML sitemap in the footer (often labelled “Sitemap”). An HTML sitemap is a page for humans, not the XML sitemap search engines use, but it is often generated from the same data and sometimes links to the XML version. The page source may also contain a <link rel="sitemap"> tag, although this is not a standard search engines rely on.

7. Crawl the Site

If none of the above works, the site may not have a sitemap at all, or it may sit at an obscure path. Run a crawl with an audit tool or a desktop crawler. Many crawlers check robots.txt and common locations automatically and report “no sitemap found” as an issue. That finding is useful in itself: a site without a sitemap relies entirely on internal links for discovery.

Sitemap Index vs Child Sitemaps

Often the URL you find is a sitemap index, a file that lists other sitemaps rather than pages:

<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-posts.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
  </sitemap>
</sitemapindex>

Each child sitemap then lists the actual URLs inside <urlset>. The protocol caps a single sitemap at 50,000 URLs and 50 MB uncompressed, which is why large sites split them up. When auditing, open every child sitemap, not only the index.

How to Test a Sitemap Once You Find It

Finding the sitemap is half the job. A sitemap test should check these things, in this order:

1. It returns HTTP 200 and an XML content type, not an HTML error page with a 200 status.
2. It parses as valid XML. A stray character or unescaped ampersand (& instead of &) breaks the whole file.
3. Every listed URL returns 200. Redirects, 404s and 5xx errors do not belong in a sitemap.
4. Every listed URL is indexable. No noindex, not blocked by robots.txt, and the URL is its own canonical.
5. Important pages are included. Compare the sitemap against a crawl. Pages in the crawl but missing from the sitemap are the gap to fix.
6. <lastmod> values are honest. Google has said it uses lastmod when it is consistently accurate. A sitemap where every URL shows today’s date teaches Google to ignore the field.

A quick way to do steps 1 and 2 is a sitemap checker or simply opening the file in a browser, which will complain about malformed XML. Steps 3 to 5 need a crawler that can take a sitemap as input and report status codes and indexability per URL.

A worked example

An illustrative audit of a mid-size blog:

• robots.txt lists https://example.com/sitemap.xml.
• That URL 301-redirects to /sitemap_index.xml (fine, but better to list the final URL directly in robots.txt).
• The index links to four child sitemaps. One of them, category-sitemap.xml, lists 40 category pages that are all set to noindex.
• 12 post URLs in post-sitemap.xml redirect to newer versions after slug changes.
• 30 published posts appear in the crawl but not in any sitemap, because they were imported from another system without the right post type.

The fixes: point robots.txt at the final index URL, exclude noindex taxonomies from the sitemap, regenerate after redirects, and fix the post type on the imported posts. None of these is dramatic on its own. Together they are the difference between a sitemap Google trusts and one it treats as noise.

For the full set of rules, see our XML sitemap optimization guide. If your site has no sitemap yet, a sitemap generator is a reasonable starting point for small static sites.

What Most People Get Wrong About Sitemaps

The common belief is that a sitemap gets pages indexed. It does not. A sitemap helps Google discover URLs and understand which ones you consider important. Whether a page gets indexed still depends on its quality, uniqueness and internal links. If a page sits under “Discovered, currently not indexed” while listed in your sitemap, the sitemap did its job; the problem is elsewhere. Our guide to Discovered, currently not indexed covers what to do next.

Frequently asked questions

How do I find the sitemap of any website?

Open the site’s robots.txt and look for a Sitemap line. If there is none, try common paths such as /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml, then try Google search operators or a crawler.

Do all websites have a sitemap?

No. Sitemaps are optional. Small sites with good internal linking can be crawled without one, but most CMS platforms generate a sitemap automatically, and it is recommended for larger or frequently updated sites.

Should the sitemap be listed in robots.txt?

Yes. Adding a Sitemap line to robots.txt lets every search engine discover it without a webmaster tool account. It is optional but cheap and widely supported.

How can I check if a sitemap is valid?

Confirm it returns status 200 and parses as XML, then check that every listed URL returns 200, is indexable and is its own canonical. Search Console’s Sitemaps report also flags errors for your own sites.

What is the difference between an XML sitemap and an HTML sitemap?

An XML sitemap is a machine-readable list of URLs for search engines. An HTML sitemap is a regular page that helps human visitors navigate. They serve different purposes and can coexist.