How to Find a Website’s Sitemap
Seven reliable ways to locate public XML sitemaps, including the cases where the familiar /sitemap.xml path does not exist.
Key takeaways
- Check robots.txt before guessing paths.
- A sitemap index can point to many child sitemaps.
- CMS-specific paths are useful clues, not universal rules.
- Automated discovery should validate XML roots instead of trusting filenames.
Start with robots.txt
Open the site's /robots.txt file and look for one or more Sitemap directives. The value is normally an absolute URL and can point to either a sitemap or a sitemap index. This is the most reliable public hint because site owners can declare non-standard locations there.
User-agent: *
Allow: /
Sitemap: https://example.com/sitemap_index.xmlTry the common public paths
If robots.txt contains no declaration, test a small set of conventional paths. Do not assume a 200 response is valid: some sites return an HTML error page with status 200, so inspect the content type and verify that the document contains a urlset or sitemapindex root.
- /sitemap.xml
- /sitemap_index.xml
- /sitemap-index.xml
- /sitemaps.xml
- /wp-sitemap.xml
Recognize CMS and framework conventions
WordPress commonly exposes /wp-sitemap.xml or a plugin-generated /sitemap_index.xml. Shopify stores a sitemap at /sitemap.xml. Other platforms may generate files dynamically or expose a custom index. Platform detection narrows the search, but robots.txt and content validation remain the source of truth.
Use first-party tools when you own the site
Search Console's Sitemaps report shows submitted files and processing status. Your CMS, deployment pipeline, or SEO plugin may also expose the generated location. This is preferable to guessing because private staging rules, reverse proxies, and subfolder installations can change the public path.
Automate discovery without creating crawl noise
A responsible finder checks robots.txt, follows declared sitemap URLs, probes a bounded list of common paths, and stops when it has enough evidence. It should deduplicate normalized URLs, follow sitemap indexes recursively with limits, reject non-HTTP targets, and use short timeouts.
The SitemapKit Finder is optimized for this discovery task. Use the Crawler when you also need to map child indexes and count their URLs, and use the Extractor when you already know the sitemap URL and want the entries.
Discover declared and common sitemap locations automatically.
Open the free toolFrequently asked questions
Is a sitemap always located at /sitemap.xml?
No. That path is common, but a site can publish a sitemap anywhere it controls and can declare multiple files in robots.txt.
Can a website have more than one sitemap?
Yes. Large sites often split URLs by content type or locale and connect the files through a sitemap index.
What if every sitemap path returns 404?
The site may not publish a sitemap, may restrict access, or may use an undisclosed location. Internal links can still make the site crawlable.
Primary references
- Google Search Central: robots.txt specifications
- Google Search Central: Manage sitemaps with Search Console
See our technical methodology and editorial policy.