In my last blog post I suggested to use “Fetch as Google” if you want your content to be indexed quickly. After reading and following the 4 simple steps outlined, some of my readers asked mainly one question:
What’s the difference between “Fetch as Google” and “Fetch and Render“?

 

So what’s the difference between “Fetch” and “Fetch and Render”?

Besides many other useful tools the Google Search Console offers a Google Fetch and Render tool.

You’ll find it in the menu on the left hand side in the “Crawl” sub menu as “Fetch as Google“. This tool offers to either just “Fetch” or “Fetch And Render” a URL.

Fetch as Google

If you leave the slug textbox empty, Google will fetch the homepage. As an alternative to a page you can also enter any directory and fetch its content.

 

Fetch as Google

If you decide to only fetch a page, Google will send out its bot immediately. Fetching a page is a fast process and once done the page will be added to the history table (shows the 100 last requests) where you also can see the status of your request.

Fetch as Google Complete

 

Some of the status codes the Google bot might give back:

  • Complete
    The Google bot crawled your page successfully and reached all resources referenced.
  • Partial
    Although the Google bot could reach and crawl your page, not all resources referenced could be reached.
  • Redirect
    While trying to fetch the given URL Google bot received a redirect response.

 

You can check the details about the results with a click on the table row:

Fetch as Google Result

 

Here’s an example of how the result of a fetch with the status “Complete” will look like:

Fetching as Google

 

Fetch as Google is a fast way to check and detect issues with your site.

 

Fetch and Render

You can also request to “Fetch and Render” your page. This process takes longer than a simple “Fetch” request as it also runs additional resources such as images or scripts and renders the page according to the specified platform.

As a result Google presents you two images that show the difference between how Google sees my site and how a user sees it:

Fetch as Google and Render

Notice the slight difference in the example above, where visitors can see the SumoMe sharebar on the left hand side, but Google bot can’t.

In this case it’s due to the Google bot not being able to get all of the page’s resources. Here the SumoMe code as you can see in the list of all blocked resources that is shown below the rendered page.

Fetch as Google blocked resources

 

The information given after “Fetch and Render” gives a deeper insight on any errors occurred while the Google bot crawled your page. This information can help to fix any these troubles where needed, and to make sure the Google bot can access all the resources you want to be crawled.

 

Bonus Tip

Once your request is completed, whether you asked to “Fetch” or “Fetch and Render“, you will see a button labeled “Request Indexing“. Use this to submit your previously fetched URL for indexing by Google.

Fetch as Google Request Indexing

You can also start the entire process right from your WordPress post editor and have your content indexed by Google in as less as 30 seconds after it’s published.

Watch this short video to see how it’s done.

 

Your Turn

Do you make use of the Fetch as Google tool to check and solve any crawling issues on your site? If so, do you also use it to get your content indexed faster by Google? Please share your thoughts in the comment section below. And if you think this post could help one of your friends please consider sharing it on Twitter and Facebook.

 

Leave a Reply

Your email address will not be published.

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