Wednesday, October 14, 2015<\/p>\n
\n In short: We are no longer recommending the AJAX crawling<\/a> \n In 2009, we made a \n Times have changed. Today, as long as you’re not blocking Googlebot from crawling your JavaScript \n Since the assumptions for our 2009 proposal are no longer valid, we recommend following the \n Q: My site currently follows your recommendation and supports \n Q: Is moving away from the AJAX crawling proposal to industry best practices considered a site \n Q: I use a JavaScript framework and my webserver serves a pre-rendered page. Is that still \n If you have any questions, you can post them here, or
\n proposal we made
\n back in 2009<\/a>.\n<\/p>\n
\n proposal to make AJAX pages crawlable<\/a>.
\n Back then, our systems were not able to render and understand pages that use JavaScript to present
\n content to users. Because
\n “crawlers are not able to see any content created dynamically<\/a>“,
\n we proposed a set of practices that webmasters can follow in order to ensure that their AJAX-based
\n applications are indexed by search engines.\n<\/p>\n
\n or CSS files, we are generally able to
\n render and understand your web pages like modern browsers<\/a>.
\n To reflect this improvement, we recently
\n updated our technical Webmaster Guidelines<\/a>
\n to recommend against disallowing Googlebot from crawling your site’s CSS or JS files.\n<\/p>\n
\n principles of
\n progressive enhancement<\/a>.
\n For example, you can use the
\n History API pushState()<\/code><\/a>
\n to ensure accessibility for a wider range of browsers (and our systems).\n<\/p>\nQuestions and answers<\/h2>\n
_escaped_fragment_<\/code>.
\n Would my site stop getting indexed now that you’ve deprecated your recommendation?<\/b>
\n A: No, the site would still be indexed. In general, however, we recommend you implement industry
\n best practices when you’re making the next update for your site. Instead of the
\n _escaped_fragment_<\/code> URLs, we’ll generally crawl, render, and index the
\n #!<\/code> URLs.\n<\/p>\n
\n move? Do I need to implement redirects?<\/b>
\n A: If your current setup is working fine, you should not have to immediately change anything. If
\n you’re building a new site or restructuring an already existing site, simply avoid introducing
\n _escaped_fragment_<\/code> urls.\n<\/p>\n
\n ok?<\/b>
\n A: In general, websites shouldn’t pre-render pages only for Google—we expect that you might
\n pre-render pages for performance benefits for users and that you would follow progressive
\n enhancement guidelines. If you pre-render pages, make sure that the content served to Googlebot
\n matches the user’s experience, both how it looks and how it interacts. Serving Googlebot different
\n content than a normal user would see is considered cloaking, and would be against our Webmaster
\n Guidelines.\n<\/p>\n
\n in the webmaster help forum<\/a>.\n<\/p>\n