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:
2009-2012: Google has implemented an annoying "feature" of running a JavaScript on their search page as you click on a search result or cached link in the search results. This JavaScript re-designs the hyperlinks to lead back to Google so Google can track what search links you are clicking on. The cutting/pasting/&strip=1 technique will only work IF Google is not "hijacking" its own search results. If the &strip=1 technique is not working, you need to disable JavaScript in your browser. Disabling the JavaScript prevents Google from hijacking the cached link. In a work environment, ask tech support for help to disable JavaScript. . UPDATE - Disabling JavaScript worked until Feb 2013 - Keep reading below to see what happened in 2013)
2011-present: Google search results no longer display a "cached" option directly in Google's search results. This change happened as Google implemented a new "feature" called "instant preview". In your Google search results, hover your mouse over a search hit that you are interested in. While hovering over the hit... A pair of >> arrows should appear just to the right of the hit. Now hover your mouse over the >>, and a small screen shot of the web page should appear. I can confirm that this "instant preview thumbshot" is causing live hits on the target website from Google, as Google goes out in real time to grab the web page from the target website to make the thumbshot . Repeat.. Displaying the "instant preview" of a search hit causes live hits to the target web server from Google. The target web master will know that his web page is being "instant previewed" in a Google search. Google also decided that the "cached" link should now be displayed in the "instant preview" window pane. There are many researchers who are angry with Google about this as shown on this thread. From 2011 onward, you can no longer get to Google's cached link to copy/paste/&strip=1 without invoking the "instant preview" pane (which will cause live hits to the target web server). The fix once again is to disable JavaScript in your browser. This would eliminate the entire "instant preview" feature... and Cached once again is listed directly in the Google's search results where it had always been for the past 15 years. BUT this solution only worked until Feb 2013.
Feb 2013 - current: By now you have previously disabled JavaScript in your browser. And you had successfully been able to "leap" directly to the "text only" version of cached, by copying & pasting cached links and adding &strip=1 onto the end of the cached address. But once again Google has managed to ruin it. When Google detects that JavaScript is disabled in your browser, Google now sends search results to you with ALL the links pre-hijacked back to Google. Adding &strip=1 onto the end of a hijacked cached link does not work - you end up viewing a full version of the cached page with all of its embedded graphics, etc being downloaded by you directly from the target website.
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%2Fsearch%3Fq%3Dcache%3Aq73OkFyPlu4J%3Anavigators.com%2Fisp.html_etc_etc_etc
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:
http://webcache.googleusercontent.com/search?strip=1&q=cache:www.navigators.com/isp.html
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
'at' navigators.com
If you use email, put "internet training" in the subject of the
email.
Copyright © Information Navigators