An XML sitemap is a machine-readable list of the important pages on your website. You create it, check that it lists only pages you want indexed, and submit it in Google Search Console so Google can discover those pages faster. Submitting a sitemap does not guarantee indexing or ranking — it guarantees discovery.
What a sitemap is — and what it is not
A sitemap tells a search engine which URLs exist on your site and when they were last modified. It is especially useful when a site is new, publishes often, has many pages, or has pages that are not well linked from other pages.
It is not a shortcut around quality. Google still decides, page by page, whether a URL is worth indexing. A page that is thin, duplicated, blocked, or redirected will not become indexable just because it appears in a sitemap. That distinction matters: a sitemap helps Google find your good pages sooner; it does not make weak pages good.
A sitemap index is a “map of sitemaps.” Large or plugin-generated setups split URLs by type — posts, pages, categories — and the index points to each child file. Submit the index only, not every child file individually; Search Console will show the child sitemaps inside it.
Step 1: Find or create your sitemap
WordPress (the common case)
WordPress 5.5 and later includes a built-in sitemap, normally at /wp-sitemap.xml. If you use an SEO plugin such as Yoast SEO or Rank Math, the plugin replaces the core sitemap with its own, normally at /sitemap_index.xml, and updates it automatically whenever you publish, edit, or delete content. Use only one sitemap system at a time — running two plugins that both generate sitemaps will cause conflicts.
To confirm yours, open your site in a browser and try the path that matches your setup. If the URL shows an XML file listing your posts and pages, you already have a sitemap and do not need to build one by hand. For Rank Math, the sitemap module and its settings live under Rank Math > Sitemap Settings; for Yoast, under SEO > Settings > Site features, with XML sitemaps toggled on.
Non-WordPress or hand-built sites
If your site has no automatic sitemap, generate one with your CMS, static-site generator, or a sitemap generator tool, then upload the resulting XML file to your site’s root. A minimal sitemap entry looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/a-helpful-page/</loc>
<lastmod>2026-11-02</lastmod>
</url>
</urlset>Keep each sitemap file under 50,000 URLs and 50 MB (uncompressed), use UTF-8 encoding, and escape special characters in URLs — an & in a URL must appear as & in XML, or the file will fail to parse.
Step 2: Run the pre-submission audit checklist
Do this before you submit, because most sitemap errors are preventable at this stage:
- Every URL returns 200. Open the sitemap and spot-check entries. Remove 404s, server errors, and redirects — a sitemap should list final, live URLs only.
- Every URL is canonical. If a page has a canonical tag pointing elsewhere, list the canonical URL, not the duplicate.
- Nothing blocked or noindexed. Remove URLs blocked by robots.txt and pages marked noindex. Submitting a URL you have told Google not to index is a contradiction, not a request.
- Only pages you want indexed. Exclude login pages, admin pages, thank-you pages, staging URLs, tag or author archives you do not want in search, and any page you would not want a stranger to land on from Google.
- The XML itself is valid. No whitespace or blank line before <?xml, correct namespace, valid dates, and no unescaped characters.
- The sitemap is reachable. It must load in a browser without a login screen, a maintenance page, or a firewall block. A sitemap that serves HTML instead of XML will be reported as unreadable.
If your site already has a sitemap that updates automatically — as WordPress plugin sitemaps do — this checklist is still worth running after a redesign, a migration, or a plugin change, when stale URLs are most likely to creep in.
Step 3: Submit it in Search Console
- Open Google Search Console and select the correct property. A Domain property covers all protocols and subdomains; a URL-prefix property covers only the exact prefix you verified.
- In the left menu, go to Indexing > Sitemaps.
- In “Add a new sitemap,” enter just the path — for example sitemap_index.xml or sitemap.xml — and click Submit.
- Optionally, add a Sitemap: line to robots.txt pointing to the full sitemap URL, so other search engines can find it too.
If the sitemap was already submitted, resubmitting the same URL prompts Google to fetch it again. That is the correct move after fixing errors — but do not resubmit repeatedly in the hope of faster indexing. One clean submission, then patience, is the whole technique.
Step 4: Read the status, then act on it
Search Console shows one status per submitted sitemap:
| Status | What it means | What to do |
|---|---|---|
| Success | The file was loaded and processed without errors, and its URLs are queued for crawling. | Nothing, except checking back after major site changes. |
| Has errors | The file was fetched, but some entries are invalid. URLs that could be parsed are still used. | Open the details, fix only the listed entries, validate, and resubmit. |
| Couldn’t fetch | Google could not download the file at all. | Check the URL in a browser: a wrong path, a 404 or 500 error, a timeout, a firewall rule, or a robots.txt block are the usual causes. Fix the cause, then resubmit. |
Wait a few days after submitting or resubmitting before judging the result; a new submission’s status often takes 24–48 hours or more to settle. After that, use the Page indexing report filtered by the sitemap to see how many submitted URLs are actually indexed and why the rest are not — that report, not the sitemap status, is where indexing problems show up.
What submission does and does not do
Submission does: tell Google where your sitemap lives, trigger a fresh fetch, and give you a status report and a discovered-URL count to monitor.
Submission does not: guarantee that any URL will be crawled on a schedule, indexed, or ranked; fix thin or duplicate content; override a noindex tag or a robots.txt block; or remove pages from the index if you later delete the sitemap from the report. Removing a sitemap from Search Console only stops tracking it — it does not deindex its pages.
Common mistakes
- Submitting every child sitemap. Submit the index. Search Console expands it for you.
- Submitting the wrong property’s URL. A sitemap submitted to a URL-prefix property must live under that prefix.
- Leaving old sitemaps listed. Remove dead sitemap URLs from the report so they stop showing errors.
- Treating “Success” as “indexed.” Success means the file was read. Indexing is a separate, per-page decision — which is why the indexing workflow in our guide to getting your website indexed by Google covers verification, blockers, and internal linking alongside the sitemap step.
FAQs
Where do I submit my sitemap in Search Console?
In the property for your site, go to Indexing > Sitemaps, enter the sitemap path (for example sitemap_index.xml), and click Submit. You need Owner or Full user permission on the property to do this.
Does submitting a sitemap guarantee indexing?
No. A sitemap guarantees discovery, not indexing. Google indexes a page only if it can crawl it, finds it accessible and canonical, and judges it useful enough to include. If submitted pages are not appearing, diagnose the cause in the Page indexing report rather than resubmitting — our guide to why a website is not showing up on Google walks through the broader checks.
What URLs should not be in a sitemap?
Redirects, 404s, noindex pages, robots.txt-blocked pages, login and admin pages, staging URLs, and duplicates whose canonical points elsewhere. A sitemap should contain only live, canonical, indexable URLs you want people to find in search.
How often should I update my sitemap?
As often as your content changes. Plugin and CMS sitemaps do this automatically. Hand-built sitemaps need a rebuild after every publish, edit, or deletion — which is the strongest reason to switch to an automatic one if you publish regularly.
I fixed the errors — what now?
Validate the file, resubmit the same URL in the Sitemaps report, and check back in a few days for a Success status and a recent last-read date. Then watch the Page indexing report for the pages themselves.
Next step
Once your sitemap is submitted and clean, the remaining work is on the pages: making sure each one is crawlable, canonical, and worth indexing. The Search Console reports explained in our Google Search Console guide are the place to monitor that — sitemap status for discovery, the Page indexing report for everything after it.
