\n This post was largely translated from our
\n Japanese version of the Webmaster Central Blog<\/a>
\n <\/i>\n<\/p>\n
\n Recently I introduced several methods to \n One of the most common problems for webmasters who run both mobile and desktop versions of a site \n When a mobile user or crawler (like Googlebot-Mobile) accesses the desktop version of a URL, you \n If you redirect users, please make sure that the content on the corresponding mobile\/desktop URL \n On the other hand, when there’s an access to a mobile-version URL from a desktop browser or by our \n Some sites have the same URL for both desktop and mobile content, but change their format \n However, note that if you fail to configure your site correctly, your site could be considered to
\n ensure your mobile site is properly indexed by Google<\/a>.
\n Today I’d like to share information useful for webmasters who manage both desktop and mobile phone
\n versions of a site.\n<\/p>\n
\n is that the mobile version of the site appears for users on a desktop computer, or that the
\n desktop version of the site appears when someone finds them from a mobile device. In dealing
\n with this scenario, here are two viable options:\n<\/p>\nRedirect mobile users to the correct version<\/h2>\n
\n can redirect them to the corresponding mobile version of the same page. Google notices the
\n relationship between the two versions of the URL and displays the standard version for searches
\n from desktops and the mobile version for mobile searches.\n<\/p>\n
\n matches as closely as possible. For example, if you run a shopping site and there’s an access
\n from a mobile phone to a desktop-version URL, make sure that the user is redirected to the mobile
\n version of the page for the same product, and not to the home page of the mobile version of the
\n site. We occasionally find sites using this kind of redirect in an attempt to boost their search
\n rankings, but this practice only results in a negative user experience, and so should be avoided
\n at all costs.\n<\/p>\n
\n web crawler, Googlebot, it’s not necessary to redirect them to the desktop-version. For instance,
\n Google<\/a>
\n doesn’t automatically redirect desktop users from their mobile site to their desktop site,
\n instead they include a link on the mobile-version page to the desktop version. These links are
\n especially helpful when a mobile site doesn’t provide the full functionality of the desktop
\n version—users can easily navigate to the desktop-version if they prefer.\n<\/p>\nSwitch content based on User-agent<\/h2>\n
\n according to User-agent<\/code>. In other words, both mobile users and desktop users access
\n the same URL (that is, no redirects), but the content\/format changes slightly according to the
\n User-agent<\/code>. In this case, the same URL will appear for both mobile search and desktop
\n search, and desktop users can see a desktop version of the content while mobile users can see a
\n mobile version of the content.\n<\/p>\n
\n be cloaking, which can lead to your site disappearing from our search results.
\n Cloaking<\/a>
\n refers to an attempt to boost search result rankings by serving different content to Googlebot
\n than to regular users. This causes problems such as less relevant results (pages appear in search
\n results even though their content is actually unrelated to what users see\/want), so we take
\n cloaking very seriously.\n<\/p>\n
![\"Diagram](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-dcf9b6b3333c.png\")
<\/p>\n