How to Submit a Sitemap to Google Search Console

Submitting a sitemap is one of the fastest ways to tell Google that your site exists and which pages you want it to crawl. It does not force Google to index anything, and it is not a ranking factor — but it hands search engines a clean, structured list of your URLs so they spend less time guessing and more time crawling the pages that matter. For a new WordPress site with few inbound links, that head start can shave weeks off the time it takes to get indexed.

This tutorial walks through the whole process: finding your WordPress sitemap URL, verifying your property in Search Console, submitting the sitemap, and reading the status report so you know whether Google actually accepted it. We finish with Bing Webmaster Tools, because the same file works there too.

Step 1: Find Your WordPress Sitemap URL

Before you can submit a sitemap, you need to know its exact URL. Where it lives depends on whether you run an SEO plugin.

If You Have No SEO Plugin (WordPress Core)

Since WordPress 5.5, the platform generates a sitemap automatically. If you have a plain install with no SEO plugin active, your sitemap lives at:

yourdomain.com/wp-sitemap.xml

Open that URL in a browser to confirm it loads. You will see a sitemap index that links to smaller files for posts, pages, categories, and other content types.

If You Have Yoast SEO or Rank Math

Both Yoast SEO and Rank Math generate their own sitemap and switch off the core wp-sitemap.xml automatically. Their sitemap index lives at:

yourdomain.com/sitemap_index.xml

In Yoast, confirm the feature is on under Yoast SEO → Settings and check the sitemaps toggle. In Rank Math, go to Rank Math → Sitemap Settings. If neither sitemap_index.xml nor wp-sitemap.xml loads, try yourdomain.com/sitemap.xml, then visit Settings → Permalinks and click Save Changes to refresh your rewrite rules.

The important thing at this stage is to open the URL and confirm you see structured XML — not a 404, not a redirect, not a blank page. If you want to understand what those files actually contain and how to customize them, the guide to XML sitemaps in WordPress covers the full picture. And if your sitemap loads but shows old dates or missing posts, read WordPress sitemap not updating before you submit — there is no point handing Google a stale file.

Step 2: Verify Your Property in Google Search Console

Search Console will not accept a sitemap for a site you have not proven you own. If you have not set up your property yet, you need to do that first.

