Search Console Couldn't Fetch Your Sitemap? How to Fix It
Quick answer: Couldn't fetch usually means Google could not read the sitemap URL, and the fix starts with opening the URL yourself. Confirm it returns valid XML with a 200 status, check robots.txt is not blocking it, resubmit the exact URL, then give Search Console a few days to retry.
You submit a sitemap, refresh the report, and Search Console answers with two words: Couldn't fetch. No error code, no line number, no hint whether Google tried and failed or has not tried yet. The status is doing a lot of work for two words, and most of the causes take under a minute to check once you know the list.
Work through the checks in order below. They run from most common to least, and each one is something you can test yourself in a browser or terminal without waiting on Google.
SEARCH CONSOLE
Search Console Couldn't Fetch Your Sitemap? How to Fix It
PRIMARY KEYWORD
Google Search Console couldn't fetch sitemap
READ TIME
7 minutes
What does the Couldn't fetch status actually mean?
It means the last attempt to read your sitemap did not return a usable file. That covers a lot of ground: a typo in the submitted URL, a redirect Google declined to follow, a server error, a robots.txt block, or a response that was not XML at all.
There is also a timing quirk worth knowing. A freshly submitted sitemap can briefly show Couldn't fetch or Pending before Google's first real attempt completes. If you submitted in the last day, wait before diagnosing. If the status has held for days, it is real.
How do you test the sitemap URL yourself?
Open the exact URL you submitted in a browser, character for character. You are checking three things: it loads without an error page, it returns XML rather than an HTML redirect or a login page, and the XML starts with a urlset or sitemapindex element.
Then check the status code, since browsers hide it. A command like curl -I against the URL shows whether the response is a clean 200 or a redirect chain. A sitemap that redirects, even to its own HTTPS twin, is a common silent cause, and the fix is submitting the final URL directly.
Which causes explain most Couldn't fetch errors?
Six causes cover nearly every case. Check them in this order and stop at the first one that matches what you saw in your own test.
- A mistyped or moved URL: the submission points at a path that 404s, often after a plugin or platform change renamed the sitemap
- A robots.txt block: a Disallow rule covering the sitemap path stops the fetch before it starts
- A redirect: the sitemap URL forwards to another address, and the submission should point at the destination
- A server or CDN error: intermittent 5xx responses fail some fetch attempts, so check server logs around the fetch times
- Invalid or empty output: the URL returns HTML, an error page, or an empty file instead of XML
- Bot protection: a firewall rule or challenge page blocks Googlebot specifically, which your own browser test cannot see
How do you confirm the fix actually took?
Resubmit the exact URL after fixing the cause, then watch the report's last-read date rather than refreshing the status hourly. Google retries on its own schedule, and a few days of patience is part of the fix. The status flipping to Success with a recent read date is the confirmation.
Success means Google read the file. It does not promise the URLs inside will be indexed, which the Page indexing report tracks separately and more slowly. This site monitors its sitemap fetch status after every deploy for exactly this reason: the file breaking silently is cheap to catch and expensive to miss.
TAKEAWAY CHECK
What belongs on the fix a couldn't fetch error today?
- 01Open the exact submitted URL in a browser and confirm real XML loads.
- 02Check the status code with curl -I and note any redirect in the chain.
- 03Search robots.txt for a Disallow rule covering the sitemap path.
- 04Validate the file starts with a urlset or sitemapindex element and is not empty.
- 05Check firewall or bot-protection logs for blocked Googlebot requests.
- 06Resubmit the final, non-redirecting URL in the Sitemaps report.
- 07Check back in two to three days for a Success status and a fresh last-read date.
What else do people ask about Google Search Console couldn't fetch sitemap?
How long does Google take to retry a failed sitemap fetch?
Google retries on its own schedule, typically within days, and resubmitting in Search Console prompts a fresh attempt sooner. If the status still reads Couldn't fetch a week after a confirmed fix, re-test the URL from outside your network, since a lingering block is likelier than Google ignoring the file.
Why does Search Console say Couldn't fetch when the sitemap opens fine for me?
Because you and Googlebot are different clients. Firewalls, bot protection, and geo rules can serve you the file while challenging or blocking Google's fetcher. Redirects you barely notice in a browser also count. Check server logs for the fetch attempts and test with a command-line client rather than a browser.
Does deleting a sitemap from Search Console remove my pages from Google?
No. Removing a sitemap submission only stops Search Console reporting on that file. Pages Google already indexed stay indexed, and Google can keep recrawling them through links and memory of the URL. Deleting a stale submission is cleanup, and it is safe to do once a replacement is live.
Should I submit a sitemap index or each child sitemap separately?
Submit the index file and let Google follow it to the children, which keeps the report tidy and matches how generators maintain the files. Submitting a child directly is a useful temporary trick when you suspect the index itself is the broken link in the chain.
Can a Couldn't fetch error hurt my rankings?
Not directly. A sitemap is a discovery aid, and Google keeps crawling through links regardless. The real cost is slower discovery of new and updated pages, which matters most on new sites and large ones. Treat the error as urgent plumbing rather than a ranking emergency.
Which primary sources support this guide?
Product behavior and metric definitions change. These are the official Google references used for this article and checked on August 17, 2026.
- 01Google Search Central: sitemaps overview
Google's guidance on what sitemaps do and when a site actually needs one.
- 02Google Search Central: introduction to robots.txt
Official explanation of what robots.txt controls and its common misuses.
- 03Google Search Console: Page indexing report
Google's documentation of index coverage states and the note that indexing does not guarantee a page will be served.
PUT THE CLAIM ON THE RECORD
Your SEO result deserves a source, not a trust-me caption.
Connect an owner-level Search Console property, choose what stays public, and get a receipt with a stable share link.