// SEO plans from €35/hour or €395/month// from €35/hr · €395/mo Free SEO checker[email protected]+31 6 4555 9353
Free SEO audit
search console and indexing

Sitemap Couldn’t Fetch in Search Console: Fixes

When the Sitemaps report says Couldn’t fetch, Google could not retrieve your sitemap file. The causes are limited and each has a clear check. This guide lists every cause Google names, the debugging steps, how to read the report columns and statuses, the parsing errors that look similar, and when to resubmit.

  • 6 named causes
  • Debug with Live test
  • Statuses and columns
  • Resubmit rules
Sitemaps reportstatus
Success | Has errors | Couldn't fetch
Couldn't fetch = file not retrieved
// quick answer
Couldn’t fetch means Google could not retrieve the sitemap file. Check six causes: blocked by robots.txt, server unavailable, wrong URL (404), login required, an unresolved manual action, or low crawl demand. Then run a Live test in URL Inspection and confirm Crawl allowed is Yes and Page fetch is Successful. Temporary errors usually need no resubmission; resubmit if one persists for several hours.

What the statuses mean

StatusMeaning
SuccessFetched and read with no errors; all URLs queued for crawling
Has errorsFetched but contains errors; URLs that parsed correctly are still queued
Couldn’t fetchGoogle could not retrieve the sitemap file

On the top-level page the error shows as Sitemap had X errors. The details page shows either Sitemap could not be read (fetch failure) or Sitemap can be read, but has errors. Google’s page I used does not describe a Pending status.

The causes of Couldn’t fetch

CauseFix
Blocked by robots.txtGoogle respects robots.txt for sitemaps; remove the blocking rule. See robots.txt syntax
Not reachable or server issuesServer unavailability can prevent retrieval; some causes are temporary, so wait and see
Wrong URL (404)The sitemap is not at that address; open it in a browser
Login requiredThe sitemap must be accessible without authentication
Manual actionSitemaps are not read while an unresolved manual action exists; fix it and resubmit. See manual actions
Low crawl demandGoogle may fetch less often when content quality is lower

Debug in three steps

  1. Open the sitemap’s details page and click the error name for more detail.
  2. Run a Live test in the URL Inspection tool on the sitemap URL.
  3. Confirm Crawl allowed? is Yes and Page fetch is Successful.

Report columns

ColumnMeaning
Sitemap URLThe exact URL submitted; redirects are not followed
TypeSitemap, sitemap index, RSS, Atom or Unknown
SubmittedDate last submitted through this report
Last readLast fetch time; shown only if fetched
Discovered pagesPage URLs parsed, duplicates counted once; not a guarantee of crawling or indexing

Because redirects are not followed, submit the final URL. Use the exact protocol and www version of your property. See submit a sitemap.

Errors that look similar

Some errors appear when the file is fetched but cannot be parsed. They show as Has errors, not Couldn’t fetch:

  • Compression error: recompress (for example gzip), upload and resubmit.
  • Empty sitemap: no URLs found.
  • File size exceeded: over 50 MB uncompressed; split into smaller sitemaps in an index.
  • Too many URLs: each sitemap holds at most 50,000 URLs; an index at most 50,000 sitemaps.
  • Invalid XML: unescaped characters such as & or <; curly quotes from word processors are a common cause of unsupported format.
  • URL not allowed: URLs above the sitemap’s directory, in a sibling directory, or on a different domain, protocol or www variant.
  • Nested indexes: an index can list only sitemap files, not other indexes.

Format rules are in sitemap XML format rules.

Fix Couldn’t fetch step by step

1
open

Open the URL in a browser

Do you see XML, not a 404 or login?

browser
2
robots

Check robots.txt

Is the sitemap URL blocked?

robots.txt
3
live test

Run URL Inspection Live test

Crawl allowed Yes, Page fetch Successful.

Live test
4
actions

Check manual actions

An unresolved one blocks reading.

Manual actions
5
server

Check server health

Look for outages or blocks.

hostingfirewall
6
resubmit

Resubmit the final URL

Once the cause is fixed.

Sitemaps report

When to resubmit

  • Google tries to fetch as soon as you submit, then recrawls the sitemap on its own schedule.
  • If a fetch or parse fails, Google retries for a few days, then stops if the problem persists. Fix it and resubmit.
  • For temporary errors you usually do not need to resubmit; if one persists for several hours, resubmit.
  • Resubmit after major sitemap changes; otherwise let Google’s schedule handle updates.
  • Google keeps data from previous successful reads even after later failures.

Notes for WordPress sites

  • Yoast serves sitemap_index.xml (my own note). Submit that exact URL and test it in a browser.
  • Security plugins or CDNs can block Googlebot from the sitemap (my own note). See verify Googlebot.
  • Caching issues can serve a stale or empty file; clear caches.
  • Staging settings that discourage search engines may interfere; check Reading settings.

Troubleshooting

SymptomLikely cause (my own diagnosis)Fix
Fetch fails just after submitWrong or redirected URLSubmit the final URL
Works in browser, fails in GoogleBot blocked by firewallAllow Googlebot
Intermittent failuresServer instabilityFix hosting
Fails persistentlyManual action or robots ruleCheck both

Checklist

Access

  • URL opens in browser
  • No login
  • Not blocked in robots.txt
  • Final URL, no redirect

Test

  • Live test run
  • Crawl allowed Yes
  • Page fetch Successful
  • Manual actions clear

Format

  • Valid XML
  • Under 50,000 URLs
  • Under 50 MB
  • Same host and protocol

After

  • Resubmit
  • Watch Last read
  • Check Discovered pages
  • Review indexing

What Google’s page does not say

It does not state the exact number of retries or the precise length of the few days, the interval for periodic recrawls, the compressed file size limit, how long submitted URLs take to be crawled, or what Pending means.

Key terms

Sitemap
A file listing URLs for Google to crawl.
Sitemap index
A file listing other sitemap files.
Couldn’t fetch
Google could not retrieve the file.
Last read
Time of Google’s last fetch.

Common mistakes

mistake 1

Submitting a redirecting URL

Redirects are not followed.

Submit the final URL.
mistake 2

Blocking the sitemap

Robots rule.

Allow it.
mistake 3

Wrong property

http, https and www differ.

Match the property.
mistake 4

Resubmitting repeatedly

Temporary errors clear.

Wait several hours first.
mistake 5

Ignoring manual actions

Blocks reading.

Resolve it.
mistake 6

Skipping Live test

No evidence.

Run it.

Related guides

faq

Sitemap couldn’t fetch questions

What does Couldn’t fetch mean?

Google could not retrieve the sitemap file.

What causes it?

robots.txt blocking, server issues, a wrong URL, a login requirement, an unresolved manual action or low crawl demand.

How do I debug it?

Check the error detail, run a Live test and confirm Crawl allowed and Page fetch.

Should I resubmit?

After fixing a cause. For temporary errors only if it persists for several hours.

Does Google follow sitemap redirects?

No. The submitted URL must be final.

How long does Google retry?

A few days, then stops if the problem persists.

What are the size limits?

50 MB uncompressed and 50,000 URLs per sitemap.

Does a failed fetch erase old data?

No. Google keeps data from previous successful reads.

sources

Statuses, causes, debugging steps, columns, errors, resubmission and limits come from Google’s help pages. The step routine, WordPress notes, troubleshooting and checklists are my own.

Scroll to Top