Sitemap "Couldn't fetch" in Search Console

Couldn't fetch means Google could not download your sitemap file at all. Open the address yourself, run a live test in URL Inspection, fix what blocks it, and resubmit.

Where you see it

In Search Console, open Indexing > Sitemaps. The Status column of the Submitted sitemaps table says Couldn't fetch.

What it means

Google tried to download the sitemap and got nothing it could use. It did not read any addresses from it.

Google keeps trying for a few days. If the file still fails, Google stops trying until you resubmit it.

Site owners often see Couldn't fetch on a new sitemap that opens fine. If the address opens as XML and the live test passes, resubmit it and check again in a few days.

Common causes

The address is wrong, so the server answers 404. A typo, the wrong file name (sitemap.xml versus sitemap_index.xml), or a sitemap that a plugin no longer makes.
A firewall, CDN, or bot protection blocks Googlebot. It answers 403 or 503, or shows a challenge page.
robots.txt blocks the sitemap address. Google respects robots.txt when it fetches sitemaps.
The site needs a login or a password, such as a store in private mode or a staging site.
The server was down or slow when Google asked. This kind of error can clear by itself.
The site has an unresolved manual action. Google does not read sitemaps until it is fixed.
The sitemap is submitted in the wrong property, such as http instead of https, or without www. Then the address redirects.

Find the cause

Open the sitemap address in a private browser window. You should see XML with <urlset> or <sitemapindex>, not a web page or an error.
In Search Console, paste the sitemap address into the URL Inspection bar and click Test live URL. Open Page availability. You want Crawl allowed? to say Yes and Page fetch to say Successful.
If the live test fails but your browser works, a firewall or bot rule treats Googlebot differently. Check your CDN or security plugin's log for blocked requests to the sitemap.
Check the Manual actions report under Security & Manual Actions.

How to fix it

Fix the address. Submit the exact URL that opens as XML in your browser.
Remove any robots.txt rule that blocks the sitemap address.
Let Googlebot through your firewall or bot protection, and remove any login on the sitemap.
Run Test live URL again until Page fetch says Successful.
In the Sitemaps report, type the address in Add a new sitemap and click Submit. This tells Google to try again now.

See which of your pages Google skipped, and why. Free for up to 500 pages.

Get my free report

When you can ignore it

You just submitted the sitemap, the address opens as XML, and the live test says Successful. Google may not have tried yet. Check back in a few days before you change anything.

On your platform

Shopify

Shopify makes your sitemap at /sitemap.xml and links it to smaller sitemaps for products, collections, blogs, and pages. Submit only sitemap.xml, in the Search Console property for your primary domain. Google can't read the sitemap while the store is in private mode with a password page. If you have more than one domain, the others redirect to the primary one, unless you use them for international targeting. Shopify pages not indexed

Blogger

Blogger serves /sitemap.xml for posts and /sitemap-pages.xml for pages, and its default robots.txt already lists the sitemap. If your blog uses a custom domain, submit the sitemap in the Search Console property for that domain, not the blogspot.com address.

WordPress

WordPress itself serves /wp-sitemap.xml. Yoast SEO and Rank Math serve /sitemap_index.xml instead, and Yoast turns off the WordPress one. Submit the address your site really uses. WordPress turns its sitemap off when Settings > Reading > Discourage search engines from indexing this site is checked. WordPress pages not indexed

Cloudflare and other firewalls

Check your security events log for requests to the sitemap address. If a rule blocked or challenged them, change the rule so it leaves out known bots. Cloudflare's own example rules use not cf.client.bot for this.

Catch sitemap problems before they cost you pages

On paid plans, CrawlCoach downloads your sitemaps every day and reads Search Console's sitemap data for each fix list. When a sitemap stops loading, Search Console reports errors in it, or Google stops reading it, the fix goes in your fix list with the steps and a link to the right guide. See plans and prices.

Questions

Why does my sitemap say Couldn't fetch when it opens in my browser?

Google's request is not your browser's request. A firewall, bot protection, or a rule for unknown visitors can block Googlebot while your browser gets the file. Run Test live URL in URL Inspection on the sitemap address. If Page fetch fails there, the block is real. If it says Successful, Google may not have tried yet: wait a few days, then resubmit.

Why does my Shopify sitemap say Couldn't fetch?

Check three things. The store must not be in private mode with a password page. The sitemap must be submitted in the property for your primary domain, as sitemap.xml. And the address must open as XML in a private browser window. If all three are fine, resubmit and check again in a few days.

Why does my Blogger sitemap say Couldn't fetch?

A common cause is a sitemap submitted in a property that does not match the blog's address, such as the blogspot.com address for a blog that now uses a custom domain. Submit sitemap.xml in the property for the address your blog opens at.

Does Couldn't fetch stop my pages from being indexed?

Not by itself. Google still finds pages through links, and it remembers what it read from earlier versions of the sitemap. But new and changed pages are found more slowly without a working sitemap, so fix it.

Sources

Checked on October 8, 2026. Search Console's wording can change after that date.

Sitemap "Couldn't fetch" in Search Console: causes and fixes