Practical guideUpdated

Sitemap 'Couldn't fetch' in Search Console: causes and fixes

'Couldn't fetch' means Google could not download or read your submitted sitemap. Often it is temporary and clears after Google retries; newly submitted sitemaps can show it before the first successful fetch. If it persists, check that the sitemap URL returns a 200 status with XML content, is not blocked by robots.txt or a firewall, is within the same property, and is valid XML within size limits.

This status is frustrating because Search Console gives few details. The causes, though, are a short list, and most can be checked in minutes. This guide covers each check in the order we would run it.

By , Founder, SerionFlow

What we measured ·

What Google shows for "sitemap couldn't fetch" right now

Method: Live Google results (United States, desktop, English) for "sitemap couldn't fetch" retrieved through DataForSEO's SERP API on 2026-10-22. Page types are our own classification of each ranking URL.

The top 8 organic results for "sitemap couldn't fetch" were 3 forum or community threads, 3 product or service pages, 1 official search-engine documentation, 1 guide or explainer. The first three were www.reddit.com, stackoverflow.com, help.fmgsuite.com. Community threads (www.reddit.com, stackoverflow.com, community.shopify.com) ranked on page one, a sign searchers want first-hand answers, not only vendor pages.

Google showed an AI Overview for this query, citing 8 source domains including www.reddit.com, support.google.com, github.com, seomatic.ai. Pages that state the answer directly and early are the ones an Overview can quote.

People Also Ask listed: "How to fix sitemap error?"; "How to fetch sitemap?"; "Why is my sitemap not found?"; "Why isn't Google reading my sitemap?". The sections below answer the ones within this page's scope.

Top organic results for "sitemap couldn't fetch", 2026-10-22
PositionDomainPage type
1www.reddit.comForum or community thread
2stackoverflow.comForum or community thread
3help.fmgsuite.comProduct or service page
4github.comProduct or service page
5sitechecker.proProduct or service page
6support.google.comOfficial search-engine documentation
01

First, rule out a timing issue

Search Console sometimes shows 'Couldn't fetch' for a sitemap that has just been submitted and not yet processed, and the status can lag behind reality. If the sitemap is new, wait 24 to 48 hours and check the 'Last read' date. Resubmitting the same URL repeatedly does not speed it up.

02

Run the five checks

If it persists, check these in order.

Sitemap fetch checks
CheckHowFix if failing
Status codeOpen the URL; check the network panel or use a command-line requestReturn 200; remove redirects or point Search Console at the final URL
Content type and formatResponse is XML, not an HTML pageFix routing so the file is served, not the app shell
robots.txtTest the sitemap URL against robots.txtAllow the sitemap path
Bot protectionCheck firewall, CDN, or security plugin logs for blocked GooglebotAllowlist verified Googlebot
Property matchSitemap host and protocol match the propertySubmit under the right property
03

The single-page app trap

On JavaScript apps hosted with a catch-all rewrite, a request for /sitemap.xml can return the app's HTML shell with a 200 status instead of the XML file, if the file is missing from the build or the rewrite takes precedence. Search Console then cannot parse it. Check that the response body begins with an XML declaration or urlset element, not with HTML. Scoping rewrites so static files are served first fixes this.

04

Format and size problems

A sitemap must be valid XML using the sitemaps.org namespace, UTF-8 encoded, with fully qualified URLs. A single file can hold up to 50,000 URLs and 50 MB uncompressed; larger sites need a sitemap index. Special characters in URLs must be escaped. If the file is generated by a plugin or script, open it and look for broken markup, HTML error messages, or PHP warnings at the top of the file.

05

After fixing

Resubmit the sitemap once in Search Console and check back after a day. Reference the sitemap in robots.txt with a Sitemap line so other search engines can find it too. Our free sitemap checker fetches a sitemap the way a crawler would and reports status, format, and URL problems in one pass. SerionFlow is the wrong tool for fixing your own sitemap file; it only maintains the sitemap of the pages it publishes.

Clear answers

Frequently asked questions

Why isn't Google reading my sitemap?

+

Usually the URL does not return valid XML with a 200 status, is blocked by robots.txt or a firewall, or was submitted under a different property. Sometimes it simply has not been processed yet.

Does 'Couldn't fetch' stop my pages being indexed?

+

Not by itself. Google can still find pages through links. A working sitemap helps discovery, especially for new or deep pages.

About the author

· Founder, SerionFlow

Shadrack builds SerionFlow's site research, page generation, and Search Console tooling, and runs the free tools these guides pair with. Search Console figures cited on these pages come from serionflow.com's own property.

Continue exploring

Related SerionFlow resources

More in Guides

All guides

Make the next move obvious

Let SerionFlow turn your market evidence into momentum.

Confirm the market, rank the opportunities that matter, create brand matched pages on your domain, and keep moving with controlled weekly intelligence.

Choose how SerionFlow uses cookies.

Essential cookies keep the site secure and working. Product analytics helps us improve reliability. Optional cookies help us remember preferences and improve campaigns. You can change optional cookies anytime in Cookie Settings.