Wednesday, February 23, 2005

Google and the Mysterious Case of the 1969 Pagejackers

Lost a lot of traffic from Google recently? Slipping in the SERPs? You've heard of the Google Bomb, Google Whacking, the Google Dance and Googlisms, but there's a new Google-word you might be interested in if you're losing your Google Juice. What is this new term? I call it 302 Googlejacking. The problem seems to have been around since at least August 2003, and is commonly known as the Google 302 Pagejacking issue. To be fair, it has affected other search engines as well.

If you're curious, there are some things you can check that will show whether or not you've been afflicted by what some people call a bug at Google. (Who knows, maybe it's just a 'feature' we don't understand. ;) Also included are some side notes on the 1969 cache bug/feature that might be related, Google Update Allegra, a poll on the big three and more. If you're into SEO, read on.

Googlejack Test

Type the following into the nearest Google searchbox:

all inurl:yourdomain.com

Look through the results. If you see a Title and Description that are identical to your site with the URL for another site underneath it, you may have been pagejacked, or as I say it, Googlejacked.

Technical Details:

Two primary types of redirects are used on the web - 301's and 302's. A 301 redirect means 'moved permanently.' This is the type of redirect you should use most of the time if you care about search engines. The other type, a 302 redirect, basically means 'moved temporarily.' When someone redirects to your site using the 302 method, Google seems to be associating their website (i.e. their URL) with your page (i.e. your CONTENT.)

If you want to read more, please, visit the original source at kuro5hin.

Article By kpaul

###

No comments: