The "Couldn't fetch" error in Google Search Console (GSC) often appears even when your XML sitemap is completely valid, accessible, and working.
Why This Happens
- Googlebot Scheduling / Crawl Demand: Google may skip fetching the sitemap if your server is busy or if Google's systems determine there is low crawl demand for your site.
- False UI Message: Google Search Console sometimes displays "Couldn't fetch" as a temporary status or glitch when Google hasn't processed the file yet.
- Server or Firewall Blocks: Caching plugins, Cloudflare "Under Attack" mode, or strict firewall/security rules can block Googlebot requests.
- Incorrect Path: Submitting the wrong URL path (such as
/sitemapor a full page URL instead ofsitemap.xmlorsitemap_index.xml).
How to Troubleshoot and Fix It
- Run a Live Test in GSC
- Go to URL Inspection in Google Search Console.
- Paste your full sitemap URL (
https://yourdomain.com) and click Test Live URL. - If the live test succeeds and returns an HTTP 200 status, your sitemap is fine. You can safely ignore the error or wait for Google to crawl it on its own schedule.
- Verify in a Browser
- Open your sitemap URL directly in an incognito browser window.
- Ensure it loads properly, starts with
<?xml version="1.0" encoding="UTF-8"?>, and does not throw any 404 or 403 errors.
- Check Firewall, Caching, or Cloudflare
- Temporarily disable security/firewall plugins or strict bot-protection settings (like Cloudflare's Under Attack mode) if they are intercepting Googlebot.
- Resubmit or Use Alternative Sitemaps
- Remove the failing sitemap entry from GSC, wait a few minutes, and resubmit it.
- If you use WordPress, make sure you are submitting the index file (e.g.,
sitemap_index.xmlfor Rank Math or Yoast) rather than an empty sub-file. - You can also try alternative submission methods.
If you'd like, let me know:
- What CMS or platform you are using (WordPress, Shopify, custom code, etc.)
- What happens when you run a Live Test in Google Search Console's URL Inspection tool
I can help you pinpoint the exact cause. Contact us for website maintenance and development
