How to Find Your Sitemap.xml (and What to Do When You Can't)

A sitemap is the single most useful file for understanding a website at a glance: it's the site's own list of the pages it wants search engines to know about. When we built SeoSitemap.app, the very first thing every scan needs is that file — and we quickly learned that "where is the sitemap?" trips people up more often than you'd expect.

This guide walks through exactly how to find the sitemap for any site, in the order we actually try ourselves, plus what to do when the obvious paths come back empty.

Start with the obvious: /sitemap.xml

Nine times out of ten the sitemap lives at the root of the domain. Before anything clever, just type the address bar guesses:

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

That _index variant matters. Large sites split their sitemap into chunks (a sitemap index that points to many child sitemaps), because a single sitemap file is capped at 50,000 URLs or 50 MB. If /sitemap.xml shows a short list of other .xml links rather than your actual pages, you've found an index file — that's normal, and a good auditor will follow those children automatically.

If one of these loads, you're done. If they all 404, don't give up — move to the reliable shortcut below.

Check robots.txt (the reliable shortcut)

Every well-configured site has a robots.txt at its root, and by convention it declares where the sitemap lives. Open:

https://example.com/robots.txt

Look for a line that starts with Sitemap:. You'll often see something like this:

User-agent: *
Allow: /

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

This is the most dependable method, because it's the location the site itself advertises to Googlebot — no guessing required. A site can even list several sitemaps here (one for pages, one for images, one for news), so scan the whole file, not just the first match.

If robots.txt exists but has no Sitemap: line, that's a finding in itself: the site is making search engines work harder than they should. Adding that one line is a free, five-second SEO win.

Platform-specific sitemap locations

If you know what the site is built on, you can skip straight to the right path. Here are the defaults for the platforms we see most often:

WordPress

Modern WordPress generates a sitemap at /wp-sitemap.xml out of the box. If the site uses Yoast SEO or Rank Math (most do), the canonical location becomes /sitemap_index.xml instead — those plugins take over sitemap duties.

Shopify

Always /sitemap.xml, and it's always an index file that links to sitemap_products_1.xml, sitemap_pages_1.xml, sitemap_collections_1.xml, and so on. You can't customise it on Shopify, which is actually convenient — you always know where it is.

Wix and Squarespace

Both expose /sitemap.xml automatically and don't let you move it. Squarespace also responds to /sitemap.xml for every site by default.

Webflow

/sitemap.xml, but note Webflow only auto-generates it when the setting is enabled in Project Settings → SEO. On some plans you have to paste a sitemap in manually.

Custom / framework sites

Static-site frameworks (Next.js, Nuxt, Astro, Hugo) usually emit /sitemap.xml at build time via a plugin. If a developer built the site, ask them — or fall back to robots.txt, which is the one place a custom setup almost always points correctly.

Still can't find it? Three fallbacks

Occasionally none of the above works. Here's what we reach for next:

Google Search Console. If you own the site, open Indexing → Sitemaps. Any sitemap that's been submitted is listed there with its exact URL and submission status. This is the source of truth for what Google is actually reading.
A site: search. Search site:example.com in Google to see what's indexed. It won't hand you the sitemap file, but it confirms whether the site is indexed at all — useful for ruling out a bigger problem.
No sitemap exists. Some small or older sites genuinely don't have one. That's not the end of the world for a handful of pages, but for anything larger it's worth generating one. Every major platform and CMS plugin can create a sitemap automatically; there's rarely a reason not to have one.

Found it — now audit it

Locating the sitemap is step one. The reason you went looking is usually step two: you want to know whether the pages in it are healthy.

This is exactly what we built SeoSitemap.app to do. Paste the sitemap URL you just found into the Sitemap Checker and it pulls every URL from the file and audits each page — up to 500 at a time — for the things that quietly hurt rankings:

Missing, empty or duplicate H1 tags across the whole site.
Title and meta description problems — too long, too short, or missing entirely.
Broken links and redirect chains that waste crawl budget.
Duplicate titles and H1s that signal keyword cannibalisation between competing pages.

Reading a sitemap by eye tells you which pages exist. Auditing it tells you which ones are actually doing their job — and that's the difference between a list of URLs and an SEO action plan.

Key takeaways

Try /sitemap.xml and /sitemap_index.xml first; the _index version means the site splits its sitemap into chunks.
robots.txt is the most reliable place to find the declared sitemap location — look for the Sitemap: line.
Most platforms (WordPress, Shopify, Wix, Squarespace, Webflow) expose the sitemap at a predictable path.
If all else fails, Google Search Console shows the exact sitemap Google is reading.
Finding the sitemap is just the start — audit the pages inside it to turn that list into something actionable.