homepage Welcome to WebmasterWorld Guest from 54.205.144.54
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
Become a Pro Member
Visit PubCon.com
Home / Forums Index / Google / Google SEO News and Discussion
Forum Library, Charter, Moderators: Robert Charlton & aakk9999 & brotherhood of lan & goodroi

Google SEO News and Discussion Forum

    
Google Proxy Hijacking Fixed? Major vulnerability possibly fixed...
incrediBILL




msg:3633628
 11:18 pm on Apr 23, 2008 (gmt 0)

I've been a stalwart on the issue of Google Proxy Hijacking for quite some time including lobbying for methods to avoid the problem and it appears the issue may be fixed.

Many people think they are being proxy hijacked that aren't and lately I've been getting a lot of email asking for help and it always turns out to be some other SEO trick and not proxy hijacking.

What is a Proxy Hijacking?

You find your content in the Google SERPs but the link to the site is something like:

http://example.com/proxy.cgi/somepath/yourdomainencodedurl

When you click on that link with your content in Google you see your web pages displayed with the proxy URL in the browser's URL bar and/or it redirects to your site. The problem is the proxy has technically hijacked your content since their domain claims ownership instead of your site.

Current State of Proxy Hijacking

I'm still seeing Googlebot crawl via proxy servers but the resulting proxy hijacked pages stopped showing up a few months ago. I have code on my server that sends different results when Google crawls via a proxy server that makes it easy to detect in the Google SERPs but these results are no longer being found.

Additionally, I went to Google and checked a few proxies that I've been tracking along with some new ones and some are no longer indexed in Google whatsoever and others only respond with 10 pages indexed total instead of the thousands of pages previously returned many months ago.

Proxy Hijacking Summary

Therefore, based on all of the evidence presented, I'm drawing a conclusion that Google Proxy Hijacking may be a thing of the past and no longer a clear and present danger to webmasters.

I think this is no longer a problem and welcome anyone to sticky me if they think they're still seeing proxy hijacking in order to review the situation in details.

Unless I see some compelling stickies, I think this problem is solved, case closed.

Moderator note: As incrediBILL is a moderator, we hare making an exception to the Google Search forum prohibition against requests for stickies in this case.

[edited by: Robert_Charlton at 11:44 pm (utc) on April 23, 2008]

 

kamikaze Optimizer




msg:3633779
 4:50 am on Apr 24, 2008 (gmt 0)

I've been a stalwart on the issue of Google Proxy Hijacking for quite some time including lobbying for methods to avoid the problem...

That is a modest understatement, to say the least.

Thanks incrediBILL for your constant pursuing of a solution to this most disturbing problem.

I vote for a sticky here.

tedster




msg:3633831
 6:31 am on Apr 24, 2008 (gmt 0)

From what I have seen recently, Google does seem to have a handle on the problem now. Haven't stumbled over any proxy urls for a few weeks at least.

incrediBILL




msg:3633879
 7:46 am on Apr 24, 2008 (gmt 0)

From the lack of response to this thread it's easy to draw a conclusion that proxy hijacking in Google isn't much of a problem anymore.

Yahoo on the other hand, but that's a different thread ;)

tshirtdeal




msg:3633881
 7:46 am on Apr 24, 2008 (gmt 0)

You guys are good....keep up the fight!

man in poland




msg:3633942
 9:31 am on Apr 24, 2008 (gmt 0)

I certainly have noticed the number and ranking of proxy pages has dramatically receeded in recent weeks. The only issue that still seems to remain are pages which are BLOCKED BY ROBOTS.TXT on the original site still being indexed under the proxy server domain (because Google simply looks for the robots.txt file on the proxy server domain).

I find this a particular problem because I often like to block a directory with robots.txt for a few days or weeks, and only 'open it up' to search engines once any bugs are fixed - however the proxy server may have got there first, and Google still seems to think that this means that the proxy domain is the original source of the content (based on indexing date, I assume) rather than mine (the original).

Has anyone else observed this?

anallawalla




msg:3633981
 10:20 am on Apr 24, 2008 (gmt 0)

I too can confirm that I can no longer see indexed proxied pages with inurl. I saw them sa recently as two or three weeks ago.

oddsod




msg:3634058
 12:38 pm on Apr 24, 2008 (gmt 0)

If you say so that's good enough for me, incrediBILL. Thanks for staying on the case.

Oliver Henniges




msg:3634433
 7:45 pm on Apr 24, 2008 (gmt 0)

What a pitty: I was almost at the point where I began to understand enough of this matter to seriously damage my competitors;)

Just kidding.

Thank you very much for your efforts and for sharing your findings with us all the time, incrediBILL. Does it also apply to this apparently new form of hijacking, which we recently discussed at length in this thread [webmasterworld.com]?

DanThies




msg:3637285
 3:18 am on Apr 29, 2008 (gmt 0)

I agree, Bill.

There are still some cases where it can happen, but it looks more like a "shoot yourself in the foot" kind of issue now. Your site has to be very untrusted.

activeco




msg:3642804
 1:17 pm on May 6, 2008 (gmt 0)

There are probably a lot more proxies that you can't detect as "a proxy" at all; e.g. http://example.com/ returning http: // mysite.com without 301 or 302.
I would like to see some examples clouding the rankings.

Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Google / Google SEO News and Discussion
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Home ¦ Free Tools ¦ Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About ¦ Library ¦ Newsletter
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved