Welcome to WebmasterWorld Guest from 184.108.40.206
joined:June 3, 2007
joined:Jan 9, 2012
Although they prefer a responsive design, they do support and recommend "Separate URLs for mobile".
We recommend using responsive web design because it has many good aspects:
- Using a single URL for a piece of content makes it easier for your users to interact with, share, and link to your content, and a single URL for the content helps Google's algorithms assign the indexing properties for the content....
In this configuration, each desktop URL has an equivalent different URL serving mobile-optimized content. A common setup would be pages on www.example.com serving desktop users having corresponding m.example.com pages serving mobile users. Google does not favor any particular URL format as long as they are all accessible to both Googlebot and Googlebot-Mobile....
joined:Oct 26, 2011
What they did do, is put links on every page of the site saying essentially, "view mobile site" (on the standard web version) and "view traditional site" on the mobile pages. For whatever reason, they used a tracking link (ie, /?source=mobile) to link back to the main site from the view traditional link.
Do we need a no follow tag or something on the links, in addition to setting up those rel canonical and rel alternate tags on the appropriate places?
This two-way ("bidirectional") annotation helps Googlebot discover your content and helps our algorithms understand the relationship between your desktop and mobile pages and treat them accordingly. When you use different URLs to serve the same content in different formats, the annotation tells Google's algorithms that those two URLs have equivalent content and should be treated as one entity instead of two entities. If they are treated separately, both desktop and mobile URLs are shown in desktop search results, and their positions may be lower than they would otherwise be.
...This article looks at how a typical responsive website is targeted to mobile handsets and tablets, contrasting it with its desktop-facing sister website. It considers how such a website might also be deployed as a cached HTML5 Web app, and why you might want to do that instead. For various reasons, discussed here, you might decide to target your responsive design more narrowly as a hybrid for smartphones and tablets, keeping it separate from the desktop interface....