Gourt Home::Gourt :: 302 Google Jacking
302 Google Jacking is the term given when web page hijacking occurs either intentionally or not on the search engine Google. A page hijack is a technique exploiting the way search engines interpret certain commands that a web server can send to a visitor. In essence, it allows a hijacking website to replace pages belonging to target websites in the Search Engine Results Pages ("SERPs").
Search engines such as Yahoo! have proved not to be as susceptible to this as Google. Meanwhile Google has not publicly acknowledged that page hijacking is a real problem. Because page hijacking is based on a standard HTTP status code (Code 302), the affected pages are not identifiable (as of May 2006) to the search engine database. Google's hands are tied until it develops a database technique to discover likely occurrences of page hijacking.
Have you been Google Jacked?
It is reported that hundreds of 302 Google Jacking pages have been reported to Google. Because it is difficult to quantify how many pages have been hijacked, GoogleJacking.org was founded in May 2006 to help make Google aware of how widespread the 302 Google Jacking problem is. Using the frappr service, visitors can easily add themselves to a map, providing a visual indicator of how widespread the problem is.
Example
The site smallshoes.net is a niche site for women who wear difficult to find sizes of shoes. A common key word search for this web site was "women's small shoes", which when entered on AltaVista, Yahoo!, or Google produces a Page Rank in the top 5. The difference is when this search is done on Google the Search Engine Results Page produces a normal looking listing (#2 as of May 19, 2006):
- Women's Small Shoes
- Directory of stores offering small sized women's shoes.
- www.smallshoes.net/
However, if you click on the title, where you would normally be directed to the URL listed (or in the case of a legitimate 302 redirect request to the appropriate page), you are instead sent to some variation of this URL (the 302 redirect is set up to send you to a different TLD each time).
The end result is that Google's bots will eventually evaluate the site based on its current content. When the bot goes to the redirect URL, it will find a link farm, and the URL will be lowered in ranking, or worse, be delisted.
See also
References
External links
Help to stop 302 Google Jacking
- GoogleJacking.org was founded to make Google aware of how widespread the 302 Google Jacking problem is.
To report spamdexed pages
- Found on Google search engine results
- Found on Yahoo! search engine results
- Found on MSN search engine results
- Found on SEO Forums and link spam discussion.
Search engine help pages for Webmasters
- Google's Webmaster Guidelines page
- Yahoo!'s Search Engine Indexing page
- MSN Search's Site Owner page
Other tools and information for Webmasters
- DMOZ Open Directory
- Online tool that detects spam techniques on web pages
- A paper explaining various methods to determine webpage/blog spam
- A public, searchable database of blog spam pages or spam blogs
- AIRWeb' 05: First Workshop on Adversarial Information Retrieval on the Web - Research on search engine spamming
Internet terminology | Spamming | World Wide Web | Search engine optimization
Suchmaschinen-Spamming | Spamdexing | 検索エンジンスパム | Link spam | Поисковый спам
"302 Google Jacking"