Skip to content
SearchSee plans and prices

"Sitemap could not be read" in Search Console: the fetch failed

"Sitemap could not be read" is the details page for a sitemap whose status is "Couldn't fetch". Google did not get the file. A sitemap WordPress serves at /wp-sitemap.xml answers 404 while "Discourage search engines" is ticked, and a file on disk can replace it.

By
WP Ministry
Published

In short

  • The Sitemaps report has three statuses. "Couldn't fetch" is the one whose details page says "Sitemap could not be read".
  • Google lists the fetch failures: a robots.txt block, a manual action, a wrong address (404), another server error, or low crawl demand.
  • The report lists sitemaps you submitted in that property. One found only from robots.txt is not in the table until you submit it.
  • On WordPress the sitemap index is /wp-sitemap.xml. It answers 404 while "Discourage search engines" is ticked.
  • Google retries a failed fetch for a few days, then stops. Fix the cause and submit the sitemap again.
  • Whether Google's next fetch succeeds is Google's. A sandbox cannot open Search Console.

"Sitemap could not be read" is not a third status in the Sitemaps report's table. The table has three: "Success", "Couldn't fetch", and "Sitemap had X errors". The help page says to open the sitemap's details when the status is not Success. If that page says "Sitemap could not be read", the fetch failed. If it says the sitemap can be read but has errors, Google got the file and some of the entries are wrong. This page is the fetch. Parsing errors are a different job.

Google keeps trying for a few days. If the fetch keeps failing, it stops trying to read that sitemap. A later success does not make Google forget URLs it already learned from an earlier read. Fix the cause, then submit the sitemap again.

Confirm which failure you have

The help page's debugging steps are short.

  1. Open the sitemap in the report and read the error on the details page.
  2. Copy that sitemap's URL into the URL Inspection tool and run the live test.
  3. Under Page availability, "Crawl allowed?" should be "Yes" and "Page fetch" should be "Successful".

The report also says it lists only sitemaps submitted in that property, through the report or the API. A sitemap Google found from a Sitemap: line in robots.txt can be in use and still absent from the table. Submit it in the report if you want the status tracked. Check that you are looking at the property that matches the address: https against http, and www against the bare name.

What causes it

  • The address you submitted does not serve a sitemap

    Common

    Google's list of fetch errors includes an HTTP 404, which it describes as the sitemap not being found at the address provided. A WordPress site serves its own sitemap at /wp-sitemap.xml, and that address answers 404 while search engines are discouraged.

    Fix: Open the address you submitted

  • robots.txt tells Google not to fetch the sitemap

    Sometimes

    The Sitemaps report's help says Google respects robots.txt when it fetches a sitemap, and that a rule blocking the sitemap has to be removed.

    Fix: Remove a robots.txt rule that blocks the sitemap

  • The server failed, or the site has a manual action

    Sometimes

    The same list includes a general server error, which can be brief, and a manual action. Google says sitemaps are not read while a manual action is unresolved.

    Fix: Rule out a manual action and a server error

  • The sitemap was submitted on another version of the site

    Sometimes

    The report shows only sitemaps submitted in the current property, through the report or the API. An http property does not list a sitemap submitted for the https property, and the reverse is true of www.

    Fix: Rule out a manual action and a server error

How to fix it

Open the address you submitted

  • Easy
  • No risk
  • About 10 minutes
  1. Step 1: Visit the URL

    Paste the sitemap URL from the details page into a browser. Google's help says to do this for a 404: if the address does not load, it is the wrong address.

  2. Step 2: Use WordPress's own sitemap

    A site with no SEO plugin serves a sitemap index at /wp-sitemap.xml. The guide to that file covers what it lists. /sitemap.xml on that same test redirected to /wp-sitemap.xml. Submit the address that answers, not a path from another site's tutorial.

  3. Step 3: If it answers 404, check the Reading setting

    While "Discourage search engines from indexing this site" is ticked, WordPress's sitemap answers 404. The box has not written Disallow: / into robots.txt since WordPress 5.3. What the box does is the check. Untick it only if you want the site indexed.

  4. Step 4: Submit the working address

    In the Sitemaps report, submit the URL that loaded. Remove the one that 404s if it is still in the table, using the report's remove control. Google's help says a removed sitemap may stay in the list for a few days.

