Slashdot Mirror
Google AdSense Meta Refresh Hijacked
aaronwall writes "With the latest Google Update Bourbon it appears that Google has had their AdSense site hijacked in the search results by a meta refresh. In March GoogleGuy commented that this sort of activity usually happens to low quality websites."
for those too lazy to RTFA, it appears google adsense wasn't exactly 'hijacked', but was victim of its own slightly buggy (at the moment) trust algorithms. from the comments there, it's apparantly only a real hijack if visitors get something other than a 301 as well in an attempt to divert their visit. here's what the 'hijacker' himself had to say on jensense.
"I want to thank JenSense and others for posting this thread. I just got off the phone with two different tech writers explaining why I would have a meta redirect on my site. It isn't an attempt to profit from either Google's page rank or some cloaked affiliate link. I am no hijacker. In fact, I'm not sure how I could in any way benefit from this link. The simple fact is this: I write and syndicate articles all over the web. I used to put into those articles direct links to sites I was talking about. A couple years ago I had a problem when I had written and syndicated several articles about GoTo.com when they changed their name to Overture. There were dozens of websites to notify and ask them to update the links in my articles. So I decided to begin using meta refresh redirects rather than listing the URL's directly. I can then keep the links current in all the articles I write. Hopefully Google will look at this and decide to make some changes so this won't occur. It's hard to believe I got a number 1 listing without trying."
This problem has been around awhile, and is part of the larger problem of search engines filtering out duplicate content. Great for the users, but it can be a real problem for site owners suffering from plagiarism or content theft. There's some information at the Copyscape plagiarism search service about what you can do about it.
Actually, Google AdSense already was at the very top of the page, even when it was "hijacked." Google puts its own sponsored links before the actual search results.
FireFox can't block text ads that aren't in an iframe.
you can right-click and select 'block iframe'...of course, I might be wrong on that point
Read that exchange again and reflect upon just how obviously wrong you are. Reading and comprehension skills aren't overrated.
Adolescent sniping is all well and good (this being Slashdot and all) but this should be a big deal to you even if you refuse to take the time to understand the specifics (RTFM).
/.) but now they themselves have been a victim of a '302 hijack'
Here's what's going on. Google has a flaw in their algorithm in the way it deals with 302 redirects. Instead of following the internet standard of following the 302 redirect to the new location and indexing that, Google sometimes applies the information, PageRank, and Google ranking position of the 302 destination page back to the page doing the redirecting.
This means that a third-party (usually a shady webmaster) can steal the ranking position of a competitor's site. The original site is usually removed entirely from the Google index further compounding the damage.
Google has repeated denied that this problem exists (here on
If Google can be hit by it - anybody can be hit by it. This is big enough to seriously f'up the Internet - get it?
What would they call him about? He did not actually do anything wrong.
He hasn't got any form of contract with google and he hasn't broke any laws...
I believe Bourbon is the name of this Google update. The slimy search engine optimizers (whose posts you can read if you click the link to webmaster world) name the updates of Google's index in order to keep track of them easier. If you read a little of the thread, I believe they refer to code words for past updates as well.
If the 302 page is just a redirect, why do they apply the redirectee's pagerank to the 302er's page, and not the other way around (apply the 302er's pagerank to the ridirected page)?
They don't. A PageRank is something that Google assigns to a URL rather than a page, based on how many pages containing the keyword links to it and some other stuff. The issue is that Google finds two URLs that lead to the same page, one is the page itself, and one is a 302 redirect.
Now when you search for a term and this page hits, Google doesn't want to display two links to the same page, so Google it has to decide which is the canonical address for the page. The way that it does this is simply to take the URL with the greater PageRank as the canonical URL, and returning that.
The issue is that this allows one, in theory, to hijack google entries by 302 to the page in question, and getting a higher pagerank for your URL then the real one. In this case the old URL will be suppressed, and Google will link to your URL instead. Once this is done, you can change your page to a phishing page or something, and get people.
Note, however, that if Google did not follow 302s, then this could still be done by simply proxying the actual page. If a request to my URL simply made the webserver fetch your page an return it, Google could never tell which was the real page, and which was the copy. It would have to return both (in which case I would be first if I had greater pagerank) or suppress one, and then they are back to the canonical problem.