How To Best Optimize Your Mobile Site For SEO
Last week my colleague, Michael Martin presented Mongoose Metrics data that demonstrates that less than 10% of you are mobile ready in 2012. He also presented some pretty compelling reasons for going mobile in 2012, including the Compuware study that 57% of customers would not recommend a business with a bad mobile site, and 40% […]
Last week my colleague, Michael Martin presented Mongoose Metrics data that demonstrates that less than 10% of you are mobile ready in 2012. He also presented some pretty compelling reasons for going mobile in 2012, including the Compuware study that 57% of customers would not recommend a business with a bad mobile site, and 40% would actually even go to a competitor with a better mobile experience.
If you’re a regular reader of this column and you don’t have a mobile experience, you are in the majority of site owners; but you’re also way behind and may not be able to catch up if you wait much longer.
So are you ready? Let’s talk about the ideal set up for your mobile site for SEO purposes.
There are cheaper, easier solutions, but this is the one that I would recommend to webmasters looking not just for a mobile friendly solution, but something that’s truly optimized to bring in traffic from mobile searchers.
If you want to build a mobile site in a way that will increase your organic search engine traffic, this is how to do it.
1. Make It Truly Mobile
Before you even think about subdomain options, you better know your mobile user: the person who you’re building this for who will ultimately make it a success or failure.
What are they looking for and why? Use the AdWords keyword tool to get mobile volumes and desktop volumes for keywords related to your brand, and to your products and services, and then find the mobile percent of total volume, or the mobile ratio, as Sherwood Stranieri put it. This gives you a sense of what concepts and keywords overindex with smartphone and mobile searchers, and it will help you build more than a desktop experience.
For example, for Walgreens, it’s clear from their brand keywords that index high among mobile searchers that the majority of searchers are looking for a Walgreens near them. It’s clear from the volume of queries where more than 30% of the total volume is mobile (smartphone and feature phone):
And it’s clear from a long tail analysis of the same list:
These are highly qualified searchers, as they’re very likely to convert offline, so why not make it as easy for them as possible?
Now that we know what our mobile users want, we can design the mobile site so that it provides those things with ease. And this will differ for all businesses, but it’s likely to be different from how your desktop website is structured.
Walgreens seems to know this, as they designed their mobile website differently than their desktop website, specifically taking advantage of the unique capabilities of a mobile device.
Instead of having their mobile searcher find a site with a lot of irrelevant content crammed on to one page that’s intended for desktop users, they’ve highlighted those areas that are most relevant to the mobile user experience.
For example, instead of doing nothing with their site and hoping that a mobile searcher finds the sections they’re looking for (which I’ve highlighted in red in the second image):
Walgreens has presented a simplified version of the home page that highlights those areas of the site that are most relevant to the mobile user experience:
When you hit the “find near me” button, it uses the phone’s GPS to find the locations closest to you, taking advantage of the specific functionality of mobile browsers rather than completely transcoding the desktop site with desktop functionality to look good on mobile browsers (i.e. responsive design).
Walgreens.com isn’t the paragon of mobile SEO, unfortunately, as they’ve done a lot of things wrong when it comes to the findability of their mobile site. With the design they really should have included a small keyword-rich text box that conveys the relevance of the page to users and search engines, as there’s not a lot of text or keywords on the page to help search engines understand that it’s relevant for what search engine users are looking for.
For some brands, there may also be concepts and keywords that aren’t included in the desktop site that need to be linked to from the homepage.
I’m guessing this is because the page was designed with users rather than SEO in mind, as someone hired the non-search-friendly mobile platform Usablenet to design the site and disallowed it in the robots.txt file so that it only appears in search engines when you put in the navigational keyword [m walgreens com].
They also promote the app over the mobile site by sending the searcher to a splash page first, which isn’t good for users or search engines.
Nonetheless, like State Farm and too few other companies, they did build a separate mobile user experience rather than used stylesheets to serve a formatted desktop experience, which is the first big step to getting a search-optimized mobile site.
2. Create A Hybrid Of Mobile-Optimized & Mobile-Friendly Content
Once you’ve settled on the design and site architecture, you need to determine the best way to host your mobile site. Though there are many opinions on the matter, the best solution is to host your mobile homepage and mobile-only pages at m.domain.com subdomain or /m subfolder.
For all other pages with content that won’t change from desktop to mobile, it’s perfectly acceptable to keep them at the same URL as your desktop and simply reformat them for mobile user agents. Redirects work fine too, but the best practice for transcoded desktop URLs is currently to add canonical tags to pass the link equity back to desktop pages.
For mobile only pages that are not strict duplicates, canonical tags are unnecessary, and could make your most valuable pages invisible to searchers.
3. Redirect Appropriately
For mobile-only content, you’ll need to set up the proper redirects. My colleague Cindy Krum has a handy tool for PHP and .NET redirects that makes it easy for novices to set up mobile redirects.
When Googlebot comes by, serve it your desktop content; but when her sisters Googlebot mobile and smartphone Googlebot arrive, give them your feature phone site (if you have one) and your smartphone site, respectively.
If you have a tablet site, by all means serve it to tablet searchers instead of your desktop or smartphone site, but there currently is no tablet Googlebot to receive your tablet site.
If you don’t have a tablet site, serve your tablet searchers desktop content, as research shows that’s what they respond to best. Just make sure you’ve removed all traces of Flash before serving it up to the iPad or other tablets that don’t support Flash.
4. Don’t Forget the Images!
It has been a long time since mobile SEO was about optimizing WAP sites, and in the near future we may be optimizing for a literal pair of Google Goggles, with a Terminator-like overlay that searches for more information on the things around us, just by analyzing images and comparing them to Google’s image and Google Goggles image database.
SEOs can prepare for this brave new world today by ensuring images are optimized for mobile searchers.
5. Analyze & Optimize
Sure, there are mobile SEO best practices beyond this, but best practices only go so far. If you want to retain the edge that optimizing your site in this way gives you, you can’t just set it and forget it.
Given how rapidly this practice is changing, and how much it has changed in the last five or six years, mobile SEO requires regularly looking to your web analytics and to columns like those in the Mobile Search section in Search Engine Land in order to stay optimized.
There are many ways to go mobile, and many of them will actually hurt your visibility among mobile searchers. If you create mobile content when appropriate, redirect appropriately, optimize your images for mobile searchers, and analyze your site for new opportunities, there won’t be many mobile webmasters who will be able to compete with you in natural search.
Opinions expressed in this article are those of the guest author and not necessarily Search Engine Land. Staff authors are listed here.