- Most platforms create a sitemap automatically. Find it before you build one.
- Submit it once in Search Console's Sitemaps report; Google rechecks it on its own.
- Your sitemap should list only live, indexable pages: no redirects, 404s or noindex pages.
- A submitted sitemap helps Google find pages, but doesn't guarantee they'll be indexed.
What a sitemap does
An XML sitemap is a file that lists the pages on your site you want search engines to find, often with the date each was last changed. Google can discover pages by following links, but a sitemap helps it find pages faster and more reliably, especially on new sites, large sites, or sites where some pages aren't well linked.
Submitting a sitemap doesn't guarantee indexing. Google still decides which pages to index based on their quality and usefulness. But it removes one obstacle, and Search Console's report then shows you how Google is processing it.
Step 1: Find your sitemap
Most platforms create one automatically. Try these addresses in your browser:
| Platform | Usual sitemap address |
|---|---|
| WordPress (built in) | yourdomain.com/wp-sitemap.xml |
| WordPress with Yoast SEO | yourdomain.com/sitemap_index.xml |
| WordPress with Rank Math | yourdomain.com/sitemap_index.xml |
| Webflow | yourdomain.com/sitemap.xml (switch on auto-generate in Site settings, SEO) |
| Squarespace | yourdomain.com/sitemap.xml |
| Wix | yourdomain.com/sitemap.xml |
| Shopify | yourdomain.com/sitemap.xml |
| HubSpot | yourdomain.com/sitemap.xml |
You can also check yourdomain.com/robots.txt, which often lists the sitemap address on a Sitemap: line.
If you see a page of XML or a list of links, you've found it. If you get a 404, check your platform's SEO settings, or ask your developer.
Step 2: Check it before you submit it
Open the sitemap and spot-check it. It should:
- List your important pages: homepage, services, key guides.
- Not list pages you don't want indexed: thank-you pages, test pages, tag archives, admin pages.
- Use your preferred domain: https, and www or non-www consistently.
- Contain only working URLs. Each should load normally, not redirect or return a 404.
A single sitemap can hold up to 50,000 URLs or 50MB uncompressed. Larger sites split them up with a sitemap index, which most plugins do automatically.
Step 3: Submit your sitemap to Google
- Open Google Search Console and select your property. If you haven't set one up, add your site and verify it first; see how to get your website on Google.
- In the left menu, under Indexing, choose Sitemaps.
- Under Add a new sitemap, enter the sitemap address (for example
sitemap_index.xml) and select Submit. - Check the status in the Submitted sitemaps table. It may say "Success" straight away, or take a little while to process.
That's it. You don't need to resubmit every time you publish a page; Google rechecks submitted sitemaps periodically. Resubmit if the sitemap's address changes, or after a big restructure.
Google retired its old sitemap "ping" address in 2023, so submitting in Search Console (or listing the sitemap in robots.txt) is the way to tell Google about it.
Step 4: Fix sitemap errors
| Status or error | What it means | How to fix it |
|---|---|---|
| Success | Google read the sitemap | Nothing; check the number of discovered pages looks right |
| Couldn't fetch | Google couldn't download the file | Check the address loads in a private browser window; make sure robots.txt doesn't block it and the server isn't blocking Googlebot; if it's newly submitted, wait a day and check again |
| Has errors | Google read it but found problems | Open the sitemap in the report to see the errors |
| Sitemap is HTML | You submitted a web page, not an XML sitemap | Submit the XML file's address instead |
| Invalid URL / URL not allowed | URLs don't match the property's domain or protocol | Make sure every URL uses the same domain and https as your property |
| Invalid date | The last modified date isn't in a valid format | Usually a plugin issue; update or switch plugin |
| Too many URLs / sitemap too large | Over 50,000 URLs or 50MB | Split into several sitemaps with a sitemap index |
"Couldn't fetch" on a brand-new submission is common and often clears up on its own. If it persists, test the sitemap URL with URL Inspection, which shows whether Google can reach it.
Step 5: Check which pages get indexed
After a few days, open Indexing, Pages in Search Console. You can filter the report by sitemap to see how many submitted pages are indexed and why others aren't. Our guide to the page indexing report explains each status.
To speed up an important new or updated page, paste its URL into URL Inspection and select Request indexing.
Questions
How do I submit a sitemap to Google?
In Google Search Console, go to Indexing, then Sitemaps, enter your sitemap's address and select Submit. Then check the status in the Submitted sitemaps table.
Where do I find my sitemap?
Try yourdomain.com/sitemap.xml, /sitemap_index.xml or /wp-sitemap.xml, or look for a Sitemap: line in yourdomain.com/robots.txt. Most website platforms create one automatically.
What does "Couldn't fetch" mean in Search Console?
Google couldn't download the sitemap. Check it loads in a browser and isn't blocked by robots.txt or your server. If it was only just submitted, wait a day; the status often updates on its own.
How often should I resubmit my sitemap?
Usually never. Google rechecks submitted sitemaps automatically. Resubmit only if the address changes or you've restructured the site.
Does submitting a sitemap get my pages indexed?
It helps Google find them, but Google still decides which pages to index. Pages need to be accessible, indexable and useful.
Every guide is checked against the platform it describes before it’s published, and re-checked when the platform changes.