Google Console Error [Couldn’t Fetch – Sitemap could not be read]

  • Resolved anonymized-12966443

    (@anonymized-12966443)


    4 years, 7 months ago

    Same as Dhruvjha’s issue. I’m using Yoast Plugin I submitted the sitemaps to Google Console. But It is showing error as “Couldn’t fetch” Status. Once clicking it shows “Sitemap could not be read”.

Viewing 5 replies - 1 through 5 (of 5 total)
  • MariusG

    (@marius_codeinwp)

    4 years, 7 months ago

    Hi @heathcliff2013,

    Can you send us a link to your website, so that we can inspect the XML Sitemaps and see if there any errors? In addition, please include a full-page screenshot from Google Search Console, where you are getting this error.

    The user from the ticket you have referred is still using the sitemaps from Yoast SEO, it’s very likely that the issue was fixed soon after opening that ticket.

    We are looking forward to hearing from you.

    Thread Starter anonymized-12966443

    (@anonymized-12966443)

    4 years, 7 months ago

    Meanwhile I have reached out to my hosting to check if the fire or anything is unusual but no.

    It went wrong the moment I option in “Option B: My site is under construction and should not be indexed”. Somehow it is stuck in this mode.

    I’m gonna reinstall my WP site but this time I won’t choose “Option B: My site is under construction and should not be indexed”.

    See what happens.

    Thread Starter anonymized-12966443

    (@anonymized-12966443)

    4 years, 7 months ago

    Outcome: same result :S

    Plugin Support amboutwe

    (@amboutwe)

    4 years, 7 months ago

    I checked your homepage in multiple online tools and don’t see any noindex robots tags. I, also, checked your robots.txt file in case it could not be viewed by Googlebot. As there doesn’t appear to be anything causes the block that we can see, please contact Google for further assistance here: https://support.google.com/.

    Thread Starter anonymized-12966443

    (@anonymized-12966443)

    4 years, 7 months ago

    As promised I will come back on this. I failed to recreate this situation with w3caffeine .com meaning it’s domain extension related. It’s caused by .SITE domain name.

    Bing and Google were able to crawl the site with the new domain name.

    • This reply was modified 4 years, 7 months ago by anonymized-12966443.
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Google Console Error [Couldn’t Fetch – Sitemap could not be read]’ is closed to new replies.