Today(Wed, April 14, 2010) after updating Google Toolbar, the cache function of PageRank Tool under Google Toolbar is not working. I am able to check the cache of any page through cache option shown in the Google Search snippet, but when I go for the toolbar cache version I am seeing a 404 Error. Following is the snapshot of the Google Toolbar's cache version of Amazon website:

Google Toolbar Error-404 Not Found Error

Also, the Google cache: command is not working. It too is showing 404 Not Found Error.

If you are seeing t he similar thing, please let me known by inputting your valuable comments...

13 comments

  1. analytics  

    April 14, 2010 at 10:40 AM

    I am getting the same thing!

  2. billy_goat_brian  

    April 14, 2010 at 1:14 PM

    Me too. This is annoying. Google is messing around with the cache url and the date format probably to stop automated queries. They're putting a bunch of characters after "cache:". The only way to get the cache right now is doing a site search and clicking the cache link in the SERPs.

  3. Skip Slates  

    April 14, 2010 at 2:27 PM

    I've been getting it since this morning.

  4. live score  

    April 14, 2010 at 11:33 PM

    Yes Mr. Vineet, i found same thing. I appreciate you for your post that always give latest change in search result. Many time i find problem related to seo and same the answer on your post. There are some change in webmaster tool that i have seen today.
    Waiting for some more stuff on your blog. Thanks and keep posting for us.

  5. live score  

    April 14, 2010 at 11:37 PM

    Hey Epert i need some help, can you please give some valuable seo feed back that can be implemented in www.csschopper.com

  6. ryan3prime  

    April 15, 2010 at 5:28 AM

    Happened all day yesterday, and still going on today. Location: New Haven, CT

  7. Skip Slates  

    April 15, 2010 at 9:50 AM

    At least for me it only seems to be happening in the Firefox version of the toolbar. I tried installing the previous version of the FF toolbar - no luck. I tried the IE version of the toolbar and it WORKS!

    Billy goat brian may be right about the automated queries hypothesis. On one occasion this morning, I did not get a 404 error, the message read something to the effect of "your computer may be sending automated queries." I should have screen captured it, but it didn't. The next time I tried, I received the 404 error again. I have not been able to duplicate the queries message.

  8. Vineet  

    April 15, 2010 at 10:15 AM

    Hi Skip,
    You are right, its working fine on IE. But still the cache: command is not working. If Google is doing something about automated queries then why its working fine on IE? It shouldn't be working on IE also...

    Hi Billy,
    Its really annoying. Its become a need for us to check Google cache on many occasions. And with cache: I too get codes sometimes but this time the error is keeping for a longer time. What the Google Guys are doing? Why not they are doing anything to resolve this error...

  9. bogdan  

    April 15, 2010 at 12:09 PM

    Hello people

    Try this: in your address bar (within the google cache toolbar generated urls) change "cache%3A" to "cache:" and your good to go.

    probably it's just a temporary URI encoding problem with their toolbar queries, since SERP cached versions are working fine. My bet is google will have it resolved pretty soon.

  10. billy_goat_brian  

    April 15, 2010 at 12:39 PM

    I just noticed if you change q=cache%3A to q=cache: it works. This is how the Google toolbar in IE is getting the cache.

  11. billy_goat_brian  

    April 15, 2010 at 12:41 PM

    I've gotten that error before as well where it says you've been sending automated queries and sometimes it's right. Usually you have to wait for a bit without sending any automated queries and then the block gets lifted.

  12. MyWebFactory  

    April 16, 2010 at 6:09 AM

    Big bobo by the Big G!

    note to google: Hire some testers first!!!

  13. Admin  

    April 16, 2010 at 7:35 AM

    yes previously I also got the same problem but now I think It has been rectified..now its ok at my end..



Favorite SEO Blogs

Favorite SEO Tips Blogs

Favorite Google SEO Tips Blogs