By Hridoy Ahmed | Last updated: November 2026 | 11 min read
Short answer: “Couldn’t fetch” means Google could not download your sitemap file at all. The usual causes are a robots.txt rule, a wrong or redirecting URL, a firewall or security tool that blocks Googlebot, a server error, or low crawl demand. Test the sitemap URL with the live test in URL Inspection, fix what it shows, then submit the sitemap again.
In this guide
- What “Couldn’t fetch” means
- Is it a real problem?
- A 10-minute diagnosis
- Symptom, cause and fix
- WordPress and Rank Math checks
- Fix, test and resubmit
- After it says Success
- Mistakes to avoid
- FAQ
What “Couldn’t fetch” means
The Sitemaps report in Search Console shows one status per submitted sitemap. There are three, and they point to very different problems.
| Status | What happened | Where to look |
|---|---|---|
| Success | Google fetched and read the file with no errors | Nothing to fix. Check indexing separately. |
| Has errors | Google read the file but found problems inside it | The error list: bad dates, invalid URLs, wrong host |
| Couldn’t fetch | Google could not get the file itself | Access: robots.txt, URL, server, firewall, crawl demand |
So “Couldn’t fetch” is an access problem. The XML inside may be perfectly fine. Google never got to read it.
Is it a real problem?
Often it is smaller than it looks. A sitemap is a hint, not a requirement. Google’s own help page says that a small site of about 500 pages or fewer, where every page can be reached by links from the homepage, probably does not need a sitemap at all. Google can still find your pages through links.
It matters more when your site is large, new, has many pages with few internal links, or publishes often. In that case you want the sitemap working. It also matters as a signal: if Google cannot fetch a public file from your site, something in your setup may also block Googlebot from other pages.
A 10-minute diagnosis
Work through these steps in order. Most cases end by step four.
- Open the sitemap URL in a private window. You should see XML or a styled list of links, without a login, a challenge page or a redirect to your homepage.
- Compare the exact URL. The Sitemaps report records the exact URL you submitted and does not follow redirects. If your site redirects http to https or www to non-www, submit the final address. Also check the property: a sitemap submitted under an http property will not show under an https property.
- Run the live test on the sitemap URL. Paste the sitemap URL into URL Inspection and click Test live URL. Open the availability details. You want Crawl allowed? Yes and Page fetch: Successful. If Google shows a block or an error here, you have found the cause.
- Read your robots.txt. Google obeys robots.txt when it fetches sitemaps. A Disallow rule that matches the sitemap path stops it.
- Check Manual actions and Security issues. Google states that sitemaps are not read while a manual action is unresolved.
- Check the response headers. The sitemap should return status 200 and an XML type. An
X-Robots-Tag: noindexheader on the sitemap file can stop Google from using it.
curl -I https://example.com/sitemap_index.xml
Read the first line for the status code, then the content type. A test that uses a Googlebot user-agent string can help, but many firewalls verify the real Googlebot by its IP address. So treat only the Search Console live test as proof of what Google sees.
If the cause is not obvious, my technical SEO service includes a crawl access check across robots.txt, firewall, headers and sitemaps.
Symptom, cause and fix
| What you see | Likely cause | Fix |
|---|---|---|
| The URL gives a 404 | Wrong address, sitemap module off, or permalink problem | Find the real sitemap URL in your plugin. Save the permalinks page once to refresh rewrite rules. |
| It opens for you, but the live test fails | A firewall, CDN or bot protection blocks or challenges Googlebot | Allow verified Googlebot. Check firewall events and security plugin logs. |
| The URL redirects somewhere | http to https, www or slash redirect | Submit the final URL that returns 200. |
| Blank page or 500 error | Plugin conflict, low memory or a very large sitemap | Read the PHP error log, raise memory, remove the conflict, split the sitemap. |
| Crawl allowed says No | A robots.txt rule | Delete or narrow the rule. |
| You see a maintenance or coming-soon page | Maintenance plugin or login wall | Turn it off or exclude the sitemap. |
| Old, empty or HTML content returned | Cache or CDN serving a bad copy | Purge the cache and exclude the sitemap from caching. |
| Everything works, yet the status stays red | A temporary error, or low crawl demand | Wait, resubmit later, add the sitemap to robots.txt, improve the site. |
The last row is real. Google lists low crawl demand among the reasons for a failed fetch, and it says that better content raises crawl demand. That is not a quick fix, but it tells you where to look when all technical checks pass.
WordPress and Rank Math checks
- Know your real URL. Rank Math serves its sitemap index at
/sitemap_index.xml. Core WordPress uses another path. Submit the one your plugin actually serves. - Use one sitemap source. If a theme, a second SEO plugin and WordPress all produce sitemaps, turn the extras off.
- Re-save permalinks. Go to Settings, then Permalinks, and click Save. This refreshes rewrite rules and fixes many 404 sitemap cases.
- Check security plugins and CDN rules. Rate limits, bot fight modes and country blocks can catch Googlebot. Review the logs for blocked requests to the sitemap.
- Check caching and optimization plugins. Minify or cache rules should not touch XML files.
- Look at the module. In Rank Math, make sure the Sitemap module is on and the sitemap settings are saved. My Rank Math setup guide shows the settings to review.
For a clean sitemap from scratch, read how to create an XML sitemap and submit it to Google.
Fix, test and resubmit
- Fix the cause you found.
- Run the live test again until it shows Page fetch: Successful.
- Open the Sitemaps report and submit the working URL. Google tries to fetch it right away.
- Check back later. If it still fails, click the sitemap and read the error details.
Google retries a failed sitemap for a few days and then stops. So after you fix the problem, always send a new request. A temporary error often clears by itself, but if it still shows after several hours, resubmit.
You can also point to your sitemap in robots.txt. This helps discovery even when the report acts up.
Sitemap: https://example.com/sitemap_index.xml
Sitemaps found through robots.txt do not appear in the Sitemaps report unless you also submit them there. Edit the file with care, using my guide on creating a robots.txt file for WordPress.
Do not forget Bing. It has its own sitemap submission and the IndexNow protocol. See Bing Webmaster Tools setup and IndexNow.
After it says Success
A green “Success” only tells you that Google could read the file. It does not tell you that your pages are indexed. Google says the discovered-page count is not a promise of crawling or indexing.
To see how many sitemap URLs are indexed, open the Page indexing report and use the sitemap filter, choosing your sitemap or “All submitted pages”. Compare indexed and not indexed counts. For the pages that stay out, the reason column tells you why. Start with my guides on pages that are not indexed and URLs indexed though blocked by robots.txt.
A healthy sitemap lists only canonical, indexable pages that return 200, uses full URLs with the same host as the sitemap, and leaves out redirects, noindex pages and parameter URLs.
Mistakes to avoid
- Submitting the same sitemap every day. Google rechecks it on its own schedule.
- Submitting a redirecting URL. The report does not follow redirects.
- Using the wrong property. Check http, https, www and non-www.
- Deleting the sitemap in Search Console to “stop crawling”. Removing it from the report does not make Google forget it or its URLs.
- Ignoring a manual action. Fix it first, then resubmit.
- Blocking Googlebot by accident. A security setting that protects your site may also block the crawler.
- Adding junk to the sitemap. Redirects and noindex URLs weaken the file.
FAQ
Is “Couldn’t fetch” a serious error?
It depends. It means Google could not get the file, which blocks the sitemap hint. Your pages can still be found through links. It becomes serious when it points to a wider crawl block or when your site depends on the sitemap for discovery.
How long before Google tries again?
Google retries a failed sitemap for a few days, and then it stops. Fix the problem and submit a new request instead of waiting.
Can I fix it by renaming the sitemap?
Only if the old name was the problem, such as a wrong path. A new name does not fix a block, a firewall rule or low crawl demand.
Why does the report say Success but my pages are not indexed?
Success means the file was read. Indexing is a separate decision for each URL. Use the sitemap filter in the Page indexing report to see the reasons.
Sitemap still red after all checks? I test Googlebot access, headers, firewall rules and sitemap content by hand. See my SEO and technical SEO service.
About the author: Hridoy Ahmed is an SEO specialist and WordPress security expert based in Dhaka, Bangladesh. He has 8+ years of experience and works with clients worldwide.
