Fix it

Search Console says the sitemap couldn't be fetched: causes and fixes

The Sitemaps report separates a file Google could not retrieve from a file it retrieved but could not fully read. The fix is different for each. This page maps the report's messages to causes, using Google's own help text.

By Adem ÇakalPublished 3 sources
Short answer

Couldn't fetch means Google could not retrieve the sitemap file at all. Google's help lists five causes: a robots.txt block, an unresolved manual action, a 404, a server error, or low crawl demand. Test the exact sitemap URL with a live URL Inspection, fix the cause, then resubmit. Has errors is different: Google got the file, and some entries failed.

The three statuses

Status in the reportWhat Google says it meansWhat happens to the URLs
SuccessFetched and read with no errorsAll queued for crawling
Has errorsFetched, but some entries failedParseable URLs are still queued; open the sitemap to see the errors
Couldn't fetchGoogle could not retrieve the fileNothing new is read until you fix the fetch

On the detail page, Sitemap could not be read means the fetch or parse failed entirely. Sitemap can be read, but has errors is the partial case.

Couldn't fetch: the five causes

CauseGoogle's fixHow to test
Blocked by robots.txtRemove the rule blocking Googlebot from the sitemapOpen /robots.txt and look for a Disallow that matches the sitemap path
Unresolved manual actionFix the issue in the Manual actions report, then resubmitOpen that report; it should show no issues
404, sitemap not foundConfirm the URL works in a browser, then correct or resubmitcurl -I https://example.com/sitemap.xml
Server or other general errorWait and see whether it recurs on later crawlsCheck server logs for the Googlebot request
Low crawl demandImprove content qualityGoogle gives no further test

Google's suggested confirmation: run a live test in URL Inspection on the sitemap URL and check that Crawl allowed is Yes and Page fetch is Successful.

Where a fetch can fail

Path of a sitemap fetch: robots.txt check, CDN or firewall, web server, sitemap file robots.txtsitemap path allowed? CDN / firewallGooglebot let through? Web server200, not 404 or 5xx? Sitemap filevalid XML, under limits? Google's help names robots.txt, 404 and server errors. Firewall and CDN blocks are not listed there.
The first three stages decide Couldn't fetch. The last decides Has errors.

The CDN and firewall stage is our addition. Google's list does not name it, but a rule that challenges unknown bots would produce the generic server error row. Compare your access logs with the time of the failed fetch. The sitemap checker fetches the file as an ordinary visitor and reports status, redirects and the URLs inside.

Has errors: the entries Google rejects

Report labelFix, per Google
URLs not followedReplace redirects with final URLs, use absolute URLs, avoid JavaScript or meta-refresh redirects
URL not allowedKeep URLs on the same domain, at or below the sitemap's directory, with matching protocol and www
Path mismatch: missing or extra wwwMake the www prefix in URLs match the sitemap's location
Compression errorRecompress the file (for example gzip), upload and resubmit
Too many URLs / File size exceededOver 50,000 URLs or over 50MB uncompressed: split it and list the parts in a sitemap index
Nested sitemap indexesRemove entries that point to other sitemap index files
Invalid dateUse W3C Datetime format; a time needs a time zone
Parsing errorEscape special characters such as & and <, then check URLs
Unsupported formatUse the correct XML header and namespace, with straight quotes
Leading whitespaceNot blocking, but remove it to meet the XML standard
Temporary errorUsually no action; if it lasts several hours, resubmit

The report also covers video, news and index-specific errors. Google's help lists them all; the rows above are the ones that site owners meet on ordinary pages. Redirecting URLs in a sitemap also show up as Page with redirect in the indexing report.

Fix, resubmit, wait

  1. Load the sitemap URL in a private browser window. You should see XML with a 200 status, not a login page or an HTML error.
  2. Run a live test on it in URL Inspection.
  3. Fix the matching row above, purge any cache that serves the old file, and resubmit in the Sitemaps report.
  4. Remember the timing Google states: a new sitemap is fetched immediately after submission, but crawling its URLs can take longer and not every URL may be crawled.

If the fetch succeeds but the URLs sit unindexed, the sitemap is no longer the problem. Read discovered, currently not indexed. Plugin-generated sitemaps (WordPress SEO plugins, Next.js and Webflow setups) differ by platform, so always test the live URL rather than the plugin's settings page.

Questions people ask

How long does Google keep retrying a sitemap that failed?

Google's help says it retries for a few days after a failed fetch or parse, then stops. After you fix the cause, resubmit the sitemap. Google also keeps information from earlier successful reads even if a later one fails.

Is Pending an error?

The Sitemaps report help page we read does not describe a Pending status, so we cannot say what it means or how long it lasts. Check the three documented statuses: Success, Has errors and Couldn't fetch.

Does Success mean all my URLs will be indexed?

No. Success means the sitemap was fetched and read without errors and its URLs are queued for crawling. Google says not all URLs may be crawled, and a sitemap is a hint, not an instruction.

Can a sitemap contain URLs from another domain?

Google's error list says URLs should stay on the same domain and at or below the sitemap's directory level, with the same protocol and www prefix. Otherwise the report shows a URL not allowed or path mismatch error.

Sources

  1. Search Console Help: Sitemaps report, accessed 2026-11-12.
  2. Google Search Central: How Google interprets the robots.txt specification, accessed 2026-11-12.
  3. Search Console Help: URL Inspection tool, accessed 2026-11-12.