I heard Google needs more examples of 302 hijacking

[s0s]

If I ran a search engine, and a method emerged for one website to sabotage another in my SERPS, I'd take my eyes off the cash pile for a while and sort it, pretty darned urgently.

What I wouldn't do is dilly and dally, having a PR (public relations that is) man put 'feelers' out for 'examples', and pretty much do nothing for months on end.

I'd tell my SERP quality team to get their data analysis tools out and fix it. Pronto.

To me it looks like a clear case of core product being overlooked in the chase for easy bucks. How often have we seen it before?

[YaxPac]

Originally Posted by jorock

A good source told me that Google only got a few examples of the 302 hijacking problem. Not enough to fix it.

I'd like to compile a list of examples.
Document the whole thing.
help them fix it.

You can't search for inurl:tracker2.php
It must be tripping a denial of service filter.
( NO, I don't think google is intentionally doing this, side effect of omething else. )

resend them to Google, or sticky me and I'll put it together.

Please keep this to just facts.

I missed this thread while researching for 302 Google Jacking data after my web site experienced a case of identity theft and by google jacking.

I am very curious if you ever were able to get feedback on this issue in terms of numbers?

R. Joe

[Marcia]

This thread is well over a year old now, and there haven't been any posts about the issue around forums, nor has Matt asked for any examples in a LONG time. Seems the issue isn't a pressing one any more, judging by the lack of mention. There are other serious concerns people seem to have at the moment.

[YaxPac]

Originally Posted by Marcia

Seems the issue isn't a pressing one any more, judging by the lack of mention. There are other serious concerns people seem to have at the moment.

Marcia,

You make a great point there. It seems that late '04 early '05 there were a number of postings regarding this - then it tappered off both on forums and blogs. But now the 302 Redirection has happened to my site which indicates that a work around for whatever fix Google might have implemented to thwart bad 302's has been circumvented. This *might* be an red flag for web masters to keep a close eye out for a possible 302 re-direct problem.

Of interest I was just notified about an hour ago that on Yahoo when my site shows up it has the same redirect as it has on Google. Yahoo was supposed to have overcome 302 problems some time ago so the fact that my listing was hijacked by the same web sites on both Yahoo and Google is very interesting (in the academic sense).

R. Joe