How to Find the Sitemap of Any Website
Five reliable methods to find any website's sitemap: checking common URLs, reading robots.txt, using Google Search Console, using tools, and what to do when there's no sitemap.
You need to find a website's sitemap. Maybe you're auditing a competitor, diagnosing crawl issues on your own site, or trying to understand the structure of a site before a migration. Sitemaps aren't always obvious, but they're almost always findable if you know where to look.
Here are five methods, starting with the quickest.
Method 1: Check the Common URLs
Most sitemaps live at predictable locations. Try these URLs in your browser, replacing example.com with the domain you're investigating:
Try /sitemap.xml
Visit https://example.com/sitemap.xml. This is the most common location by far. If the site has a sitemap, there's a good chance it's here.
Try /sitemap_index.xml
Large sites often use a sitemap index that references multiple sitemap files. Check https://example.com/sitemap_index.xml.
Try CMS-specific paths
Different platforms use different default locations:
- WordPress (Yoast):
/sitemap_index.xml - WordPress (core):
/wp-sitemap.xml - WordPress (Rank Math):
/sitemap_index.xml - Shopify:
/sitemap.xml - Wix:
/sitemap.xml - Squarespace:
/sitemap.xml - Webflow:
/sitemap.xml - Drupal:
/sitemap.xml - Magento:
/sitemap.xmlor/pub/sitemap.xml
Try other common variations
Some sites use non-standard paths:
/sitemap//sitemap.xml.gz(compressed)/sitemaps/sitemap.xml/sitemap1.xml/page-sitemap.xml/post-sitemap.xml
If any of these return XML content with <urlset> or <sitemapindex> tags, you've found the sitemap. If you get a 404 page, move on to the next method.
Method 2: Check robots.txt
The robots.txt file often declares the sitemap location. This is actually the "official" way for sites to advertise their sitemaps.
Visit https://example.com/robots.txt in your browser. Look for a line that starts with Sitemap::
User-agent: *
Disallow: /admin/
Disallow: /private/
Sitemap: https://example.com/sitemap.xml
Sitemap: https://example.com/sitemap-news.xml
A site can declare multiple sitemaps in robots.txt. Each Sitemap: line points to a different sitemap file. This is especially common for sites that have separate sitemaps for different content types (pages, blog posts, news, images).
The Sitemap directive is case-insensitive for the directive name
The protocol specifies Sitemap: with a capital S, but most crawlers accept any casing. The URL itself, however, is case-sensitive on most servers. sitemap.xml and Sitemap.xml could be different files.
Method 3: Use Google Search Console
If you own the site (or have access to its Search Console account), this is the most authoritative source.
Log into Google Search Console
Go to search.google.com/search-console and select your property.
Navigate to Sitemaps
In the left sidebar, click "Sitemaps" under the "Indexing" section.
View submitted sitemaps
You'll see a list of all sitemaps that have been submitted for this property, along with their status, the number of discovered URLs, and the last time Google fetched each one.
This shows you exactly what Google knows about your sitemaps. If a sitemap was submitted years ago and never updated, you'll see that here. If there are errors, they'll be flagged.
Found a sitemap? Validate it.
Check your sitemap for errors, broken URLs, and indexing issues before they affect your search visibility.
Method 4: Use a Google Search Operator
You can use Google itself to find sitemaps, even for sites you don't own.
Try this search query:
site:example.com filetype:xml inurl:sitemap
This searches for XML files on the domain that have "sitemap" in the URL. It doesn't always work -- Google doesn't index every sitemap file -- but it catches a good number of them.
You can also try:
site:example.com "sitemap" "urlset"
This looks for pages containing sitemap-related keywords, which sometimes surfaces sitemap files that have been inadvertently indexed.
Method 5: Use a Crawling Tool
If the above methods come up empty, a crawling tool can check multiple potential sitemap locations automatically and also discover sitemaps linked from the HTML of the site.
Screaming Frog will find sitemaps during a crawl and report them in the Sitemaps tab. Sitebulb does the same. Even a simple curl command can check multiple URLs quickly:
# Check common sitemap locations
for path in sitemap.xml sitemap_index.xml wp-sitemap.xml sitemap.xml.gz; do
status=$(curl -o /dev/null -s -w "%{http_code}" "https://example.com/$path")
echo "$path: $status"
done
A 200 response means the file exists. A 404 means it doesn't. A 301 or 302 means it redirects somewhere else -- follow the redirect to find the actual sitemap.
What You're Looking At
Once you find the sitemap, you'll encounter one of two things:
A Sitemap Index
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://example.com/sitemap-pages.xml</loc>
<lastmod>2026-02-15</lastmod>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap-posts.xml</loc>
<lastmod>2026-02-18</lastmod>
</sitemap>
</sitemapindex>
This is a parent file that references child sitemaps. Click into each child sitemap to see the actual URLs.
A Regular Sitemap
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-02-10</lastmod>
</url>
<url>
<loc>https://example.com/about</loc>
</url>
</urlset>
This lists individual page URLs directly. Small sites may have just one of these. Large sites may have dozens referenced by an index.
What to Do When There's No Sitemap
Sometimes a site genuinely doesn't have a sitemap. This is more common than you'd expect, especially with custom-built sites or older projects. Here's what to do depending on your situation:
If it's your own site
Create one. You have four options:
Install a CMS plugin
Use an online generator
Generate programmatically
Write one by hand
If it's someone else's site
You have limited options, but you can still map the site's structure:
- Use a crawler. Tools like Screaming Frog or Sitebulb will crawl the site and build a list of all discoverable pages. This gives you the same information a sitemap would, just gathered differently.
- Check the Wayback Machine. The Internet Archive sometimes captures sitemap files. Visit
web.archive.org/web/*/example.com/sitemap.xmlto check for historical snapshots. - Use Google's cache. Search for
cache:example.com/sitemap.xmlto see if Google has a cached version.
Common Sitemap Locations Quick Reference
| Platform | Default Sitemap URL | Customizable? |
|---|---|---|
| WordPress (core) | /wp-sitemap.xml | Limited |
| WordPress (Yoast) | /sitemap_index.xml | Yes |
| Shopify | /sitemap.xml | No |
| Squarespace | /sitemap.xml | No |
| Wix | /sitemap.xml | Limited |
| Webflow | /sitemap.xml | Per-page toggle |
| Drupal | /sitemap.xml | Yes (with module) |
| Magento | /sitemap.xml or /pub/sitemap.xml | Yes |
| Ghost | /sitemap.xml | Limited |
| Custom/Static | Varies | Fully |
Key Takeaways
Finding a sitemap usually takes under 30 seconds: check /sitemap.xml, check robots.txt, done. When it's not that simple, the methods above cover every edge case. And if you discover that a site -- especially your own -- doesn't have a sitemap at all, that's a clear signal to create one. Search engines can discover pages without sitemaps, but you're making their job harder than it needs to be.
Related Articles
Finding a sitemap takes 30 seconds. Not having one costs you crawl coverage every single day.
Validate your XML sitemap
Check your sitemap for errors, broken URLs, and indexing issues. Free instant validation.