A file named sitemap.xml in the site's root is the answer for that path, in place of anything WordPress would generate. If you uploaded one for a staging copy, it is what Google fetches on the live site too.

The sitemap checker reads a sitemap from outside and reports whether the file could be fetched and read. It is one page's view, not Search Console's.

Remove a robots.txt rule that blocks the sitemap

  • Easy
  • Low risk
  • About 10 minutes

Google's help says it respects robots.txt when fetching a sitemap, and that you must remove the rule that prevents the fetch.

  1. Step 1: Read the file Google sees

    Open /robots.txt on the site. A rule that disallows / or the sitemap's path blocks the fetch. WordPress's own robots.txt, when no file is on disk, disallows /wp-admin/ and names the sitemap. Where that file comes from shows both cases.

  2. Step 2: Find the line

    The robots.txt tester answers whether a rule blocks the sitemap's address. Change the line that matches, not a line for a different crawler.

  3. Step 3: Inspect the sitemap again

    Run the live test from the steps above. "Crawl allowed?" should be "Yes".

To undo it: Put the rule back if you removed the wrong line.

Rule out a manual action and a server error

  • Easy
  • No risk
  • About 15 minutes
  1. Step 1: Check Manual actions

    The Sitemaps report's help says sitemaps are not read while a manual action is unresolved. Open that report, fix the action if one is listed, and submit the sitemap again.

  2. Step 2: If the browser loads the file and Google does not

    The help calls some server errors transient and says to wait and see whether a later crawl still fails. A firewall that blocks Googlebot is described on the Page indexing report help, under server connectivity. Ask the host when the file loads for you and the live test still fails.

  3. Step 3: Confirm the property

    If the sitemap is missing from the table entirely, the help's first guess is that it was submitted on another property, or that it was never submitted in the report. Add the sitemap to the property whose address matches the site.

"Sitemap had X errors" means Google did read the file. Those rows are entries inside it, not this status. Leave them until the fetch itself is "Success".

A WordPress SEO audit covers a sitemap that still will not fetch after the address, the Reading setting and robots.txt have been checked.

Common questions

Is "Sitemap could not be read" the same as "Couldn't fetch"?

Yes. "Couldn't fetch" is the status in the report's table. "Sitemap could not be read" is what the details page says for that status. "Sitemap had X errors" means the file was fetched and some entries failed.

Does the site stay out of Google until this is fixed?

No. The help page says a sitemap is not required for Google to crawl a site, and that URLs it already read from an earlier sitemap are not forgotten when a later fetch fails. A failed sitemap does mean Google is not getting the list you submitted. A WordPress site that is not on Google is the wider check.

I see "Success" and the pages are still not indexed

The report says discovered page URLs are not a guarantee they will be crawled or indexed. Filter the Page indexing report by the sitemap to see what happened to the URLs inside it.

Which address should I submit?

On a site with no SEO plugin, /wp-sitemap.xml. If a plugin replaces that file, submit the address the plugin documents, and confirm it loads. The wp-sitemap.xml guide has the WordPress side.

When to get help

When the address answers 200 in a browser, the URL Inspection live test still says the fetch failed, and you cannot see a robots.txt rule, a manual action or a host error. Reading the live test beside the file the server actually sends is the next step.

More on this subject

Would you rather we fixed it?

SEO audit is $249. A written audit, each finding with its source, and up to 2 hours of fixes done and tested again.

More about this work: WordPress SEO audit

May we measure how this site is used?

A yes notes the pages of this visit and loads Google Analytics. A no keeps and loads nothing. See the cookies page.

If you say yes, we note the pages you look at during this visit and load Google Analytics. If you say no, nothing is kept and nothing is loaded. The site works the same either way. The cookies page has the details.