1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Freaking Javascript Search Results!

Discussion in 'White Hat SEO' started by Sweetfunny, Apr 24, 2009.

  1. Sweetfunny

    Sweetfunny Jr. VIP Jr. VIP

    Joined:
    Jul 13, 2008
    Messages:
    1,758
    Likes Received:
    5,042
    Location:
    ScrapeBox v2.0
    Home Page:
    Google has just pushed out Javascript search results, and no i'm not logged in to a Google account.

    SEOQuake is busted, and many traffic and other scripts which rely on the referrer string from Google will be broken now. The URL's address looks like:

    Note the # after Google.com well that means browsers etc ignore everything after it. For instance that URL above will show PR10 because the browser thinks you are on Google.com

    Also the search results page source code shows no Titles, URL's or Descriptions, just a bit of Javascript.

    I admit the results are fast as heck, but this sucks big time. Took me a bit to work out why SEOQuake was broken, well that's why.
     
  2. cristianraiber

    cristianraiber Regular Member

    Joined:
    Nov 22, 2008
    Messages:
    293
    Likes Received:
    381
    Occupation:
    Onliner
    Location:
    Internet
    darned :(
     
  3. shm03

    shm03 Regular Member

    Joined:
    May 19, 2008
    Messages:
    284
    Likes Received:
    123
    Damn, so this is gonna screw up alot of applications that rely on viewing the source code.
     
  4. neobyte

    neobyte Junior Member

    Joined:
    Sep 15, 2008
    Messages:
    122
    Likes Received:
    16
    Maybe SEOQuake need to change the code to show the actual link instead of google's?
     
  5. Sweetfunny

    Sweetfunny Jr. VIP Jr. VIP

    Joined:
    Jul 13, 2008
    Messages:
    1,758
    Likes Received:
    5,042
    Location:
    ScrapeBox v2.0
    Home Page:
    I'm not sure how SEOQuake will work around this when it's fully rolled out, all the URL's in the results are in an external .js with a random filename instead of in the HTML.

    Is anyone else getting the same as me?

    I have found a workaround for now, go to command prompt and ping Google and get the IP then use that. I'm using http://74.125.45.100/ you can use that, but it's better to ping Google yourself so you get the geo datacenter you normally search through when using the domain version.

    Not sure what this will do to scrapers, i just ran one and it did still work because they are falling back to default for non JS browsers/tools.. But this change isn't fully done yet.
     
  6. evilgary

    evilgary Junior Member

    Joined:
    Apr 3, 2008
    Messages:
    187
    Likes Received:
    26
    holy this is really bad news
     
  7. kingtrojan

    kingtrojan Junior Member

    Joined:
    Feb 28, 2008
    Messages:
    175
    Likes Received:
    167
    Occupation:
    Software Engineer
    Location:
    127.0.0.1
    you are calling us gay ?