What to Do When Search Console Says Your Sitemap Couldn’t Be Fetched
Does your sitemap URL open normally in a browser, yet Search Console says it “couldn’t be fetched”? The short answer is that seeing the file is not enough. You also need to verify that Google can actually read the exact URL you submitted.
“Couldn’t fetch” does not mean your site has disappeared from search. It usually means Google was unable to retrieve the sitemap file properly.
Start by checking the URL you submitted.
- A sitemap that opens is not necessarily a sitemap Google can read.
- WordPress makes it easy to submit the wrong URL.
- Follow these steps before resubmitting.
- The fix depends on the cause.
- If the URL is the problem, choose one standard.
- If access is blocked, check your server and security settings.
- If the XML format or file size is the problem, reorganize the structure.
- Repeatedly resubmitting it is not the solution.
- Manage your sitemap settings and robots.txt with SOHO SEO.
- What to do first on my site
- WordPress Resources
- Frequently Asked Questions
A sitemap is an XML file that tells search engines about the important URLs on your site. XML is simply a file format that lists text and URLs according to a defined set of rules.
Search Console groups sitemap statuses into categories such as “Success,” “Couldn’t fetch,” and “Has errors.” Submitting a sitemap can help Google discover URLs, but it does not guarantee that every URL in the file will appear in search or be indexed.
WordPress has included built-in sitemap functionality since version 5.5. If you have not enabled a separate sitemap feature, the default URL is usually /wp-sitemap.xml.
Just because the sitemap opens does not mean everything is fine.
A sitemap that opens is not necessarily a sitemap Google can read.
The problem often starts when WordPress core, an SEO plugin, caching, or security settings generate different sitemap URLs.
For example, you may open the URL generated by a plugin in your browser but submit the older core URL to Search Console. If both URLs load on screen, the situation becomes even more confusing. One may be the file currently in use, while the other may be empty or outdated.
Google lists robots.txt blocking, an incorrect submission URL, a 404 error, and an unavailable server among the reasons it may fail to fetch a sitemap. The robots.txt file tells search engines which areas they may access and which they should avoid.
Also, the Search Console report may show only sitemaps submitted through that screen or related feature. If a sitemap discovered by Google through robots.txt does not appear in the report, that alone does not mean something is broken.
A URL can open in your browser without being readable to Google.
WordPress makes it easy to submit the wrong URL.
Do not stop at confirming that the sitemap exists. You need to check whether Google can read the exact URL you submitted without logging in, being blocked, or receiving an invalid format.
- Copy the sitemap URL exactly as it appears in Search Console.
- Open it in a browser and make sure it does not redirect you to the homepage.
- Check that it does not display a login screen, security check, or 404 page.
- Open site-address/robots.txt and compare the URL listed after Sitemap.
- Look for any Disallow rule that blocks the sitemap.
- Run a live test in Search Console’s URL Inspection tool.
- Open each child XML file referenced by the sitemap index.
In the live test, crawling should be allowed—effectively “Yes”—and page fetching should be reported as successful. A sitemap index is a list of multiple child sitemaps, so confirming that the index itself opens is not enough.
If even one child URL returns a 404, redirects elsewhere, denies access, or displays an HTML page, the full check may be blocked. If HTML appears instead of XML, the URL may be wrong or the server may be returning the wrong response.
You need to check the child files too.
Follow these steps before resubmitting.
The fix depends on the cause.
If you use only WordPress core and do not have a separate sitemap plugin, start with /wp-sitemap.xml. If an SEO plugin provides your sitemap, it is better to use the actual URL specified by that plugin as your reference.
The key is not to submit both the core and plugin URLs indiscriminately. Choose one active sitemap generator and make sure the same URL is used in robots.txt and Search Console.
Use one consistent URL.
If the URL is the problem, choose one standard.
Remove any robots.txt block, correct the wrong URL, and make sure the server is available. If the sitemap is visible only after logging in, Google cannot read it either.
The fact that the sitemap opened on your computer is not conclusive evidence. You cannot assume that your browser and Google received the same response, so check both robots.txt and the live Search Console test.
Relying only on what you see on your screen can leave problems undetected.
If access is blocked, check your server and security settings.
Invalid characters or incorrect XML syntax and tags can also cause a sitemap to fail. A character such as & in a URL may not have been encoded according to XML rules, for example.
A sitemap containing more than 50,000 URLs, or an uncompressed file larger than 50MB, must be split into multiple files. When that happens, use a sitemap index.
The format and file size must meet the requirements too.
If the XML format or file size is the problem, reorganize the structure.
The most common reaction is to think, “I’ll just submit it again.” But if the underlying problem remains, you will simply repeat the same failure.
Google may retry fetching a sitemap for several days after an initial failure. If the attempts continue to fail, Google may stop trying to read that sitemap URL, so fix the problem first and resubmit it afterward.
Fix it first. Resubmit it afterward.
Adding URLs to a sitemap also does not guarantee that every page will appear in search. A sitemap helps Google discover and crawl URLs; it does not force them into the index.
Manual checks are free, but opening each sitemap and child XML file and comparing them with robots.txt can become tedious. If repeated checks are too much work, you can choose a paid or credit-based tool that checks your configured sitemap and robots.txt from an external server, but weigh the cost and the use of an external server carefully.
Manual checking is possible, but it becomes burdensome when repeated.
Repeatedly resubmitting it is not the solution.
If sitemap URLs are scattered across different places or WordPress core and a plugin are generating different versions, first decide which sitemap should be the standard. SOHO SEO lets you enable or disable standard XML sitemaps and Google News sitemaps under Sitemap, making it useful for managing which sitemap features WordPress uses.
If you also need to review the Sitemap URL or blocking rules in robots.txt, you can edit the file under SOHO SEO’s robots.txt & llms.txt section. Even after changing the settings, however, you must separately verify that Google can actually read the result using Search Console’s live test and by checking the child XML files.
Manage your sitemap settings and robots.txt with SOHO SEO.
If you use only WordPress core, first make sure the default URL matches the Sitemap URL in robots.txt. If you use an SEO plugin, use the single sitemap URL provided by the active plugin as your reference.
If the URL opens but continues to fail, use the live test to check for a security screen, login requirement, server error, or an incorrect response left in the cache. The correct order is to fix the error first and resubmit the sitemap only afterward.
- Is the submitted URL the sitemap currently in use?
- Does the browser return a 200 response and valid XML?
- Is robots.txt allowing access to the sitemap?
- Do all child sitemaps open successfully?
- Does the live test show that crawling is allowed and fetching succeeded?
- Did you resubmit only after completing all of these checks?
Ultimately, the answer is straightforward. Do not keep resubmitting the same URL. Choose one submission URL and fix its access and format first.
It will be read successfully only after the underlying cause is fixed.
A sitemap error is not solved by repeatedly clicking the submit button. It is a matter of aligning the sitemap generator and access rules. First decide which sitemap you will actually use, then confirm that the same URL appears in robots.txt and Search Console.
If you need to manage sitemap settings and robots.txt together in WordPress, SOHO SEO can handle that task. Even after configuring it, the process remains the same: verify the result with a live test and by checking the child XML files.
What to do first on my site
Q. If the sitemap opens in my browser, doesn’t that mean it’s working?
A. Not necessarily. Check for robots.txt blocking, a login screen, or a server error, and review the results of the live Search Console test as well.
Q. What should I check first on my site?
A. If you use only WordPress core, first compare /wp-sitemap.xml with the Sitemap URL in robots.txt. If you use an SEO plugin, use the URL provided by the currently active plugin as your reference, then check the child XML files and the live test results.
Q. Can a tool make this problem easier to solve? Which tool should I use?
A. You can use a tool that automatically checks your sitemap and robots.txt. It may charge a fee or use a credit-based model, and the check may run on an external server, so review the cost and data-handling practices first.
Q. Can I manage my sitemap and robots.txt in one place?
A. SOHO SEO’s Sitemap section lets you enable or disable standard XML sitemaps and Google News sitemaps, while its robots.txt & llms.txt section lets you edit robots.txt.
You can manage both settings in one plugin, but that does not mean the plugin verifies whether Google can actually access them. After making changes, you still need to run a live Search Console test and check the child sitemaps.
WordPress Resources
Frequently Asked Questions