As a Blogger, Fetch as Google is one of my favorite tools. Whenever I write a new Blog post, the next thing I do is navigating to Google Search Console for this one smart tool called Fetch as Google.
Because it helps my blog post to index faster as well as it shows how Google can see my page and how users can see my page.
But sometimes, I face problems with something called Errors.
When we upload the URL, it has to show the status “Complete“. But sometimes, it shows us different names, Which we can consider as an Error.
These are some Errors, we will be facing most of the time.
Partial, Redirect, Not Found, Blocked, Unreachable, & even sometimes the name of the error is “error“. & so on.
But each and every error in the Fetch as Google tools has one solution. Now we will find that out.
Fixing All “Errors” of Fetch as Google in Search Console: Complete Guide
Now when we have to discuss solving errors, We should definitely start with What it is? & How to use it?
- How to run Fetch as Google?
- Fetch Status Errors
- Errors that Allow Indexing
- Errors that do not allow Indexing
- Not Found Error:-
- Not authorized Error:-
- DNS not found Error:-
- Blocked Error:-
- Unreachable Robots.txt Error:-
- Unreachable Error:-
- Temporarily Unreachable Error:-
- “Error” Error:-
- These May be Helpful for You
How to run Fetch as Google?
We basically use Fetch as Google tool for two main reasons.
- To Index our page faster in Google
- To check how Google and Users can see our page.
So, to do that
we enter into Search Console>Crawl and select Fetch as Google.
There we enter our page URL, which we want to Index in Google.
After, we click on that Fetch or Fetch & Render button.
Now we can find the Fetch Status in the fetch History Table down below.
The most common status “Complete”. Which is good and there is no need to look back.
But sometimes, we find some other names which are called Errors.
Fetch Status Errors
Fetch Status Errors can be divided into 2 type.
The Errors Which allows Request Indexing and the errors which don’t allow Indexing.
Errors that Allow Indexing
Partial and redirect errors are errors that allow Indexing. Means, you may be facing the problem with this error, but still, you can request Google for Indexing.
When you are facing this kind of error. Relax, It’s easy to solve them.
The partial error just means, your page will be indexed, but Google may not see some stuff on that page which is hidden mostly because of robots.txt file
Partial Error cannot be seen when we just use Fetch option, It is only visible when you use Fetch & Render Option. This Error can be found only be rendering
Difference between Fetch & Fetch And Render?
Fetch option is the fast process to say Google about our page and request Index.
Fetch & render adds more features to that fetch which is called render.
Render option is to show us how Google can see our page and how users can see our page.
There is a point to be mentioned here.
Fetch option just analyses HTTP responses. So that it can find all errors but not partial error. But render option analyses total page code and shows how Google and users can see our page. So partial error can only get found by Fetch and Render option.
Fixing Partial Error in Fetch as Google:-
Click on the URL in the fetch History table.
Where you can find a page which shows how Google and Users can see your page.
Check how Google is seeing your page. Most of the time it just can’t see comments section. That’s because of your theme or comments plug-in you use which intentionally makes your comment section hide with no-follow tag. It’s not at all problem, you can just be fine, Google doesn’t need comments section. There is no need of solving this error.
Scroll down to bottom,
Here you can find which is the reason for that partial error on the right side of this table.
If the problem is with other sites, you need not do anything. For example:- Comments section blocked by comments plug-in or theme.
If the problem is with your site, you have to check it. Mostly the problem will be your robots.txt file blocking something on that page which stops Google to see.
Edit your robots.txt file to make that visible to Google.
Redirect Errors occurs when you have added URL of a 301 redirected page. Google crawlers may pass through redirects but Fetch as Google tool can’t.
Fixing Redirect Error in Fetch as Google:-
You have to redirect manually.
Check your URL to which URL it is redirecting to.
Copy that redirected URL and Pastes it in Fetch as Google tool.
So that you can solve Redirect error.
Errors that do not allow Indexing
Errors other than partial and redirect, no other error allows you for Indexing. Here are the errors, what they mean? & how to solve them?
Not Found Error:-
After fetching the URL and if you are facing the problem with this Not Found Error, then that page may be an HTTP 404 or 410 page. Which means, there is no such page on your site.
But actually, you may have a page with that URL. The biggest problem here is when you are facing the problem with this error is not only that page, all the pages on your site will show that Not Found Error.
Fixing Not Found Error in Fetch as Google:-
The problem may be big, but the solution is simple.
You may not be selected the preferred domain name.
In the Google search Console, select that setting option on the top right and select site settings.
In the preferred domain section, your option may be in don’t set a preferred domain. Change that to with www or without www.
This could solve your Error. You may have to wait for some time or one day. I don’t know the exact duration as I am not facing this Error, I even couldn’t find anyone saying.
But this is the reason for your Not Found Error.
Not authorized Error means that Googlebot is unable to access that page. Maybe, you may have a password for that page.
When you search for that page in the browser, You will see HTTP 403 or 401 Error page.
Fixing Not Authorized Error in Fetch as Google:-
Your page may be private or you may be using passwords to access the page means that page can be seen only by logged in person.
Even Google cannot crawl such pages unless you remove the password.
Once you removed the password, make sure your page to get indexed in sitemap by checking meta robot tags.
Once your page is on the sitemap, you can Fetch that page.
DNS not found Error:-
The DNS Not Found Error says that Google can’t find your server. This could only happen when you enter the wrong domain name.
FIxing DNS Not Found Error in Fetch as Google:-
Maybe you have to add another property in Search Console with the right domain name.
This means that the resource is blocked by Robots.txt. If you found this error, Fetch & Render the URL. So that you can check How Google and Users can see your pages by clicking on the URL in the Fetch History Table below.
When you scroll down, you can find, what your robots.txt is actually blocking from that page.
Fixing Blocked Error in Fetch as Google:-
You have to update your Robots.txt file by removing the lines which are blocking your page to get indexed.
You can easily update your Robots.txt using Yeast SEO plug-in.
Unreachable Robots.txt Error:-
Means that Googlebot is unable to reach the robots.txt file and stops loading sending this error to us.
Fixing Unreachable Robots.txt Error in Fetch as Google:-
Maybe you have to create a Robots.txt file again following the proper instructions.
This is caused because of server problem. What Google trying to say is that your server is not running properly.
Fixing Unreachable Error in Fetch as Google:-
You should check your server whether it is up and running properly. If you are facing any problem try contacting your hosting service.
Google will not show this error once your server is ok.
Temporarily Unreachable Error:-
This could happen because of two reasons:-
- Your server may have taken soo long to respond to Googlebot. ( OR )
- There may be many Fetch as Google requests taken place at that time. Google may be facing the problem with their server to load the Fetch as Google requests.
Fixing Temporarily Unreachable Error in Fetch as Google:-
You may have to wait for some time and try again later. Because your server or Google server is too busy working.
If the Status just shows Error without specifying any name of the error, that means that Fetch is unable to find out what Error it is.
Fixing that unspecified Error in Fetch as Google:-
This may help you in most cases,
JohnMu from Google
If this could not solve the problem, You can say your problem in Webmaster Central Help Form.