Sub-domain or sub-directory for mobile version
-
sub-domain or sub-directory for mobile version
advantages or dis-advangages?
-
Ok, in my opinion mobile website are not the actual part of the main website (mobile website do not have same status as blog) so it is intelligent to go with sub domain but always keep the visitor’s sensor on so if they are coming from smart phone or ipad it should open a mobile website for them but if they are coming from desktop or laptop in that case it should be the main website for web.
-
domain.mobi (Subdirectory)
Pros
- Carrier transcoding. Sprint PCS in the US and Vodaphone in the UK transcode (modify websites) that you load on your phone for the best experiences (although, it breaks some websites). These carriers assume .mobi is mobile-friendly and do not modify their content.
- .mobi means mobile-friendly and is best for search: Some search engines can be set to only search .mobi domains with the assumption that they're all mobile-friendly. Although, this area is very new and search engines can determine a mobile-friendly site via other methods, this is one area of speculation.
- Brandable. Some might say that .mobi is more brand-able than m.domain.com. For instance, it's easier to tell people to go to http://domain.mobi and build a campaign around it than http://m.domain.com.
- Separate control. This might be important for an agency who is building a mobile website for a client. If they wanted to purchase and host the domain names themselves, they can. This can speed up the process for getting a domain established for the mobile site.
Cons
- Opportunity for domain squatters. Several companies own their domain.com, but they don't always own the .net/.org variations. This could either be due to never having thought about it, lack of interest, or the .net/.org being owned by a domain squatter. The domain squatter also has the opportunity to purchase domain.mobi
- More effort to type. .mobi takes longer to type than .com thanks to the .com button on most smartphones. At the end of the day, a .mobi domain isn't needed much.
- New domain, no SEO juice. A .mobi domain would be treated as a new domain name and it wouldn't take any SEO from whatever current domain you have.
- Costs involved and inconvenience. The cost of a .mobi domain and added inconvenience for managing it may not make it worthwhile.
m.domain.com(Subdomain)
Pros
- Easier to access and maintain. The DNS is all stored under the same domain. No additional domain to purchase, set up, and manage.
- Easier to type on a phone. iPhone and Android on-screen keyboards include a .com button on the virtual keyboard.
- Keeps your brand in-tact. People already know domain.com is yours. Something like domain.mobimight confuse them.
- Free. Setting up a subdomain should be a simple process depending on the web host.
- Higher adoption in the US. Companies such as Yahoo, Twitter, Google, YouTube, and Facebook have adopted this method.
- Support for multinational domains. Some companies such as Amazon have Amazon.com for their US presence and Amazon.co.uk for their UK presence. A .mobi site just comes in .mobi. I suppose you could have co.uk.amazon.mobi, but that sounds messy (and backwards). m.amazon.co.uk makes more sense.
- It's what Matt Cutts said. Matt, who works at Google and shares webmaster tips for best practices, suggested that m.domain.com will do the trick.
- _Cookie support. _This may be one of the greatest benefits of the m.domain.com method. Cookies, or temporary files on your computer used to store information, can be set for a domain and a certain subdomain. With domain.mobi, however, cookies cannot work across multiple domains. So, if you logged into a mobile website but needed to view the desktop website and wanted to switch to that mode, using m.domain.com would be best so you can stay logged in between both sites.
Cons
- Too ambiguous. Some would argue "m.domain.com" makes no sense and isn't intuitive for people looking for the mobile site.
- No carrier transcoding. Few phone carriers are transcoding websites so when someone access a site on their phone the website gets reduced in size so it loads faster. This could break some desktop websites and mobile sites. Only Sprint PCS in the US and Vodaphone in the UK are doing this that we've heard of. The work around is to manually register your mobile website as a mobile website with each carrier.
One question I often hear is which makes more sense for someone to type in, m.domain.com, or domain.mobi? My answer: if you want the mobile version, go to the desktop site and it should take you to the mobile version.
If in doubt, use m.domain.com and redirect the domain.mobi to m.domain.com.
This was the more common method of delivering a mobile optimized website before responsive design came along. You have a mobile site on a different sub-domain, such as m.bbc.co.uk, keeping all of your mobile content on different URLs.
The two most important points if you’re using this method are:
Use the rel=”alternate” tag pointing to the mobile URL on the desktop version of the page, helping Google find your mobile content.
Use the rel=”canonical” tag pointing to the desktop URL on the mobile version of the page, helping Google understand which version of the content is duplicated.
**At the last my suggestion is go with subdomain for mobile website. **
Let me know if you need more help.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Canonicals from sub-domain to main domain: How much content relevancy matters? Any back-links impact?
Hi Moz community, I have this different scenario of using canonicals to solve the duplicate content issue in our site. Our subdomain and main domain have similar landing pages of same topics with content relevancy about 50% to 70%. Both pages will be in SERP and confusing users; possibly search engine too. We would like solve this by using canonicals on subdomain pointing to main domain pages. Even our intention is to only to show main domain pages in SERP. I wonder how Google handles it? Will the canonicals will be respected with this content relevancy? What happens if they don't respect? Just ignore or penalise for trying to do this? Thanks
Algorithm Updates | | vtmoz0 -
Do more internal links from sub-domains to domain (website) hurt rankings?
Hi, We have nearly 10 sub-domains. Couple of our website top pages including homepage have been linked from every page of these sub-domains; from footer or top menu. Is this kind of linking is bad as per Google? What is the right way of linking between website and sub-domains?
Algorithm Updates | | vtmoz0 -
Is it bad from an SEO perspective that cached AMP pages are hosted on domains other than the original publisher's?
Hello Moz, I am thinking about starting to utilize AMP for some of my website. I've been researching this AMP situation for the better part of a year and I am still unclear on a few things. What I am primarily concerned with in terms of AMP and SEO is whether or not the original publisher gets credit for the traffic to a cached AMP page that is hosted elsewhere. I can see the possible issues with this from an SEO perspective and I am pretty sure I have read about how SEOs are unhappy about this particular aspect of AMP in other places. On the AMP project FAQ page you can find this, but there is very little explanation: "Do publishers receive credit for the traffic from a measurement perspective?
Algorithm Updates | | Brian_Dowd
Yes, an AMP file is the same as the rest of your site – this space is the publisher’s canvas." So, let's say you have an AMP page on your website example.com:
example.com/amp_document.html And a cached copy is served with a URL format similar to this: https://google.com/amp/example.com/amp_document.html Then how does the original publisher get the credit for the traffic? Is it because there is a canonical tag from the AMP version to the original HTML version? Also, while I am at it, how does an AMP page actually get into Google's AMP Cache (or any other cache)? Does Google crawl the original HTML page, find the AMP version and then just decide to cache it from there? Are there any other issues with this that I should be aware of? Thanks0 -
Image Thumbnail in Google Mobile Search results
HI all, We can see that Google is now showing thumbnails of products in the search results on mobile.
Algorithm Updates | | RetailClicks
Very nice, but... What are specs of our snippets to show? Cause i see it at other search results of websites, but not ours?
Please help us out. Thanks!
Jeroen http://searchengineland.com/google-mobile-search-results-now-showing-images-snippets-2589190 -
Are multiple domains for my website hurting my Google ranking?
Hello, I currently have two domains showing up in google search: shwoodshop.com shop.shwoodshop.com These domains are currently ranked in the #2 and #3 spot, however my page is much more trafficked than the current #1 ranking. I am wondering if the fact that I have two domains competing for the #1 spot is hurting my search ranking. If so, what is the best way to remedy this issue and get back my #1 spot? I'm rather new to SEO and teaching myself as I go, so I appreciate the feedback!
Algorithm Updates | | shwoodshop0 -
What is the best way to build a Mobile Site?
I am looking into building a mobile version for my website, knowing that Google Likes Google should I stick with using their mobile building tool or build something from scratch in Dreamweaver? How to optimize for Google Mobile? Thx
Algorithm Updates | | Ben-HPB0 -
Google SERPS problem - "block all results from this domain - click here".
Anyone know what can be done about this when it happens to one of your own domains? On the Google SERPS page, underneath the Title, next to the Description, Google has added "Block all results from this domain?". I understand that this is a new "feature", aimed at allowing users to filter out results from low quality, pornograhphic or offensive sites. But the site in question is none of the above - any ideas how to tackle? Couldn't find anything yet by searching.
Algorithm Updates | | Understudy0 -
Google changing the casing in SERPs of our domain name in Title tag!
I've added NOODP and NOYDIR metas to our pages... but Google is still somehow showing the correct title tag that is on the page, but is changing the CASING of the | Domain.com portion. In some instances, they are still showing a different title tag all together. Why would they be ignoring the <title>tag on the page and placing an uncased version of our domain name at the end?</p> <p> </p> <a download="MxQjo" class="imported-anchor-tag" href="http://imgur.com/MxQjo" target="_blank">MxQjo</a></title>
Algorithm Updates | | CareerBliss0