Monday, October 27, 2014<\/p>\n
\n We recently announced that our indexing system has been \n For optimal rendering and indexing, our new guideline specifies that you should allow Googlebot \n Historically, Google indexing systems resembled old text-only browsers, such as Lynx, and that’s \n Pages that render quickly not only help users get to your content easier, but make indexing of \n In conjunction with the launch of our rendering-based indexing, we also updated the \n And, as always, if you have any comments or questions, please ask in our
\n rendering web pages<\/a>
\n more like a typical modern browser, with CSS and JavaScript turned on. Today, we’re updating one
\n of our
\n technical Webmaster Guidelines<\/a>
\n in light of this announcement.\n<\/p>\n
\n access to the JavaScript, CSS, and image files that your pages use. This provides you optimal
\n rendering and indexing for your site. Disallowing crawling of Javascript or CSS files in
\n your site’s robots.txt directly harms how well our algorithms render and index your content and
\n can result in suboptimal rankings.<\/strong>\n<\/p>\nUpdated advice for optimal indexing<\/h2>\n
\n what our Webmaster Guidelines said. Now, with indexing based on page rendering, it’s no longer
\n accurate to see our indexing systems as a text-only browser. Instead, a more accurate
\n approximation is a modern web browser. With that new perspective, keep the following in mind:\n<\/p>\n\n
\n uses. Make sure your web design adheres to the principles of
\n progressive enhancement<\/a>
\n as this helps our systems (and a wider range of browsers) see usable content and basic
\n functionality when certain web design features are not yet supported.\n <\/li>\n
\n those pages more efficient too. We advise you follow the best practices for
\n page performance optimization<\/a>,
\n specifically:\n <\/p>\n\n
\n by concatenating (merging) your separate CSS and JavaScript files, minifying the
\n concatenated files, and configuring your web server to serve them compressed (usually gzip
\n compression)\n <\/li>\n<\/ul>\n<\/li>\n
\n Googlebot.\n <\/li>\n<\/ul>\nTesting and troubleshooting<\/h2>\n
\n Fetch and Render as Google<\/a>
\n feature in Webmaster Tools so webmasters could see how our systems render the page. With it,
\n you’ll be able to identify a number of indexing issues: improper robots.txt restrictions,
\n redirects that Googlebot cannot follow, and more.\n<\/p>\n
\n Webmaster Help forum<\/a>.\n<\/p>\n