1. Go to Google Search Console and sign in with a Google account.
2. Click Add property. You will see two options: Domain and URL prefix.
3. Choose one:
   • Domain covers every subdomain and both HTTP and HTTPS, but it requires adding a TXT record to your DNS settings.
   • URL prefix covers only the exact address you enter (for example https://yourdomain.com) and offers easier verification methods, including an HTML tag.
4. Verify ownership. The simplest method for most WordPress owners is the HTML tag option — Yoast SEO and Rank Math both have a field where you paste the verification meta tag, so you never touch a theme file. Alternatively, upload the HTML verification file to your site root, or add the DNS TXT record for a Domain property.

Once Search Console confirms verification, your property is live. If any of this feels unfamiliar, the WordPress SEO guide walks through Search Console setup as part of a broader first-week checklist.

Step 3: Submit Your Sitemap

With your property verified and your sitemap URL confirmed, the actual submission takes about thirty seconds.

1. In Search Console, select your property from the dropdown at the top left.
2. In the left sidebar, click Indexing → Sitemaps.
3. Under Add a new sitemap, you will see your domain already filled in with an empty field after it. Type only the path — sitemap_index.xml for Yoast or Rank Math, or wp-sitemap.xml for core WordPress. Do not paste the full https:// URL; Search Console prepends the domain for you.
4. Click Submit.

Search Console will fetch the file, count the URLs it finds, and add a row to the Submitted sitemaps table with a status. You only ever need to submit a sitemap once — Google re-fetches it on its own schedule from then on.

If you run separate sitemaps for different content — say an image sitemap or a news sitemap that your plugin generates as its own file — you can submit each one individually. For most WordPress sites, submitting the single index file is enough, because the index already points Google to every child sitemap.

Step 4: Read the Status and Coverage Report

After submission, the sitemaps table shows a few columns: the sitemap URL, the type, when it was submitted, when Google last read it, the status, and the number of discovered URLs. This is where you confirm the submission worked — and where you catch problems early.

What “Success” Means

A green Success status means Google fetched your sitemap, parsed it without errors, and read the list of URLs. The Discovered URLs column shows how many links Google found in the file.

Important distinction: “Success” means the sitemap was read successfully, not that every URL in it has been indexed. Discovery and indexing are separate steps. To see how many of those URLs are actually in Google’s index, open the Pages report (under Indexing), which breaks your pages into indexed and not-indexed buckets with reasons for each.

What “Couldn’t Fetch” Means

A Couldn’t fetch status means Google tried to reach your sitemap and failed. It does not always mean the file is broken — sometimes Google simply has not retried yet, and the status resolves itself within a day or two. But if it persists, the usual causes are:

• A wrong or mistyped URL. Open the exact address you submitted in a private browser window and confirm it returns XML.
• The server blocking Googlebot. A security plugin, firewall, or host-level rule can block crawler user agents. Check that Googlebot is allowed.
• A robots.txt block. If your robots.txt disallows the sitemap path or the URLs it lists, Google cannot fetch them.
• A redirect on the sitemap URL. The submitted URL should return the file directly with a 200 status, not redirect to another address.
• A caching or generation error producing an empty or malformed file.

Work through those, then use the Refresh or resubmit action to prompt Google to try again. For a deeper look at crawler access, redirects, and the settings that govern how Google reaches your pages, see technical SEO for WordPress.

Other Statuses You Might See

You may also encounter Has errors (the sitemap was fetched but contains invalid entries, such as URLs on a different domain) or a status showing a partial URL count. Click the sitemap row to see the specific errors Google flagged, then fix them at the source — usually in your SEO plugin’s sitemap settings.

Step 5: Resubmitting a Sitemap

You do not need to resubmit after every new post. Google revisits your sitemap automatically, and your SEO plugin pings search engines when you publish. Resubmit only when there is a real reason:

• You fixed a Couldn’t fetch or error status and want Google to retry immediately.
• You significantly restructured your site or added a large new section.
• You changed your sitemap URL — for example after switching SEO plugins or moving from core to a plugin sitemap.

To resubmit, delete the old sitemap row if the URL changed (click the row, then Remove sitemap — this only removes it from the report, it does not delete the file), then add the correct URL as a new sitemap. If the URL is unchanged and you just want a re-fetch, submitting the same path again refreshes it. Removing a sitemap from the report does not deindex your pages; it only tells Search Console to stop tracking that file.

Bonus: Submit Your Sitemap to Bing Webmaster Tools

Google is not the only search engine worth feeding. Bing powers a meaningful slice of search traffic — and, increasingly, feeds several AI answer tools — so submitting your sitemap there is a low-effort win.

1. Go to Bing Webmaster Tools and sign in.
2. You can import your site directly from Google Search Console, which carries over verification and your submitted sitemap in one step — the fastest route by far.
3. If you prefer to add it manually, enter your site URL, verify ownership (via an HTML meta tag, an XML file, or a DNS record, just like Google), then open Sitemaps and submit the same sitemap_index.xml or wp-sitemap.xml URL.

The same WordPress sitemap file works for both search engines, so there is nothing extra to generate. Bing’s report reads much like Google’s, showing submission status and discovered URL counts.

A Quick Recap

Submitting a sitemap is straightforward once you know the moving parts:

1. Find your sitemap URL — wp-sitemap.xml for core WordPress, sitemap_index.xml for Yoast or Rank Math.
2. Verify your property in Google Search Console using the HTML tag, file upload, or DNS method.
3. Submit the sitemap path under Indexing → Sitemaps.
4. Check that the status reads Success, and troubleshoot Couldn’t fetch if it appears.
5. Resubmit only when the URL changes or you fix an error.
6. Repeat the process in Bing Webmaster Tools for extra coverage.

From there, indexing is a waiting game — Google crawls on its own schedule, and a clean, accurate sitemap is the best nudge you can give it. Keep an eye on the Pages report over the following weeks to confirm your URLs move from discovered to indexed. If you want the bigger strategy around getting those pages to actually rank once they are indexed, continue with the guide on how to rank a WordPress site.

FAQ

What is the difference between wp-sitemap.xml and sitemap_index.xml?

wp-sitemap.xml is the sitemap WordPress generates natively when no SEO plugin is active. sitemap_index.xml is the sitemap created by Yoast SEO or Rank Math, which automatically disable the core version when they are active. Check which plugin (if any) you run, open the matching URL to confirm it loads, and submit that one. You should only ever have one active sitemap source.

Do I submit the full URL or just the path in Search Console?

Just the path. The Add a new sitemap field already shows your domain, so you type only sitemap_index.xml or wp-sitemap.xml after it. Pasting the full https:// address usually produces an error because the domain gets duplicated.

Why does my sitemap say “Couldn’t fetch”?

Google tried to read the file and could not. The most common reasons are a mistyped URL, a server or security plugin blocking Googlebot, a robots.txt rule blocking the path, or a redirect on the sitemap URL. Open the exact URL you submitted in a private browser window to confirm it returns valid XML with a 200 status, fix whatever is blocking access, then resubmit. Sometimes the status clears on its own within a day or two.

How long does it take Google to index my pages after I submit a sitemap?

There is no fixed timeline. Submitting a sitemap speeds up discovery, but indexing depends on your site’s authority, content quality, and how often Google crawls you — anywhere from a day to several weeks. Watch the Pages report in Search Console to track how many URLs move into the indexed bucket over time.

Do I need to resubmit my sitemap every time I publish a post?

No. Google re-fetches your sitemap automatically, and your SEO plugin notifies search engines when you publish new content. Only resubmit when you fix an error status, restructure your site significantly, or change the sitemap URL itself.