What the error actually means
The message only tells you that the crawler either could not get the file or could not parse it. Those are two different problems. The first is about access: the address, redirects, server protection. The second is about content: format, stray characters, broken structure. Until you know which one you have, changing things at random just wastes time.
Two small notes. Right after you add a sitemap, the status can stay vague because the crawler has not visited it yet. And the status reflects the last attempt, so after a fix you need to resubmit the file.
Step 1: open the sitemap the way a crawler sees it
Paste the sitemap URL into an incognito window, so your login and cache don't hide anything. Then open the Network tab in your browser's developer tools and check the response code. The file should return 200 and contain XML. Typical problems:
- 404: the path is wrong, or the sitemap is no longer generated (a plugin was disabled during an update, for example)
- 5xx: the server struggles to build a large sitemap on the fly
- a login prompt: the sitemap is locked together with a staging version of the site
- very slow loading: the database assembles thousands of records on every request
- 200, but you see the homepage or an error page instead of XML
Wrong URL, redirects and the wrong property
A very common cause is a mismatch of addresses. The sitemap was added with http while the site runs on https, or without www while the main version uses www. The crawler hits a redirect and does not always reach the file. Submit the final address of the sitemap, with no redirect chain.
Also check which property in Search Console the sitemap belongs to. If the property was verified as a URL prefix for one version of the address and the sitemap lives on another, you get a conflict. A domain property removes that problem. If your site has separate subdomains, say for different regions, each needs its own sitemap and property. And make sure the file name is right: some systems create sitemap_index.xml or wp-sitemap.xml instead of sitemap.xml.
Blocked by robots.txt or bot protection
Open robots.txt and confirm the sitemap path is not disallowed. Sometimes a whole technical folder is blocked and the XML file goes down with it.
The second case is trickier: everything opens in your browser but not for the crawler. A hosting provider or security service may treat the search bot as suspicious traffic and return a 403 or a verification page. It often shows up right after moving to a new host or switching on a protection layer. Check the server log to see which status code Googlebot or Yandex's robot receives when it requests the sitemap. If you see 403 or a captcha, set up an exception for verified search crawlers.
Format and size problems
If the file opens and returns 200 but the panel still complains, look inside. Run the sitemap through any XML validator; it will point to the line where the structure breaks. The usual suspects:
- a space, blank line or invisible character before the XML declaration
- a PHP warning or a piece of HTML inside the file
- unescaped characters in URLs, such as an ampersand in parameters
- a missing or incorrect namespace
- an encoding other than UTF-8
- a compressed file served with the wrong content type
- more than 50,000 URLs or more than 50 MB uncompressed in a single file
After the fix, and when to call in help
Fix the cause, open the sitemap once more in incognito, and resubmit it in Search Console and Webmaster tools. Check the status again after a few days. If every check passes but the error stays, remove the sitemap from the panel and add it again; sometimes the status simply gets stuck. Write down what caused it: a change of hosting or a CMS update can bring the problem back.
While the sitemap is not processed, your site does not disappear from search, because crawlers keep finding pages through links. But for online stores with large catalogs and sites that launch new sections, indexing will slow down noticeably, so don't leave it for months.
If you have gone through the list and still can't find the cause, or you would rather not dig through server logs, this is ordinary technical SEO work. The markdev team can run an audit and fix indexing as part of SEO optimisation in Uzbekistan. Describe your situation and we will suggest where to start.
FAQ
Will my site drop out of Google if the sitemap can't be read?
No. Crawlers still find pages through internal links. But new or deeply nested pages get indexed more slowly, especially on large sites.
Why does the sitemap open in my browser but Search Console reports an error?
Usually the server blocks the crawler, there is a redirect between address versions, or HTML is returned instead of XML. Check the server log and the response in incognito mode.
I fixed everything. Do I need to wait?
The status does not update instantly. Resubmit the sitemap and check again after a few days. If the error remains, delete the sitemap from the panel and add it again.
Is listing the sitemap in robots.txt enough?
The Sitemap directive points crawlers to the file, but submitting it in the panel gives you a report on its status and errors. It is best to use both.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.