Part of the SiteMap Series
Most websites already have a sitemap. The platform you built your site on probably generated one automatically. The plugin you installed for SEO probably added another. Your developer might have configured one years ago without telling you. The first practical step in any sitemap project is not building. It’s finding what already exists.
Skipping this step is what gets people into trouble. They install a plugin and create a sitemap, not realising the site already had one. Now they have two competing files, both auto-updating, and the search engines have to decide which one to trust. Or they ask their developer to build one without checking the CMS, when the CMS has been generating a perfectly good sitemap all along.
This lesson walks through four methods for finding a sitemap, in order of speed and reliability. They work on your own site, on a competitor’s site, and on a client site you have just been handed. By the end, you will have a reliable diagnostic process you can run on any website in under five minutes.
Why finding comes first
Building a sitemap before checking what exists treats every site like a blank slate. Real Technical SEO does not work that way. The reason for this lesson is in one of three situations: they have a working sitemap and do not know it, they have a broken or outdated sitemap and do not know it, or they genuinely have no sitemap at all. Each situation needs a different response, and you cannot pick the right response until you know which one you are in.
The find step is also a forever skill. You will use it on every site you audit, every competitor you research, and every client you take on. Building a sitemap is a one-time task. Finding one is something you do constantly throughout your career.
Method 1: Try common sitemap URLs directly
The fastest check takes about ten seconds. Open a new browser tab, type the domain followed by /sitemap.xml, and look at what loads. If a valid XML sitemap appears, you have found it. If a 404 page appears, that exact URL does not exist, but the sitemap might still live somewhere else.
These are the common locations to try, in order of likelihood:
/sitemap.xml/sitemap_index.xml/sitemap-index.xml/wp-sitemap.xml/sitemap1.xml
The first three are the most common. /wp-sitemap.xml is the path used by WordPress 5.5 and later when no SEO plugin is active. /sitemap1.xml is occasionally used by older configurations or by sites that built their sitemap manually.
A few patterns worth knowing. If the URL returns a sitemap index file (containing references to other sitemaps rather than a list of pages), follow one of the links inside to see the actual URL listings. If the URL redirects somewhere else, follow the redirect, because the destination is your real sitemap location. If the URL loads but the page looks like styled HTML rather than raw XML, your site is probably running an HTML sitemap plugin, which is a different beast and was covered back in Lesson 3 of Module One.
Method 2: Check the robots.txt file
Direct URL checks are fast, but they assume you know where to look. The proper way to find a sitemap is to check the robots.txt file, because that is the standardised place where sitemap locations are declared.
Visit your domain followed by /robots.txt. You will see a plain text file. Somewhere inside it, you should find one or more lines that look like this:
Sitemap: https://example.com/sitemap_index.xml
That line tells you exactly where the sitemap lives. If the site has multiple sitemaps (large sites often do, and we will cover why later in the module), you will see multiple Sitemap directives, one per line. Each one points to a different sitemap file.
This is the most reliable method because the Sitemap directive is part of the official sitemaps.org protocol. Any properly configured site will declare its sitemap location here. Search engines themselves use this method to find sitemaps when they have not been told the location any other way.
What if robots.txt exists but has no Sitemap line? The sitemap might still exist (the declaration is recommended but not required), so fall back to Method 1 and try the common URLs.
Method 3: Look in Google Search Console
If you have Search Console access for the site, the Sitemaps report tells you exactly which sitemaps Google has been informed about. This is the most authoritative source for your own sites because it shows what is actually being processed.
To get there, open Search Console, select the property, and click Sitemaps in the left sidebar under the Indexing section. You will see a list of submitted sitemap URLs with their status (success, has errors, could not fetch), the date Google last read each one, and how many URLs were found inside.
This report has limits worth understanding. It only shows sitemaps that have been submitted to Google. A site might have a perfectly good sitemap that nobody ever submitted, in which case the report will be empty even though a sitemap exists. It also only works for properties you have verified access to, so it will not help you investigate a competitor’s sitemap or any site you do not own.
For competitor research or audits on sites you do not own, Methods 1 and 2 are your tools.
Method 4: Find it through your CMS
If the direct URL and robots.txt checks both come up empty, the next step is to look inside the CMS itself. Most modern platforms generate a sitemap automatically, and the exact location depends on which platform and which plugins are active.
These are the default sitemap locations by platform:
- WordPress with no SEO plugin:
/wp-sitemap.xml(native, since WordPress 5.5) - WordPress with Yoast SEO:
/sitemap_index.xml - WordPress with Rank Math:
/sitemap_index.xml - WordPress with All in One SEO:
/sitemap.xml - Shopify:
/sitemap.xml(generated automatically, cannot be disabled) - Wix:
/sitemap.xml - Squarespace:
/sitemap.xml - Webflow:
/sitemap.xml - Ghost:
/sitemap.xml
For WordPress sites running an SEO plugin, the plugin almost always overrides the native WordPress sitemap. So if Yoast is installed, the native /wp-sitemap.xml is disabled and Yoast’s /sitemap_index.xml takes over. This is the most common reason people get confused about which URL to check.
If you are logged into the CMS, the SEO plugin’s settings page usually has a link to the active sitemap. In your Yoast settings, find the XML Sitemaps section. In Rank Math, look under Sitemap Settings. In All in One SEO, check the Sitemaps tab. The exact menu paths change between versions, but every reputable SEO plugin makes the active sitemap easy to access from inside the admin area.
What to do if you cannot find one
If all four methods come up empty, there are three possible explanations. The most common is that no sitemap exists. Some sites simply do not have one, particularly older sites or those built without an SEO-aware CMS.
The second possibility is that the sitemap lives at a custom location that does not match any of the conventions. This is rare but happens when a developer manually configured a sitemap and chose an unusual path. In this case, ask the developer or check whatever technical documentation the site has.
The third possibility is that the sitemap exists but is blocked from public access. This is also rare and usually points to a misconfiguration. Check robots.txt for a Disallow directive that might be hiding it, and check server-level settings if you have access.
If you have ruled out custom locations and blocking, you almost certainly have no sitemap. The building lessons later in this module will show you how to create one. For now, you have done the diagnostic work, and that is what matters.
Where this leaves us
You now have a reliable diagnostic for finding any sitemap, on your own site or anyone else’s. Try the common URLs, check robots.txt, look in Search Console, check the CMS defaults. Four methods, about five minutes of work, and you know what you are dealing with.
Finding a sitemap is only the first step. A sitemap can exist and still be wrong. The URLs inside might point to pages that no longer exist. Important pages might be missing. The formatting might be quietly broken in ways that make search engines ignore parts of it. The next lesson walks through how to read a sitemap properly and judge whether it is actually doing its job.
Up next: What’s Actually In Your Sitemap? →
This is Module 2: Lesson 1 of The Sitemap Series, a Technical SEO series on sitemaps from first principles, built for the AI Search era.