Let me preface this by saying that I’m not a dotMobi hater and actually disagree with my esteemed colleague Cindy Krum and others who are calling for (or declaring) the “death of the .mobi” at this year’s SES San Jose. On the contrary, there’s evidence to suggest that dotMobi is growing faster than most TLDs and the organization itself deserves credit for foregrounding a positive mobile user experience when so many consumers cite a poor user experience as a reason for avoiding the mobile Web. By contributing resources for mobile developers and mobile marketers and actively promoting mobility, as an organization they have done more than most to speed adoption of the mobile Web, and in turn the marketing to users of the mobile Web that we’ve all been hoping for. There are actually many reasons to acquire a dotMobi domain for your site (direct navigation and usability among them), but none of them, currently, involve SEO.
From an SEO standpoint, if you already own a dotcom domain, hosting your mobile site at the dotMobi might even hurt you, as doing so doesn’t’ take advantage of site factors like age of domain and link popularity that could help your site become more visible in search engines. As it is, there’s currently no evidence that dotMobi is a mobile search quality signal for the most popular mobile search engines or that dotMobi sites do better in search results. There is some evidence, however, that like any new domain in search results without the benefit of age and link popularity, they do worse.
For that reason I typically recommend both buying a dotMobi for your brand, and permanently redirecting it to the dotcom version of your site, hosted at m.domain.com or some easy to type alternative (e.g. domain.com/m).
Whether you choose to redirect the dotMobi to the dotcom or the dotcom to the dotMobi, redirect one of them for better visibility in search engines. Though it might be tempting, do not host a dotMobi site and a dotcom site with the same content. In SEO and mobile SEO this is duplicate content, and it won’t help your SEO efforts.
To illustrate, I’m going to use the new m-commerce site from Ralph Lauren at m.ralphlauren.com and polo.mobi. Ralph Lauren has been getting a lot of well-deserved press for their pioneering mobile commerce site and to salute their commitment to mobility I’m going to give them a link and a bit of free advice: redirect the dotMobi. There’s a lot wrong with this site in terms of SEO, but this is one of the biggest and most common.
Keep in mind, duplicate content in mobile search isn’t always bad currently. As we point out in the Resolution Media mobile SEO white paper, creating different mobile versions of your mobile content can actually help make it more visible. Look at the Google mobile search results for movie tickets for confirmation.
Google mobile search for “movie tickets”
MovieTickets.com has four of the six listings on the page, precisely because they created multiple mobile sites and hosted them at the .com domain. Had they blocked those with REP, as some consultants inexplicably suggested at SMX Local & Mobile, they would have had one of six listings on the SERP.
The difference between this and the Ralph Lauren site, however, is that the duplicate content for MovieTickets.com is all hosted at the dotcom TLD, while Ralph Lauren has duplicate content on different TLDs. As a result, Google mobile has all but made the dotMobi invisible even for RL brand terms, and you literally have to put in the keyword polo.mobi to find it in the mobile engine.
My advice to those looking to optimize their mobile site: don’t let Google decide which site is canonical and which should be suppressed. Whether you decide on dotMobi or dotcom as the TLD for your mobile site, pick one and permanently redirect the other. My recommendation is to permanently redirect the dotMobi to the dotcom, as it’s currently best for mobile SEO in the most popular mobile search engines; but the dotMobi is far from dead and should certainly be acquired. Just don’t host two sites at separate TLDs, or one of them will be suppressed. Better to consolidate your link popularity while giving mobile users a positive user experience, regardless of how they choose to access your site.
Hey Bryson! I completely on that. Use the strength of your existing domain and host mobile content on a subdomain or in a subfolder as mentioned in the example above. That way you’ll benefit from all trust, links and whatever your existing domain already has. With a new domain you’ll have to rebuild everything from scratch.
Hi Bryson, I’m reading your this blog entry and a question is raised then:
If you do a direct redirection from a .mobi to a .com, is it better then to redirect to the subdomain of the mobile part (say http://m.ralphlauren.com) or to the www; then have a browser recognition that would then redirect to the mobile version?
Thanks in advance
I agree that an indexed .com is valuable internet real estate, but I disagree that anything to the left of the dot (subdomain) is going to have similar success. Here’s why: the site is already indexed at the root level. The search engines are far less likely to “discover” the mobile site on the subdomain. At this time, there are so few developed websites that appear in the zone file for .mobi as compared to .com, your chance of discovery on the search engines is much higher. This next part is pure speculation, but as mobile algorithms become more sophisticated, I believe that the major search engines will have an easier time finding mobile content on a TLD designed for mobile (.mobi).
My own personal experience in developing new sites is that my newly developed .com sites sit unvisited by spiders for weeks, while my .mobi sites are crawled before they are finished.
I’ve noticed this article was written in August of 2008, and I am commenting in February of 2009. Has your opinion about this changed at all? Thanks!
All the Best,
Hi Holly! Nowadays with sitemaps and webmaster tools allowing a webmaster to communicate directly with search engines, I don’t think the Internet zone files are as important as dotmobi often asserts. I’ve had new dotcoms indexed within hours, making the sandbox effect seem a thing of the past. Similarly, common mobile subdomains are able to be verified within webmaster consoles and indexed as quickly. dotMobi domains are no different in this respect. And if a webmaster doesn’t already own a dotcom, they might have an easier time finding a dotmobi with keywords in the domain. On top of that, dotMobi is exceptional in their commitment to the mobile user experience, and so eventually they may be able to trump the daunting link popularity card that often has dotcoms dwarfing them in mobile search results. But the key word here is eventually. For now, however, it’s difficult for me to recommend hosting a site at a dotMobi if the webmaster already owns a dotcom, as the domain factors are just too strong at this point. However, if no dotcom is owned, there are plenty of things mobile webmasters can do to make their sites competitive in search results. My point here is, regardless of which one you choose, redirect the other, as you don’t want the search engines deciding which domain is canonical, and which will be unable to rank. At any rate, thanks for your comments! Hopefully this clarifies my position, which is fairly domain agnostic, but realistic. Best, Bryson
I suggest anyone can check the mobilized features of web by the tool mobiready provided by dot mobi at http://ready.mobi