How to Submit Sitemap to Google Search Console (Step by Step)

Here is how to submit sitemap to Google Search Console: open the Sitemaps report under Indexing, paste the full URL of your sitemap into Add a new sitemap, and click Submit. Submitting is not an upload. It only tells Google where the file lives on your site, and Google fetches it from there. The whole thing takes under 60 seconds once the file is live and reachable.

The part that trips people up is everything around that button. Which URL do you paste on WordPress? What does “Couldn’t fetch” mean?

I’ve worked in SEO for 8 years, and the same four questions decide the path every time.

What Decides Your Path Before You Click Submit?

Four variables change what you should do. Check them first and the rest of this guide becomes a short route instead of a guessing game.

1. Your permission level. The Sitemaps report needs owner permissions. Full or restricted users can’t submit, so they take the robots.txt route instead.
2. What builds your sitemap. WordPress core, Yoast SEO, Rank Math, Shopify or a hand-made file all publish it at a different URL.
3. Your site’s size. One sitemap holds at most 50,000 URLs or 50MB uncompressed. Bigger sites need a sitemap index.
4. Whether the sitemap URL redirects. Google’s Sitemaps report does not follow redirects for the URL you submit, so you want the final address.

If you’re an owner, on a site under 50,000 URLs, and you know the final sitemap URL, you’re on the main path below. Anything else, jump to the branch that matches.

How to Submit Sitemap to Google Search Console in Five Steps

These steps follow Google’s own Sitemaps report help page, with the checks I add on client sites.

1. Find your sitemap URL. Open yourdomain.com/robots.txt first. Most CMSs and SEO plugins list the sitemap there on a Sitemap: line.
2. Open the URL in a browser. You should see XML, not a 404 page or a login screen. If your browser follows a redirect, copy the final address from the address bar.
3. Run a live test in URL Inspection. Paste the sitemap URL into the inspection bar, run the live test, and confirm Page fetch says “Successful”. This is the step most tutorials skip.
4. Submit it. Go to Indexing, then Sitemaps, paste the URL into Add a new sitemap, and click Submit.
5. Check the status. Refresh the report and look at the Status column. You want “Success”.

Step 3 is the one I’d never skip. When a sitemap “won’t submit”, the live test usually shows the real reason in seconds. Typical culprits are a security plugin blocking Googlebot, a staging password left on, or a robots.txt rule.

Before step 4, check you’re in the right property. The report only lists sitemaps for the property you have open, and Google’s help warns that http vs https and www vs non-www versions count as different properties. A Domain property covers all of them at once, which is why I set one up on every new site.

Google says it fetches the sitemap right after you submit. Crawling the URLs inside it is a different matter. That can take much longer, and Google’s help page is clear that not every URL in a sitemap will be crawled.

Which Sitemap URL Should You Submit on WordPress?

This is where most WordPress mistakes happen. WordPress has shipped its own sitemap since version 5.5, at /wp-sitemap.xml. SEO plugins replace it with their own, usually at /sitemap_index.xml.

Here’s the trap. When I checked yoast.com and rankmath.com, both answered /wp-sitemap.xml with a 301 redirect to /sitemap_index.xml. My own site does the same thing, and its robots.txt points straight at /sitemap_index.xml.

That redirect is fine for crawlers following links. It isn’t fine for the Sitemaps report. Google’s help page says the report shows the exact URL you submitted and that redirects are not followed, so always paste the final /sitemap_index.xml address when a plugin is active.

Shopify owners have it easier, because the sitemap is one of several SEO basics the platform switches on by default, as I explain in is Shopify good for SEO. Shopify’s help center says every store builds sitemap.xml on its own and keeps it current, so you just type sitemap.xml into the report. Stores on several international domains need one submission per domain, and a store kept private can’t be crawled at all.

One more WordPress check. If Settings, Reading, Search engine visibility is ticked, core WordPress switches its sitemap off entirely. It’s a common leftover from a staging copy, and no sitemap submission fixes it.

What Should Actually Be Inside the Sitemap?

A clean file beats a big one. I only want URLs that return a 200 status, are indexable, and are the canonical version of the page. Redirects, 404s, noindexed thank-you pages, tag archives you don’t want ranking, and URLs with tracking parameters all waste Google’s attention.

Why be strict? Because Google reads your sitemap as a list of pages you’d like in search. Every junk URL in it muddies that message. It also makes the Page indexing report harder to read later, since excluded URLs you never cared about pile up next to the ones you do.

Plugins handle most of this for you. Yoast, for example, leaves noindexed pages out automatically. Still, open the file once after setup and scan it. Five minutes of reading beats months of guessing.

What If You Don’t Have Owner Access in Search Console?

