Freaking Javascript Search Results!

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:

http://www.google.com/#hl=en&q=testing&btnG=Google+Search&aq=f&oq=testing&fp=_rpp-4zAm3I

Click to expand...

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.

darned

Damn, so this is gonna screw up alot of applications that rely on viewing the source code.

Maybe SEOQuake need to change the code to show the actual link instead of google's?

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.

holy this is really bad news

insanity said:

so gay... i wander if this will affect the scraper my jv is running.. im sure it will ..fucking bull shit .. we were planing on using that in many future ways...

fuck it im drunk...lol..

Click to expand...

you are calling us gay ?