Wednesday, June 06, 2012<\/p>\n
\n Every day more and more smartphones get activated and more websites are producing \n Today we’d like to give you Google’s recommendations for building smartphone-optimized websites \n The full details of our recommendation can be found in our \n When building a website that targets smartphones, Google supports three different configurations:\n<\/p>\n \n Responsive web design is a technique to build web pages that alter how they look using CSS3 media Using responsive web design has multiple advantages, including:<\/p>\n \n However, we appreciate that for many situations it may not be possible or appropriate to use \n If your website uses a dynamic serving configuration, we strongly recommend using the \n As for the separate mobile site configuration, since there are many ways to do this, our \n These annotations will help us discover your smartphone-optimized content and help our algorithms \n This blog post is only a brief summary of our recommendation for
\n smartphone-optimized content. Since we
\n last<\/a> talked about how to build
\n mobile-friendly websites, we’ve been working hard on improving Google’s support for
\n smartphone-optimized content. As part of this effort, we launched
\n Googlebot-Mobile for smartphones<\/a>
\n back in December 2011, which is specifically tasked with identifying such content.\n<\/p>\n
\n and explain how to do so in a way that gives both your desktop- and smartphone-optimized sites the
\n best chance of performing well in Google’s search results.\n<\/p>\nRecommendations for smartphone-optimized sites<\/h2>\n
\n new help site<\/a>, which we now summarize.\n<\/p>\n\n
\n URLs, with each URL serving the same HTML to all devices and using just CSS to change how the
\n page is rendered on the device. This is Google’s recommended configuration<\/strong>.\n <\/li>\n
\n HTML (and CSS) depending on whether the user agent is a desktop or a mobile device.\n <\/li>\nResponsive web design<\/h2>\n
\n queries. That is, there is one HTML code for the page regardless of the device accessing it, but
\n its presentation changes using CSS media queries to specify which CSS rules apply for the browser
\n displaying the page. You can learn more about responsive web design from
\n this blog post<\/a>
\n by Google’s webmasters and
\n in our recommendations<\/a>.\n<\/p>\n\n
\n interact with, share, and link to and for Google’s algorithms to assign the indexing properties
\n to your content.\n <\/li>\n
\n different Googlebot user agents to retrieve and index all the content.\n <\/li>\n<\/ul>\nDevice-specific HTML<\/h2>\n
\n responsive web design. That’s why we support having websites serve equivalent content using
\n different, device-specific, HTML. The device-specific HTML can be served on the same URL (a
\n configuration called dynamic serving) or different URLs (such as www.example.com and
\n m.example.com).\n<\/p>\n
\n Vary<\/code> HTTP header to communicate to caching servers and our algorithms that the
\n content may change for different user agents requesting the page. We also use this as a crawling
\n signal for Googlebot-Mobile<\/a>.\n<\/p>\n
\n recommendation introduces annotations that communicate to our algorithms that your desktop and
\n mobile pages are equivalent in purpose; that is, the new annotations describe the relationship
\n between the desktop and mobile content as alternatives of each other and should be treated as a
\n single entity with each alternative targeting a specific class of device.\n<\/p>\n
\n understand the structure of your content, giving it the best chance of performing well in our
\n search results.\n<\/p>\nConclusion<\/h2>\n
\n building smartphone-optimized websites<\/a>. Please read
\n the full recommendation and see which supported implementation is most suitable for your site and
\n users. And, as always, please ask on our
\n Webmaster Help forums<\/a>
\n if you have more questions.\n<\/p>\n