Then you can’t use the Sitemaps report at all. Google’s documented alternative is to list the sitemap in your robots.txt file, which any crawler that reads robots.txt can pick up.

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://example.com/sitemap_index.xml

Google’s robots.txt rules say the Sitemap: line needs a fully qualified URL, isn’t tied to any user agent, and can appear as many times as you need. Put it at the bottom. It works for Bing and other major engines too.

The downside is visibility. The Sitemaps report only lists sitemaps submitted through the report or the API, so a robots.txt-only sitemap won’t show a status or error count. My advice: ask the owner to add you as an owner, or ask them to submit it once so you can track it.

Does a Large Site Need a Sitemap Index?

Only if you cross the limits. Google’s build and submit a sitemap docs set the same cap for every format.

If you pass either sitemap limit, split the file and list the parts in a sitemap index. Then submit only the index. Google reads the children from it, and the Discovered pages column counts every URL across all of them.

You can also split on purpose while under the limits. Google’s docs note that submitting several sitemaps can help you track each one separately in Search Console. I like one child sitemap per content type, so posts, pages and products each get their own row and their own error count.

Honestly, most small business sites never get close. Google’s own sitemap overview says a site with about 500 pages or fewer that is well linked internally might not need a sitemap at all. I still add one, because the Sitemaps report and the sitemap filter in the Page indexing report give you a cheap health check.

What Does “Couldn’t Fetch” Mean, and How Do You Fix It?

The report shows one of three statuses for the latest request. Here’s what each means and what I do next.

“Couldn’t fetch” has a short list of documented causes. Work through them in this order:

• Blocked by robots.txt. Google respects robots.txt when fetching sitemaps, so a stray Disallow kills it.
• Wrong URL. A typo or old path returns a 404. Open it in a browser.
• Unresolved manual action. Google doesn’t read sitemaps while one is open. Check the Manual actions report.
• A general or server error. Some are temporary. Wait and see if later attempts succeed.
• Low crawl demand. Google ties this to content quality, and no setting fixes it.

For “Has errors”, the usual suspects are URLs outside the sitemap’s scope, relative URLs, too many redirects inside the file, or a broken gzip file. If Google keeps failing, it retries for a few days and then stops. Fix the problem, then resubmit.

Can You Still Ping Google When Your Sitemap Changes?

No. On June 26, 2023, Google announced it was retiring the sitemaps ping endpoint, and said it would stop working in 6 months. The deprecation post on Google Search Central now carries a banner saying the deprecation is complete.

Old plugins that still ping don’t hurt anything. The request just returns a 404. What matters now is an honest lastmod date. Google says it uses lastmod for scheduling crawls when the dates match reality, and it ignores changefreq and priority completely.

Google also means last significant change. Rewriting the main text, changing structured data or updating links counts. A tweak in the sidebar or footer doesn’t, and a site that bumps every date daily teaches Google to stop believing its dates.

So don’t spend time tuning priority values. Spend it making sure your CMS only bumps lastmod when the main content really changed.

The Decision Matrix

That last row is its own problem. A sitemap gets URLs discovered. It doesn’t force indexing, and Google calls a submission “merely a hint”. If your report shows URLs stuck as discovered, my post on Discovered, Currently Not Indexed covers that status.

When Should You Hand This to a Technical SEO?

Submitting a sitemap is a five-minute job. Escalate when the sitemap is the symptom, not the cause: a manual action, a server that times out for Googlebot, thousands of redirecting or noindexed URLs inside the file, or a migration that changed every path.

That’s work for a technical SEO who can read server logs and crawl data, not another resubmit. My technical SEO checklist covers the wider crawl checks. If you’d rather have my team review the whole setup, our complete SEO service starts with a free audit.

Once the sitemap shows “Success”, the next report worth learning is Performance. I explain it in my Google Search Console performance report guide.

Frequently Asked Questions

Do I Need to Resubmit My Sitemap After Every New Post?

No. Google recrawls a sitemap it has already read on its own schedule. Resubmit only after big changes, like a migration or a new sitemap structure, or after you fix an error.

How Long Does Google Take to Read a Submitted Sitemap?

Google says it tries to fetch a sitemap as soon as you submit it. If the status still looks empty after a few days, run the live URL Inspection test. Crawling and indexing the URLs inside it takes longer and isn’t guaranteed.

Does Removing a Sitemap Stop Google From Crawling Those URLs?

No. Removing a sitemap only takes it out of the report. Google doesn’t forget the URLs. To stop crawling, use a robots.txt rule, delete the pages, or add noindex.

Can I Submit More Than One Sitemap?

Yes. You can submit several sitemaps or sitemap index files, up to 500 index files per site. The report shows a maximum of 1,000 submitted requests, so a single index keeps things tidier.

Last updated: September 2026 by Mizanur Rahman