Monday, December 04, 2017<\/p>\n
\n The \n As a reminder, the AJAX crawling scheme accepts pages with either a \n With this change, Googlebot will render the \n We expect that most AJAX-crawling websites won’t see significant changes with this update. \n If your site is currently using either \n We hope that this change makes it a bit easier for your website, and reduces the need to render
\n AJAX crawling scheme<\/a>
\n was introduced as a way of making JavaScript-based webpages accessible to Googlebot, and we’ve
\n previously announced our
\n plans to turn it down<\/a>.
\n Over time, Google engineers have significantly improved rendering of JavaScript for Googlebot.
\n Given these advances, in the second quarter of 2018, we’ll be switching to rendering these pages
\n on Google’s side, rather than on requiring that sites do this themselves. In short, we’ll no
\n longer be using the AJAX crawling scheme.\n<\/p>\n#!<\/code> in the URL or a
\n fragment meta<\/code> tag<\/a>
\n on them, and then crawls them with an ?_escaped_fragment_=<\/code> in the URL. That escaped
\n version needs to be a fully-rendered and\/or equivalent version of the page, created by the website
\n itself.\n<\/p>\n#!<\/code> URL directly, making it unnecessary
\n for the website owner to provide a rendered version of the page. We’ll continue to support these
\n URLs in our search results.\n<\/p>\n
\n Webmasters can double-check their pages as detailed below, and we’ll be sending notifications to
\n any sites with potential issues.\n<\/p>\n#!<\/code> URLs or the fragment meta<\/code> tag, we
\n recommend:\n<\/p>\n\n
\n Google Search Console<\/a>
\n to gain access to the tools there, and to allow Google to notify you of any issues that might be
\n found.\n <\/li>\n
\n Fetch and Render<\/a>.
\n Compare the results of the #! URL and the escaped URL to see any differences. Do this for any
\n significantly different part of the website. Check our
\n developer documentation<\/a> for
\n more information on supported APIs, and see our
\n debugging guide<\/a> when needed.\n <\/li>\n
\n Inspect Element<\/a>
\n to confirm that links use
\n a<\/code> HTML elements<\/a>
\n and include a
\n rel=nofollow<\/code><\/a>
\n where appropriate (for example, in user-generated content)\n <\/li>\n
\n Inspect Element<\/a>
\n to check the
\n page’s title<\/a> and
\n description meta<\/code> tag<\/a>,
\n any robots<\/span> meta<\/code> tag, and other meta data. Also check that any
\n structured data<\/a>
\n is available on the rendered page.\n <\/li>\n
\n either JavaScript or “normal” HTML, if their content should be indexed in search.\n <\/li>\n<\/ul>\n
\n pages on your end. Should you have any questions or comments, drop by our
\n webmaster help forums<\/a>,
\n or to join our
\n JavaScript sites working group<\/a>.\n<\/p>\n