Why use fetch as google tool?
“If you build it, they will come.” That line no longer works for online sites or blogs, especially if your site or blog is dependent on regular traffic. You need traffic and the main source is search engines.
Google is the search engine which amounts for 70% of search engine traffic. Now your site needs to be indexed on google search engine to receive a decent amount of traffic.
You have sweated blood to creating this site with a cool design and amazing content, but how would you feel if no one is able to find it. I know how it feels and have gone through this that’s why I have written this post to make things a bit easier for you.
One of the best ways to optimize your site for google search engine indexing and ranking is to use Google webmaster tools, now known as search console. In the Search Console you have an option “Fetch as Google”, this enables you to test if the google search engine can successfully crawl your site URL. This is useful for identifying any issues with crawling your site URL, and then resolving the issues.
One more important reason for using fetch as google is if you are syndicating your blog content to blog syndication sites, like Inbound.org, Medium, LinkedIn, etc. I wanted to promote my blog so I also syndicated my content to some content aggregator sites.
I soon noticed a drop in the SEO ranking on the original article which was posted on my blog. Prior to syndication of the article, the article had a ranking of 21 for a particular keyword.
After syndicating the content, the article was not even ranked in the top 120 for the same keyword. Google saw the syndicated version as the original article and the one on my blog as a copy. This penalized our SEO rankings for the original article.
I stopped syndicating any other content till I found the reason for this. I searched online and came to know of few other bloggers who have faced similar SEO issue after syndicating their blog content and how they resolved the issue.
Yes, you’re dead right, it’s fetch as google tool in the search console. As soon as you publish your blog post, the next thing to do is to submit this blog post URL to google using the fetch as google tool. This way google knows that your blog post is the original source of content and your article will not be penalized for SEO.
After this, you can syndicate your blog post to other content aggregator websites and you will no longer face any SEO ranking issues.
How to use fetch as google?
I’ll walk you through the whole process step by step of how to use the “fetch as google” tool.
- Login to your search console account. In the left menu, you will see a heading Crawl, under that you will find “Fetch as Google”, click the link. (Refer the below screenshot)
- Once you are on the “Fetch as Google” page, you need to paste your page URL in the area provided (without the domain name which is already preset). Refer highlighted in the below screenshot.
- The newly fetched page will show in the list as below. Click on “Submit to index”. This will open a pop-up window.
- In the pop-up window, select the option “Crawl only this URL” (this will index only this particular page) and click the Go button. This will close the pop-up and once again the list of URLs will be shown.
- Finally, to confirm that the page has been indexed by google, make sure that you see “Complete” under the status. The URL will be submitted to index within a few minutes.
Resolve fetch as google redirected status
When I first tried to use “fetch as google” for one of the URL of my website, I got the status as “Redirected” that was marked as an error. Below is the screenshot of the error
If you click the “Redirected” link you will get information regarding the error. Google considers that as a 301 redirect and shows the server response code.
Most likely you are getting the error because of one of the below two reasons, let’s find out:
- To fix the problem, add a single Forward Slash “/” at the end of your URL to close it, and the google crawler will fetch your page properly. Ideally a URL with or without a “/” should be treated as same, but it’s best to close with Forward Slash to avoid this issue altogether. Refer the below image which shows the URL with “/”.
In some cases, this will resolve the issue and you will get a “Complete” status instead of “Redirected”. If you are still getting the “Redirected” status then, refer the next point which should most likely resolve the issue.
- The redirect status can show if you are not using the correct version of your domain name. First check if you have verified the domain name with www or without www in the site setting.This should be the same domain which you have defined when you installed your WordPress Blog.If you have set your domain in the WordPress as example dot com and in the Google search console you have set the preferred URL as www dot example dot com, then this could most likely be the reason of the error.
In this case, you need to sign into your Google Search Console account, click your site, then “Site Settings” at the top right. Now you have to select the example dot com without the www and you will need to verify the ownership of the domain. Once this is done, submit the URLs again and your issue should be resolved now and you will get a “Complete” status.
It is important to note that you can have the preferred domain as with the www or without www. You do not need to change the domain settings, as there is no difference from SEO point of view if your domain is with www or without. The preference is totally yours.
In this post, I have listed the importance of using the “fetch as google” tool of the Google search console, how to use the tool and fix any errors that you face while using this tool.
I hope you have found this post useful, please share your experience about the usage of this tool. I have spent hours writing this post, hence please spare a few seconds to share this post in your social network.
Get more stuff like this
Subscribe to our mailing list and get interesting stuff and updates to your email inbox.
Thank you for subscribing.
Something went wrong.