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."

25 of 122 comments (clear)

  1. bring in the clowns by jack_call · · Score: 5, Funny
    In March GoogleGuy commented that this sort of activity usually happens to low quality websites
    1. Yes! I've noticed it alot on /.
    2. I for one welcome our new AdSense overlords
    3. in soviet russia low quality websites hack YOU!
    4. I host a low quality website You insensitive clod!(tm)
    --
    This is my sig. There are many like it but this one is mine. My sig is my best friend. It is my life.
    1. Re:bring in the clowns by sound+vision · · Score: 4, Funny

      5. In Korea, only old people hijack sites.

    2. Re:bring in the clowns by stlhawkeye · · Score: 4, Funny

      1. Recite tired Slashdot attempts at humor 2. .... 3. Profit!

      --
      "I have never won a debate with an ignorant person." -Ali ibn Abi Talib
  2. for those too lazy to RTFA by professorhojo · · Score: 4, Informative

    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."

    1. Re:for those too lazy to RTFA by ad0gg · · Score: 4, Interesting

      It is a hijack. What he is refering to is that he isn't a hijacker since he isn't profiting off the link. He using the common 301 redirect hijack that has plague google for a while. If you view the cache of his website, you'll see that googlebot is getting a different page than normal users. Googlebot is getting a 301 to adwords. The inbound(trust) links are credited towards the hijacking site as seen here. If you check the first result, you'll notice no link to the hijackers page yet is credited as an inbound link.

      --

      Have you ever been to a turkish prison?

    2. Re:for those too lazy to RTFA by hankwang · · Score: 2, Informative
      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.

      That's not what I read there. The TrustRank issue was mentioned, but that's about sites that are linked to from Yahoo's RSS feed and thus suddenly from one day to the next are linked to from many sites that use those RSS feeds. Apparently, obtaining a massive number of links within a day's time triggers some spam filter in Google.

      Page hijacking is normally that a big website uses a redirect to a small website. Then Google sees that the big website's redirected page has the same content as the small site's page, and throws out the small site's page from the index due to duplicate content. However, this is not the case here since the small site (hijacker) should not be able to trigger the dupe filter for the big one (Google), so it must have been something else.

      That you can get a pagerank 9 on a redirecting URL was already well-known, but that won't help you since the pagerank only counts for the target of the redirection and will not increase the pagerank of other pages on your own website.

    3. Re:for those too lazy to RTFA by Eric+Giguere · · Score: 2, Interesting

      As someone who's written books with actual URLs on the printed page, I can understand his desire to have some way to update stale links without having to track down and change every copy. Automatically redirecting is not a big deal -- this is how TinyURL and other similar (and useful) services work. Most of the printed links in my new book (see below) are done in this way to keep them from breaking when the destination site changes things around and they don't bother to redirect incoming links to the correct location.

      There is a difference between "redirecting" and "hijacking". Redirection by itself is not hijacking.

      Eric
      Buy your dad this book for Father's Day
    4. Re:for those too lazy to RTFA by Buran · · Score: 4, Interesting

      Just to clarify that a bit -- 301 redirects are not a hijack. They just mean that a resource is 'moved permanently' and search engines will change their databases to point to the new location. I have done this with two paths on my own website here at work and in time Google picked up on the redirections and cleaned its database. It's also useful because this way visitors who got to the site by clicking on old links don't get 404 errors and lose interest -- they just get redirected to the correct page. (It's implemented as ModRewrite instructions in the htaccess file for the site).

      It's only a hijack if you're specifically targeting search bots with customized pages and doing sneaky things that way. Which this guy might or might not be doing ... I couldn't verify anything in that blog post. None of the tests listed to reproduce what is described worked -- no hijacks are apparent anywhere, or even the guy's site, in the search results..

  3. Out of date by Spez · · Score: 3, Interesting

    Its not even true anymore if you search for "Adsense" or "google adsense" in google, you'll get the Google Adsense page.

    --
    I wouldn't mind you in my head, if you weren't so clearly mad -Lews Therin Telamon
  4. Content hijacking by manmanic · · Score: 4, Informative

    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.

  5. Re:So, ummm... by th3space · · Score: 3, Funny

    Of *course* I light him on fire...how the hell else would I get the point across to him?! He has to learn to obliterate ads from my view, and conflagration is really the most effective tool at my disposal...if only I could have a piece of software that would do these things for me, I'd save a fuck ton on foxes...

    --
    "How like you to drag your keyboard to a gun fight." - Aaron Bedard (BANE)
  6. Re:Easy Fix by Doros · · Score: 3, Informative

    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.

  7. Wha?? by Intron · · Score: 5, Funny

    When I google too much bourbon, my senses get hijacked, too!

    --
    Intron: the portion of DNA which expresses nothing useful.
  8. Google cloaking the cause? by Anonymous Coward · · Score: 5, Interesting

    In Googleguy's comment, he says that "spammy" sites with low pagerank are more likely to get "hijacked".

    Recently, Google's AdSense pages made headlines for cloaking - something they rectified by temporarily imposing sanctions upon the AdSense pages.

    It seems to me that the resulting low pagerank for the AdSense pages would quite easily account for the fact that they got "hijacked".

    So basically, Google did something many people (a.k.a. whiny morons) thought was "spammy", they subjected themselves to the same sort of punishment they dole out to "spammy" pages to shut up the whiners, and, as a result, they ended up having the same minor bug that affects "spammy" pages affect their own pages.

    Big deal.

  9. Hey guys - this is a BIG deal by Gieckboy · · Score: 5, Informative

    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).

    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 /.) but now they themselves have been a victim of a '302 hijack'

    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?

    1. Re:Hey guys - this is a BIG deal by bigberk · · Score: 4, Interesting
      This is big enough to seriously f'up the Internet - get it?
      Oh come on, you're exaggerating. A failure of 10 root DNS servers is big enough problem to seriously f'up the Internet. The mishandling of 302 redirects allows easy mischief and much confusion, but no catastrophic problems as far as I can tell.
    2. Re:Hey guys - this is a BIG deal by Frank+T.+Lofaro+Jr. · · Score: 2, Informative

      302 redirects are temporary, 301 is permanent.

      Following a 302 and using the resulting page in the index would be breaking spec.

      If I give you a URL and it 302 redirects somewhere, and tomorrow I change the redirect, remove the old redirected to page (assuming it is all on my site) and put a new one where the new 302 points to - your links will get broken if you threw out the original URL and kept where it (originally) pointed to.

      E.g.

      a ---(302)---> b

      I give out URL a.

      Then, I change where a points

      a ---(302)---> c

      deleting b and creating c at the same time.

      If you keep using URL a like you are supposed to, you are OK. If you treated "a" as a 301 and kept URL b, you now get a bad URL.

      Now one could say treat 302 as a 301 if it crosses sites. This would stop most 302 Google poisonings, but what if I have multiple domains and I am doing something legitimate (e.g. make topicsubtopic.com point to topic.com/subtopic until I make topicsubtopic its own independant site). In which case it would hurt me. Or treat a 302 normally, but treat it as a 301 if the destination page is reachable via a non-redirect link. (people could make links to 302 destinations then and break things). Of course one could decide to treat a 302 normally, unless something on the same domain points directly at the 302 destination. So if site A 302 redirects to a page on site B, as long as site B itself has a non-redirection link to that page - then Google could treat the 302 as hostile (throwing it out or treating it as a 301). But domain level assumptions are bad - 2 unrelated entities can share a domain, and 2 separate domains can be controlled by one (or cooperating) entities.

      One could also create a new meta tag that means I allow the following pages/domains/etc to 302 redirect to me - if it is not there - Google could treat the 302 as a 301 or not index it. That would be the cleanest solution I think.

      --
      Just because it CAN be done, doesn't mean it should!
  10. Re:The site's registered with 'real' information, by localzuk · · Score: 2, Informative

    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...

  11. I saw this two weeks ago with "Google" by DeadSea · · Score: 4, Interesting

    Two weeks ago if you searched for "google" on www.google.com, the first result that you got was https://desktop.google.com which redirects to the google home page. Google desktop seemed to have hijacked the google search homepage!

    Of course, the slashdot editors rejected the story.

    Google needs to adjust their canonicalization algorithm so that a page the redirects is not chosen as the canonical url.

  12. Re:So, ummm... by th3space · · Score: 2

    Point. I'd offer up some explanation about how I'm busy today or this, that and the other...but I really don't know how the hell I overlooked that...

    I am shamed, now and forever more.

    --
    "How like you to drag your keyboard to a gun fight." - Aaron Bedard (BANE)
  13. Slashdot blacklists itself! by Animats · · Score: 4, Funny
    Yesterday, the Slashdot home page was, instead of showing Apache headlines, showing a message that the Slashdot RSS feed had been blacklisted. Apparently, Slashdot's RSS feed server blacklisted Slashdot's own home page builder.

    Yes, you too can shoot yourself in the foot.

  14. Re:Hijacked? No, ESCORTED. by adpowers · · Score: 3, Informative

    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.

  15. Re:I don't get it by hanssprudel · · Score: 2, Informative

    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.

  16. Not only that by broothal · · Score: 3, Interesting

    Check the pagerank of this site and take a wild guess whom they hijacked...

  17. my thoughts as a 'victim' of this process. by Eric+Coleman · · Score: 4, Interesting

    From reading the responses here and from the last time this topic surfaced on slashdot, it seems as though people don't fully comprehend the crappiness of the problem.

    I run a game programming website as a hobby, so my livelihood doesn't depend on google's ranks. But my page rank has descreased and I have fewer back links as reported by google. The links to my site and it's content have not decreased, but google's reporting says it has.

    This is simply the effect where the cause is some casino website that does this damn 301 redirect to my website. I had a leeching problem for a while, so I analyed my web server logs to find out the culprit, in doing so I found some odd web log spam for some website in china and a casino website doing a redirect and theft of my site's content.

    I don't make any money off my website, it's a very small niche, but the content is good and it had a nice page rank for a while, so it was an easy target. And there really isn't much I can do. My site got hijacked, google indexed the hijacking page as though it was mine, then they change their page after being indexed in google so that now display advertisements instead of doing the redirect.

    As a hobbyist, I can't get into litigation with a damn casino website in a different country. I know a lot of complaints are from the so-called "search engine optimizing" companies, but as an honest webmaster with no comercial interest in google, it's still a pain in the butt. There is absolutely nothing honest webmasters can do to prevent this or to rectify it. The ball is in Google's court to give credit where credit is due, and that's the final target URL, not the referer.