Issues with Cached at Google
Clicking on Google's cached link for a web page (html)
almost always make hits to the live website,
A typical Google Search hit:
Clicking on a cached link downloads the text of a web page from Google's cache to your browser. Google does not cache the embedded multimedia such as the graphics. So your browser will make hits directly on the live website to download the remainder of the webpage.
Want to jump directly to Google's cached "text only" version of a webpage? Try this process:
Many internet researchers incorrectly assume that clicking on Google's "cached" in a search result will only make hits to Google, and make no hits to the search target's website. Truth is, clicking on "cached" will almost always result in unusual hits to the target web server. Consider the following sequence of events.
Let me walk you through the history of using Google's cached search links over the past many years. This page assumes you are already familiar with persona concepts described on persona tips .
1997-2009: Google does offer a "Cached text only" version of the web page, but normally you can't get to the text-only cached page until you first view the regular version of Google's cached page (which by then will have downloaded the embedded multimedia from the target site). Here is the work around:
I do have a solution for this.. but it is UGLY and tedious. You have to essentially copy and paste the cached address... and then EDIT the heck out of it to remove all the Google Hijacking. Only then can you add &strip=1 onto the end of the corrected cached link to directly view the "text only" version of the target webpage from Google's cached ( = zero hit on the target website)
The Google hijacking has made the following changes to the cached URL:
Here is what a cached link looks like that has been hijacked by Google, followed by the same cached link without being hijacked
Here is the ugly procedure to fix this.
The resulting URL still needs to be edited to remove the ASCII/Hex codes. Below you can compare a partial example of what your link now looks like, vs what it should look like without any hijacking. Note I have inserted blank spaces in the second address so you can see the text lined-up. When you do the edits, do not leave any spaces in the final URL.
webcache.googleusercontent.com / search ? q = cache : q73OkFyPlu4J : navigators.com / isp.html
In this example above "%2F" needs to be replaced with just "/" , " %3F" needs to be replaced with "?", etc.
Here is a list of edits you may need to change:
Finally.... after all these edits... don't forget to add &strip=1 onto the end of the cleaned-up url. And hit enter to leap the text-only version of Google's cached. I know... this is an ugly tedious fix.
April 2013 - current = the technique described at the
very top of this page.
You start with this address: http://webcache.googleusercontent.com/search?strip=1&q=cache:
and add to the end of it the specific URL you are interested in for example:
you will need the complete URL of the target web page - which you can extract from Google's hijacked cached links using the techniques described in "Feb 2013 - current" section of this web page.
Maybe eventually some clever plug-ins might be developed similar to these (sorry - the plug ins below do NOT solve the current Google hijacking issue)
Contact me at 703-729-1757 or Russ
If you use email, put "internet training" in the subject of the email.
Copyright © Information Navigators