Search Console Sitemap Status "Couldn't Fetch": A Step-by-Step Fix
Short answer: "Couldn't fetch" means Google tried to download your sitemap file and did not get a clean copy. The cause is usually one of five things: a wrong address, access refused by a firewall or login, a redirect or error response, malformed XML, or a file that breaks size limits. Work through those stages in order, test the file in a browser and with a header check, then resubmit. Often the problem is a simple typo or a plugin that moved the file.
What the status means and what it does not
In Search Console, open Indexing, then Sitemaps. Each submitted file shows a status: Success, Has errors, or Couldn't fetch. "Couldn't fetch" is about retrieval: Google could not get the file. It says nothing about whether your pages are indexable. "Has errors" means the file was retrieved but some lines are invalid.
One detail catches people: a newly submitted sitemap may briefly show "Couldn't fetch" before Google has tried properly. If the file passes every check below, wait a day or two and look again before changing anything.
Stage 1: is the address right?
- Copy the exact sitemap URL you submitted and paste it into a browser's private window.
- Confirm it matches the protocol and host of the Search Console property. A sitemap on
https://www.example.combelongs to that property, and a file hosted on a different domain generally cannot list your URLs unless ownership is verified. - Look for typos:
sitemap.xmlversussitemaps.xml, upper case letters, an added/or a wrong folder. - If you use an SEO plugin, find out which address it actually generates. Many produce an index such as
/sitemap_index.xmlpointing to child files. Submit the index, not an old default path.
Stage 2: can Google reach it?
If the file opens for you, test it as a stranger would.
- Check the sitemap path is not blocked in robots.txt. A disallow rule covering it prevents the fetch.
- Check no login, IP allow-list, password protection, or security challenge guards the path.
- Look at the Page indexing or Crawl Stats reports for 401, 403 or 5xx responses that might include the sitemap request.
- If your host or CDN blocks automated traffic aggressively, add an exception for the sitemap path.
Stage 3: what does the server really return?
Run curl -I https://example.com/sitemap.xml and read the first line and headers.
| Response | Meaning | Fix |
|---|---|---|
200 with content-type: application/xml or text/xml |
Healthy | Move to stage 4 |
| 301 or 302 to another address | The file moved or a redirect rule intervenes | Submit the final address, and remove needless redirects |
| 404 | File missing | Regenerate it or correct the path |
| 403 | Access refused | See stage 2 |
| 500 or 503 | Server error, often caused by a heavy plugin generating a large file on demand | Cache the sitemap, or reduce its size |
200 with text/html |
A CMS "page not found" template or maintenance page is being served | Fix routing; the real file is not there |
A common silent failure is a soft error: the URL returns 200 but the body is a styled error page. Open the file in a browser. A valid sitemap displays as XML or as an unstyled list of addresses, not as your site's theme.
Stage 4: is the XML valid?
- It must begin with an XML declaration or the
urlsetorsitemapindexroot element, with no stray characters, spaces or blank lines before it. A PHP notice printed above the file breaks it. - The encoding must be UTF-8, and special characters in URLs must be escaped, for example
&as&. - Every
locmust be a full, absolute URL, with the same protocol and host as the property. - Dates must follow the W3C datetime form, like
2026-11-05. - A sitemap index may list sitemaps, but not other indexes inside it.
Paste the file into an XML validator, or open it in a browser, which will complain about malformed markup.
Stage 5: size and compression
A single sitemap may hold up to 50,000 URLs and 50 MB uncompressed. If your shop or blog is bigger, split it into several files listed from an index. If you serve a gzip version, the file must decompress correctly, and the header must not claim a wrong content type. Very slow responses can also cause a timeout, so make sure the file is generated quickly or served from a cache.
Resubmit and monitor
- After the fix, open the Sitemaps report, remove the old entry if the path changed, and submit the correct one.
- Click the file to see the last read date and the discovered page count.
- If it still shows trouble after a few days, run the URL Inspection live test on the sitemap URL itself to see Google's view.
- Add the sitemap line to robots.txt as well:
Sitemap: https://example.com/sitemap.xml. Google reads it without submission.
Illustrative case
An Irish bakery moves from one SEO plugin to another. The old plugin's sitemap path now returns a 404 page styled like the site, with status 200. Search Console reports "Couldn't fetch". The bakery submits the new plugin's index address, removes the stale entry, and the status changes to Success with the page count you anticipated.
FAQ
Does a failed sitemap stop my site being indexed?
No. Google can find pages through links. The sitemap is a helper, especially for new or deep pages.
Must the sitemap be resubmitted whenever pages are added?
Not usually. Google rechecks submitted sitemaps periodically, and an accurate lastmod helps.
Can I submit more than one sitemap?
Yes. List them in an index file or submit each separately.
Why is the page count lower than my total pages?
The sitemap should list only indexable canonical pages. A smaller count often means excluded duplicates or noindexed pages, which is desirable.
For tidy sitemaps and robots rules that behave, tell us what your site runs on and we will set them up with you.