WebProNews

With a first look at a site:familyonetransportation.com query, everything seems fine. But with a look at the cache:familyonetransportation.com result for that page, the picture becomes much more clear.

Now the question is why is it displaying the cache of a different site? This shocking information was revealed in a Google Groups thread, where the owner of the site said he or she had a 302 redirect from FamilyOneTransportation.com to ShuttlesInOrlando.com in the past. But some two months back, even when she stopped the 302 redirect, Google is still displaying the wrong site in the cache.

In an event, Susan Moskwa from Google explained, “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.”

There is a big problem with Google's cache operator. It seems that Google is aware about the 302 change, and that they have cached the correct home page. The operator for a cache is not working properly right now.

Comments

Tag: