How to Fix Sitemap Couldn’t fetch HTTP Error 403

(Last Updated On: October 17, 2019)

Every blogger know that sitemap is very important for SEO and ranking but sometimes we unable to index our sitemap,

we face many errors when we submit the sitemap to  google search console

and we can’t get any solution in google search because there are many reasons behind this

So let’s fix Sitemap Couldn’t fetch HTTP Error 403 General HTTP error

 

Step 1. Login your wp-admin if you are using WordPress and disable cache plugin because sometimes google unable to read your sitemap file because of cache so it’s very important you disable cache plugin if you are not using any cache plugin or WordPress then ignore this step

Recommended cache plugin: W3 Total Cache 

Step 2. Generate your blog or website XML sitemap file from here

Note: if you are using any external plugin for sitemap don’t forget to check your sitemap URL accessible from the browser, always use sitemap URL like this: yourwebsite.com/sitemap.xml 

Step3. Login to your cPanel and upload sitemap.xml file to public_html folder

Step4. After uploading your sitemap.xml file to public_html location login to your google search console and enter your sitemap URL  to URL inspection option in google search console and hit enter button

 

it means google bots able to access our sitemap URL so now our sitemap URL is ready to submit > go to sitemaps option in google search console and add a new sitemap and submit your sitemap 🙂

Note: if you are using cloudflare please remove it and use your hosting providers default nameservers 

I hope you understand every step or still if you have any issue related to sitemaps you can open a support ticket 

 

4 Comments

  1. Aadarsh Roy Reply

    Hey hostkarle blog ,

    Awesome and well written post. I really gain helpful ideas through it and your blogs works as a knowledge-booster for me.

    You have truly suggested an effective steps to fix sitemap couldn’t fetch http error 403. Following the steps will be helpful and helps user to sort out the issue.

    Eventually thanks for sharing such a helpful content.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

This website is using cookies to improve the user-friendliness. You agree by using the website further. Privacy policy