Webmasters

Guildelines for tablets

When thinking about how to configure your website for mobile users, it's common to think about visitors using tablet devices to access your site. Although we do not have specific recommendations for building search engine friendly tablet-optimized websites, there are some tips for building websites that serve desktop, smartphone and tablet users.

Responsive web design

As for smartphone-optimized sites, our recommendation is to use responsive web design. This means that your website serves the same HTML code to all devices along with different CSS style rules to optimize the site's interface on desktops, smartphones, and tablets.

If your website uses responsive web design, test it on a variety of tablets to make sure it renders correctly as, just like for smartphones, there are a variety of tablet sizes and screen resolutions.

Device-specific content

A website can return different pages (different HTML, CSS, JavaScript, etc) for different devices. These pages can be served on the same URL (a configuration called dynamic serving) or on separate dedicated URLs. Learn more about correctly detecting devices and user-agents.

If your website has different pages to serve desktop and smartphone users and does not have tablet-specific pages, in our experience tablet users usually expect to see your desktop site rather than the site's smartphone pages.

If your website has tablet-optimized sites, these guidelines can help you configure your site:

  • Dynamic serving: Here the same URLs serves desktop, smartphone, and tablet users by serving different HTML (and CSS) depending on the user-agent. As described in our smartphone website recommendations, we strongly suggest using the Vary HTTP header.
  • Separate tablet-dedicated URLs: In this case, we strongly suggest you allow Googlebot to crawl the tablet URLs and use a rel="canonical" on each tablet URL to point to the equivalent desktop URL.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.