Mobile SEO: Responsive Design vs. Separate Mobile Site vs. Dynamic Serving
UPDATE – May 11,2016: I originally wrote this post prior to Google’s “Mobilegeddon” update in April of 2015, and I’ve been happy to see so many people finding it useful when deciding between responsive vs. separate mobile site designs, as well as dynamic serving. From my standpoint, everything you’ll read here is still valid, so read with confidence! -JR
The SEO industry is abuzz with talk of Google’s impending mobile-friendly algorithm update on 4/21/15. If you receive significant search traffic from mobile devices and don’t have a mobile-friendly website, there’s a good chance you could be impacted by this change in a couple weeks.
Hopefully you’re in good shape and have already verified that your site is mobile-friendly. If you’re starting from scratch, however, and are scrambling to get a solution in place, one of the first decisions you’ll need to make is how to approach the implementation at a high-level: responsive design, separate mobile site, or dynamic serving. Here’s a quick run-down of each to make sure you head down the right path from the beginning.
Responsive design delivers the same code to the browser on a single URL for each page, regardless of device, and adjusts the display in a fluid manner to fit varying display sizes. And because you’re delivering the same page to all devices, responsive design is easy to maintain and less complicated in terms of configuration for search engines.
The image below shows a typical scenario for responsive design. As you can see, there’s no device detection that occurs when the page is served; whether it’s a desktop or mobile device, each user agent (or device type) enters on a single URL and gets the same HTML content.
With all the discussion surrounding Google’s mobile-friendly algorithm update, I’ve noticed a lot of people suggesting that mobile-friendliness is synonymous responsive design – if you’re not using responsive design, you’re not mobile-friendly. That’s simply not true. There are some cases were you wouldn’t want to deliver the same payload to a mobile device as you do to a desktop computer, and attempting to do so would actually provide a poor user experience.
Google recommends responsive design in their mobile documentation because it’s easier to maintain and tends to have fewer implementation issues. However, I’ve seen no evidence that there’s an inherent ranking advantage to using responsive design.
Pros and cons of Responsive Design:
Separate Mobile Site
You can also host a mobile version of your site on separate URLs, such as a mobile sub-domain (m.example.com), an entirely separate mobile domain (example.mobi), or even in a sub-folder (example.com/mobile). Any of those are fine as long as you properly implement bi-directional annotation between the desktop and mobile versions.
It’s a good idea to incorporate elements of responsiveness into your design even when you’re using a separate mobile site because it allows your pages to adapt to small differences in screen sizes.
A common myth about separate mobile URLs is that they cause duplicate content issues since the desktop version and mobile versions feature the same content. Again, not true. If you have the proper bi-directional annotation, you will not be penalized for duplicate content, and all ranking signals will be consolidated between equivalent desktop and mobile URLs.
Pros and cons of a Separate Mobile Site:
Dynamic Serving allows you to serve different HTML and CSS, depending on user agent, on a single URL. In that sense it provides the best of both worlds in terms of eliminating potential search engine indexation issues while providing a highly tailored user experience for both desktop and mobile.
The image below shows a typical scenario for separate mobile site.
Google recommends that you provide them with a hint that you’re altering the content based on user agent since it’s not immediately apparent that you’re doing so. That’s accomplished by sending the Vary HTTP header to let them know that Googlebot for smartphones should pay a visit to crawl the mobile-optimized version of the URL.
Pros and cons of Dynamic Serving:
Which Method is Right for You?
The best mobile configuration is the one that best fits your situation and provides the best user experience. I’d be leery of a design firm who comes out of the gate recommending an implementation approach without fully understanding your requirements. Don’t get me wrong: responsive design is probably a good choice for most websites, but it’s not the only path to mobile-friendliness.
Whatever your approach, the message is loud and clear: your website needs to be mobile friendly. Given that the mobile-friendly algorithm update is expected to have a significant impact, I predict that 2015 will be a busy year for web design firms.
27 Responses to “Mobile SEO: Responsive Design vs. Separate Mobile Site vs. Dynamic Serving”
Leave a Reply