How to Find the Sitemap of Any Website
Every website should have an XML sitemap, but finding it is not always straightforward. Here is how to find the sitemap of any website, step by step — whether you are auditing a competitor, checking a client site, or troubleshooting your own.
1. Try /sitemap.xml
The standard location for a sitemap is at the root of the domain. Open your browser and type example.com/sitemap.xml. If the site follows conventions, you will see an XML file listing all URLs. This works for most WordPress sites (Yoast and Rank Math place it here), Next.js sites, and many other platforms.
2. Check robots.txt
Go to example.com/robots.txt. Look for a line that says Sitemap: followed by the full URL. This is the official way sites declare their sitemap location. Some sites use non-standard paths like /sitemap_index.xml or /post-sitemap.xml — robots.txt is the only reliable way to find these.
3. Try Common Sitemap Paths
If /sitemap.xml returns a 404, try these common alternatives: /sitemap_index.xml (WordPress with Yoast) /wp-sitemap.xml (WordPress core sitemap) /sitemap/sitemap-index.xml /sitemaps/sitemap.xml /sitemap1.xml /page-sitemap.xml /post-sitemap.xml Shopify sites always have their sitemap at /sitemap.xml. Wix uses /sitemap.xml. Squarespace uses /sitemap.xml.
4. Use Google Search Console
If you own the site, log into Google Search Console and click Sitemaps in the left menu. You will see all sitemaps Google knows about for your site, including any that were auto-discovered. This also shows you the submission date, last read date, and how many URLs were discovered versus indexed.
5. Use SitemapFixer (Fastest Method)
Enter any domain in SitemapFixer and we check all 20+ common sitemap paths automatically. We also parse robots.txt, follow sitemap index references, and handle compressed sitemaps. You get the full URL list in under 60 seconds — plus an AI-powered SEO analysis of your sitemap structure.
6. Google the Sitemap
As a last resort, search Google for site:example.com filetype:xml. This can surface sitemaps that are linked from pages but not at standard paths. You can also try site:example.com sitemap to find pages that reference or link to the sitemap.
Sitemap Paths by Platform
How to See the Sitemap of a Website (View vs Find)
Once you have located the sitemap URL, "seeing" the sitemap means rendering the XML in a way you can actually read. Browsers handle this differently and the readable representation matters more than people realise.
Chrome and Safari render the XML as a collapsible tree by default. You see the <urlset> root, expandable <url> nodes, and the <loc> child of each. For a sitemap index, you see <sitemapindex> with nested <sitemap> entries — click each <loc> URL to drill into the child sitemap.
Firefox applies a built-in XSL transform that renders the sitemap as a table with columns for URL, last modified, change frequency, and priority. This is the friendliest in-browser view — easier to scan than Chrome's tree view — and it works even when the sitemap does not declare its own XSL stylesheet.
If the sitemap returns gzip-compressed (.xml.gz), your browser will usually decompress and display it transparently. If it does not, save the file and run gunzip sitemap.xml.gz locally. Some servers also serve .xml.gz with the wrong Content-Type header, which makes browsers download instead of display — adding the right header (application/gzip) fixes this on the server side.
For programmatic inspection, the fastest one-liner is curl -s https://example.com/sitemap.xml | xmllint --format -, which fetches the sitemap and pretty-prints it. To extract just the URLs: curl -s https://example.com/sitemap.xml | grep -oP '(?<=<loc>).+?(?=</loc>)'. Both work for sitemap indexes too, but you need to repeat the call for each child sitemap to get the full URL list.
What "Find a Sitemap" Means in Different Contexts
The exact same question — "how to find a sitemap" — gets asked for three different reasons. Knowing which one applies changes the answer:
You are a site owner trying to find your own sitemap. The fastest path: log in to Google Search Console → Indexing → Sitemaps. Every sitemap Google currently tracks for your property is listed there with its full URL. If GSC has none, check your CMS settings (the SEO plugin usually exposes the sitemap URL in its dashboard), then your robots.txt for a Sitemap: line. If neither shows one, your site does not currently expose a sitemap.
You are an SEO auditing a competitor. Sitemaps are public by design — no special access needed. Check robots.txt first (the Sitemap: directive is the canonical declaration), then the common paths in the platform table above, then run the competitor through SitemapFixer for autodiscovery across 20+ candidate locations.
You are a developer integrating with a third-party site's sitemap. Treat robots.txt as authoritative — it is the only place a site is required to declare its sitemap location for crawlers. Hard-coding /sitemap.xml works for many sites but breaks for any site using a sitemap index at a non-default path, which is the majority of large sites.