Tag Info

New answers tagged


Even though "hashbangs" (#!) are still supported, Google suggests steering away from using them and just use the History API to change the URL. Libraries like History.js make it easy to do so. This basically removes your problem altogether, there's no need to set up urls with _escaped_fragment_ when using the History API


According do Google's Guide: http://stereofox.com/post.php#!idPost=5326 would get crawled at http://stereofox.com/post.php?_escaped_fragment_=idPost=5326. Your server would have to respond to that URL the same way that it used to respond to http://stereofox.com/post.php?idPost=5326. You should then also 301 redirect ...


In it's very basic form search engines don't crawl content provided by ajax. Google at least gives a lookout on this matter: In the near term, your site will remain indexed by Google as-is, with many pages likely not fully represented in search results. However, we are continously working to make Googlebot behave more like a browser. As we implement more ...


Why not have a normal "fallback"? E.g. <a onClick="ajaxPage(2); return false;" href="app/page/2">Page 2</a> | <a onClick="ajaxPage(3); return false;" href="app/page/3">Page 3</a> You can make this hidden (I wouldn't)...


I think this is what you're looking for: Google's AJAX Crawling: Guide for Webmasters and Developers Here's the full specification I think a jQuery plugin called BBQ is worth being familiar with too (it sounds similar to history.js) That said, AJAX and JS in general can be problematic for accessibility and who's to say how other search engines might ...


Bing, which powers Yahoo, does support Google's standard. There is no indication that Duck Duck Go does.

Top 50 recent answers are included