Separate Mobile Sites

A separate mobile version of a website will generate an additional URL for the site, typically this is m.domain.com and allows the website to be responsive on a mobile device. However, there are a number of issues which can arise when using a separate mobile site, we cover these within our Hangout Notes, along with insights and recommendations from Google.

Mobile-First Index will Support AMP Pages

May 16, 2017 Source

AMP pages will be used in the mobile-first index if they are set up as separate mobile URLs, or if the AMP page is your canonical page.


Use Redirects to Remove a Separate Mobile Site

February 24, 2017 Source

If you are moving from a separate mobile site to a responsive site, redirect Mobile URLs back to Desktop and remove the rel alternate links from the desktop pages. You can use JavaScript redirects but it will take longer for Google to pick them up.


Primary Content’ Should be the Same on Mobile and Desktop Pages

January 27, 2017 Source

Google expects the visible Primary content to be the same on mobile and desktop pages, including AMP pages, but the navigation can be different.


AMP Sites can Also be the Mobile Version

January 27, 2017 Source

You can reference an AMP site with both mobile rel alternate and rel AMP HTML, however the AMP page will become the primary version when Google moves to mobile-first indexing.


Structured Data and Hreflang Need to be Added to Mobile Pages

January 27, 2017 Source

When Google moves to mobile first, the rel alternate and canonical tags won’t need to be changed, but the mobile pages will require dedicated structured data and hreflang tags.


Links on Mobile Pages Will Be Used For the Link Graph

January 10, 2017 Source

Mobile-first indexing will use the links on your mobile pages for calculating the link graph.


Use Fetch & Render using Smartphone User Agent, Mobile Friendly Testing Tool, and AMP Testing Tool to test for Mobile-first Indexing

December 20, 2016 Source

The Fetch and Render tool set to use a smartphone user agent, the Mobile Friendly Testing Tool, and the AMP Testing Tool can be used to show you the content Google will use for the mobile-first index.


Separate AMP Pages Don’t Need Hreflang

December 9, 2016 Source

If you have separate AMP pages, you don’t need to add hreflang. Implement in on the main desktop pages, the same as a dedicated mobile site.


Separate Mobile Pages May Appear for Site: Queries

November 4, 2016 Source

Sometimes you may see your mobile URLs appear for site: queries, but they might not be indexed. Check the cached version of the pages to see what content has been indexed for those URLs.


Related Topics

Dynamic Serving Mobile Pages Mobile Interstitials Mobile-first Indexing AMP Responsive Design