Google Slow to Update Cache Data?

Sep 26, 2007 • 8:02 am | comments (0) by twitter Google+ | Filed Under Google Search Engine Optimization

Take a look at a query. Notice everything looks fine and dandy.

Now, lets look at the result for that page.

Why is it displaying the cache of a different site? Currently, I see for a cache lookup for But why? Here is the cache information:

This is G o o g l e's cache of as retrieved on 22 Sep 2007 00:58:26 GMT.

In a Google Groups thread, the owner of the site said he or she had a 302 redirect from to in the past, but over two months ago, she stopped the 302 redirect, but Google still displays the wrong site in the cache.

What makes this a bit weirder is that I can get the cache page of the home page if I go this route.

In any event, Googler Susan Moskwa said:

I've seen a couple other users report the same phenomenon recently in our Help Groups. I'm not sure if/how it's related to your 302 redirects, but I've passed your case along to the team to look into further.

So this might be a larger problem with Google's cache operator. It appears Google knows about the 302 change, it also appears they have cached the correct home page. But the operator for a cache: lookup does not appear to work 100% correctly right now.

Forum discussion at Google Groups.

Previous story: Should Google Block AdWords Qualified Professional Pages?
blog comments powered by Disqus