• http://www.joblr.net Mikkel deMib Svendsen

    The problem is that browsers don’t pass on what comes after the hash-mark – so it’s not, as far as I can see, enough for the analytics providers to update their scripts. If the last part of the URL is not in the refeerer frield there is nothing to collect.

    See also:
    http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/

  • http://smackdown.blogsblogsblogs.com/ mvandemar

    Matt Mikkel is right,

    Nathan Buggia recently wrote about URL fragments (the portion of a URL after a hash mark) on Jane and Robot. In that post, Avinash Kaushik — Google’s Analytics Evangelist — provides a javascript snippet that will allow tracking of URL fragments after the hash mark.

    In Nathan’s article, he is referring to hash marks in the landing page url (ie. ones you can set in ppc campaigns, for instance). The referring url, which is what actually contains the keywords, still does not pass that portion, regardless of what Javascript you use on your own pages.

  • http://www.mmmeeja.com/blog/ andymurd

    Mikkel is right about it screwing with analytics packages but I think rankcheckers will be OK.

    Google get a ton of traffic from their OpenSearch plugin (the search box at the top right of your browser) and rankcheckers should be able to easily mimic that. I can also imagine a lot of people blocking javascript from their search page so my guess is that there will always be a CGI interface to Google search.

  • http://coderrr.wordpress.com coderrr

    http://news.ycombinator.com/item?id=465803

    Here’s a crazy hack they could do to use ajax queries while preserving the current referer url:

    Whenever the ajax search is performed an invisible iframe is loaded at: http://google.com/search?q=search+term&donothing=true.

    The donothing=true tells Google’s webserver to perform no actual query and return a blank page. This should happen extremely quickly. (It could be performed after the ajax results have been fully loaded as to not affect response time)

    Then when a user clicks a search result, Google does a javascript redirect from the iframe (use javascript to add a new tag with a window.top.location= in it) and you get a referer just like you would before… with a negligible performance hit.

  • bmungovan
  • StandardsGirl

    I have not seen this question answered and while I have a post into Jim Thatcher, I thought I would ask here.

    So how would this effect accessibility tools? http://www.webaim.org/techniques/ajax/ Would the most used web search in the world suddenly become mostly inaccessible? How is Google intending to address this issue? Have you asked? Thanks!

  • StandardsGirl

    BTW I know they have the accessibility index. Would this be what people with accessibility issues would use in place of the current index? Or can you make AJAX completely accessible?