If Google Search Console shows "Sitemap could not be read," it could be due to incorrect URL formatting, permissions issues, or server errors. Check the sitemap URL and ensure it's properly accessible.
If Google Search Console shows "Sitemap could not be read," it could be due to incorrect URL formatting, permissions issues, or server errors. Check the sitemap URL and ensure it's properly accessible.
If you're using WP, submit all of the versions of the sitemaps, not only the main one,
Sometimes it happens for strange reasons, especially with the main sitemap (the one containing the list of other sitemaps),
Lastly, refresh GSC after submitting the sitemaps, it could be fetched but shows the error
Sometimes GSC "remembers" a temporary problem with fetching your sitemap and continues to show the error for some time and re-submitting your sitemap doesn't help.
You can try this technique to re-submit your sitemap: if your sitemap looks like this:
sitemap.xml
try to add a slash in the beginning:
/sitemap.xml
It worked for me about a year ago. Google tries to re-fetch the sitemap a new.
That Googlebot was unable to access your sitemap file due to issues like incorrect URL formatting, server errors, robots.txt blocking access, invalid XML structure with in the sitemap, or the file being too large or complex for Google to process properly.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.