Well, a recurring problem with Google is that when someone wants to display the exact google results for something; they can often change later. Maybe the parameter is a cache key so that another user when linked can retrieve the same results? |
I suppose the "fp" parameter is just a random string, to force the browser to load that URL. If the user tries searching twice for the same thing, the URL wouldn't change if the fp param wasn't there, and the browser wouldn't bother loading it because it's just a (non-)change to the anchor part of the URL (the part after the #). |
Entering a URL in that format redirects to the old style search result URL for me.
![[put at-character here]](image/at.gif) WindPower I don't think changes in the anchor part of the URL will make the browser load the page anew. Actually, I think that they specifically won't |
Based in Norway, I don't see a similar url when searching for foo over at Google. For me the results from both urls give exactly the same result. Often websites include the hashtag to make the back/forward buttons use if they were to start using an ajaxy search.. |
Most importantly those URL don't work for people and devices without JavaScript at all (!).
Google results were always fully generated on the server side and accessible to all different devices. The change means that some of the work is now carried on the client side using AJAX (JavaScript) and some browser and devices are just left out. Try disabling JavaScript in your browser and going to a "new style" URL. Instead of the results you will see Google's homepage. |
i think this is only for sites with personalised Google search (because it is javascript based anyway). |
These are AJAX SERPs.
A logical step in making the SERPs "live" (a la FriendFeed and Twitter) and ensuring Google, and not any other site, is the first place people turn to for data... :D
|
I'm pretty sure the "fp" stands for "Friendship Power." |
