m. vs. The Right Way
Posted by Rich on Tuesday February 26th 2008, 9:10 am
Filed under: Development, Mobile

Hey LinkedIn, your mobile site is really quite good. It’s going to be a big help adding new people while at conferences, etc. and not having to wait till I can sit down with a laptop.

But if you’re going to use m.linkedin.com instead of detecting user-agents on www.linkedin.com, you might as well have used a .mobi address. (Read: this is the wrong thing to do)

Here’s what you do:

- Redirect based on user-agent from linkedin.com.

- Put a link on the bottom of your mobile pages to get to the full version of the site.

- Feel good that you’re not losing users who don’t know to put an m. before mobile URLs

- Profit!

Come on, if Facebook can do it, so can you.

Bookmark and Share

6 Comments so far
Leave a comment

Hey Rich, speaking of, I typed clearspring.com all by itself into my browser the other day and got an error. Looks like the default IP there doesn’t map to the same thing as http://www.clearspring.com. Not that I assume you have all that many typeins, but still, I know you had at least one who was confused.

Comment by Mike Rowehl 02.26.08 @ 1:49 pm

Thanks Mike! We just upgraded the main site and it looks like our A records were overwritten, but it wasn’t visible till recently when we shut down older servers.

Sometime today they should all be redirecting correctly.

Comment by Rich 02.26.08 @ 2:10 pm

dotMobi talked about this on our blog today. You may not agree but I think it’s worth considering all viewpoints. See http://dotmobi.typepad.com/dotmobi/2008/02/do-you-have-the.html.

Comment by Vance Hedderel, Director of PR & Communications 02.26.08 @ 4:31 pm

Vance. I understand where your post is coming from, but I don’t agree. Mobile formatting is not akin to geo localization. Not at all.

Even looking at the trivial evolution of this, if we segment mobile formatted content from web content, how then do we further segment the mobile content into localized information? Do you want a .mobi.uk? That’s getting a bit much, don’t you think?

In fact, I’d argue in the opposite direction. I think instead of forcing the user to identify their locale on the web, companies should do an IP geo lookup and forward to the correct localized site. Sure everyone can’t afford an enterprise-class IP lookup service, but BMW certainly can.

Your point about indexing mobile content better through the .mobi domain may have some merit, but not for long. Search engines are getting smarter, and there are many metadata cues that can be used to index properly.

Moving forward, URLs will take a back seat to search and default browser behavior. If I have a brand name, I want a .com domain because that’s the first thing a browser tries if a user only types a single word, and empirically, I see that search engines put .com domains that exactly match single word searches first.

If you get all the phones in the world to default to .mobi first, and all the search engines to place .mobi domains at the top of the list when searching from mobile, then I might buy in.

But as it stands now, if I have a brand name, I want a .com after it, and I want to have as much smarts at the front door as possible to get people to the right content based on their location and their device. Right now that’s the absolute best way to get the most users to the content they want.

Comment by Rich 02.26.08 @ 10:45 pm

[...] from .Mobi was nice enough to send a counter point to my last post. The .mobi versus autodetection debate has gone on for a while, and I’ve stayed out of it, [...]

Pingback by A Little .mobi Discussion | Mobilitee 02.26.08 @ 11:06 pm

[...] expressed my opinions on a separate .mobi domain before, and I’m glad I can finally end the [...]

Pingback by .mobi Sold Off | Mobilitee 02.12.10 @ 12:14 pm



Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

(required)

(required)