Google bot (search console google)- Sitemap could not be read – General HTTP err

  • Resolved mendje12

    (@mendje12)


    1 year, 10 months ago

    Hello,

    I have a problem with GOOGLE search console about sitemaps. My sitemap is: https://www.mendjeshendoshe.com/sitemap_index.xml. In Google search console, when I Inspect the url of sitemap the error after testing about this sitemap is: Failed-Blocked due to access forbidden (403) and also in sitemaps If I erase and resubmit it, I get “Sitemap could not be read – General HTTP error”.

    I contacted the HOST after they tried some tests like restarting the server, disabled firewall and also suggested that I disable the plugin: WP SECURITY again had the same problem. Then they manually created the file sitemap_index.xml and I tested it with inspect url sitemap address and it showed success, but the status of my sitemap is again: couldn’t fetch, but after contacting the host they suggested me to talk to you. I haven’t activated the wp_security plugin yet.

    The answer and the question related to this topic from my host suggested to you. Host Tech said:
    <quote>”So if I create the file manually it works but if we let wordpress to provide the file dynamically it fails. This confirms that it is a software issue with your xml sitemap generator. I believe you are using Yoast. Please check with them what is this about because this issue is not fixed yet. It was a test that I made by creating the sitemap manually but if I delete that file you will have the same issue again. You can tell them that the firewall is disabled and that your .htaccess is clean (it was reverted back to its original status). Maybe it is another plugin causing conflicts with your redirections. You can revert the changes from CloudFlare back. I won’t suggest enabling your security plugin, I’m almost sure that it is related even when it is disabled. There is one plugin causing the issue for sure, either Yoast or any other plugin that is not redirecting google to the sitemaps file.”</quote>

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @mendje12

    Thanks for reaching out about your sitemap. First, I’ll like to mention that the Yoast SEO plugin generates your XML sitemap dynamically based on your site content; there’s no physical file on the server. I see no reason for Google not to fetch the sitemap as it displays correctly, and there are no errors when validated.

    It’s been mentioned that the new Google Search Console sometimes shows ‘Pending’ as ‘Couldn’t fetch’?incorrectly, and there’s no way of telling the difference. You can try URL Inspection on the sitemap URL. If it says not indexed, it means Google can fetch it. It’s likely just ‘Pending’,?in which case, wait.?

    Thread Starter mendje12

    (@mendje12)

    After doing an Inspect URL, IT SAYS AGAIN: “In Google search console, when I Inspect the url of sitemap the error after testing about this sitemap is: Failed-Blocked due to access forbidden (403)”

    Plugin Support Maybellyne

    (@maybellyne)

    Thanks for following up @mendje12

    403 is often from a firewall and that’s blocking Googlebot; if the sitemap can’t be fetched by URL inspection, the problem is not the Yoast SEO plugin since the sitemap loads fine.

    You’ve tried all the troubleshooting steps that readily come to mind with issues like this – checking Cloudflare, firewall, security plugins, .htaccess file etc. You may consider posting in the Google Search Central Community.

    Plugin Support Maybellyne

    (@maybellyne)

    This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Google bot (search console google)- Sitemap could not be read – General HTTP err’ is closed to new replies.