Community inside the domain or in a separate domain
-
Hi there,
I work for an ecommerce company as an online marketing consultant. They make kitchenware, microware and so on.
The are reviewing their overall strategy and as such they want to build up a community.
Ideally, they would want to have the community in a separate domain. This domain wouldn't have the logo of the brand. This community wouldn't promote the brand itself. The brand would post content occassionally and link the store domain. The reasoning of this approach is to not interfere in the way of the community users and also the fact that the branded traffic acquired doesn't end up buying at the store
I like this approach but I am concerned because the brand is not that big to have two domains separated and lose all the authority associated with one strong domain. I would definitely have everything under the same domain, store and community, otherwise we would have to acquire traffic for two domains.
1. What do you think of both scenarios, one domain versus two? Which one is better?
2. Do you know any examples of ecommerce companies with successful communities within the store domain?
Thanks and regards
-
EGOL and Samuel raise some very good points here. I feel like you're also somewhat at risk of looking like you're trying to deceive the audience if you're deliberately divorcing the community from the brand site and image, but using it to drive the community to commercial action. I am not sure how subtle they are planning on making that connection, but subtlety in that manner rarely works: it's a lot more "honest" and appreciated to cultivate a community and openly market a product, as Moz has done.
Using the Moz example, this site did not start out as a tool / analytics provider, so the community actually came first. When I was a full time employee, we were largely an SEO consultancy. The blog was a labour of love as far as Rand and the staff were concerned. In 2007 when we first introduced Premium (now Pro) accounts, we clearly used the community (which was pretty substantial, even back then) to market the service. To all but a very few negative folks, this went down fine.
If Rand had started a separate company and website hosting and selling SEO tools and subscriptions, and had dropped hints and posts every now and again here to promote it, it would not have been met with nearly as much favour.
The SEO points about two sites being twice as hard to maintain, market and rank than one also apply, but I would question whether a smaller brand can build a totally separate community that is a) big enough, and b) independent enough not to annoy users if they figure out the commercial intent behind it. If there's one thing that's slightly worse than no community, it's an empty one.
-
Forums take a LOT of work. If they want the forum to be successful and reflect well on the company then they should put it on the main domain where their name is on the line and all of their clients will see it and have an opportunity to check it out and use it regularly.
If they are not serious about this then just put the forum in an outhouse where nobody will see it. It's going to die because they are not dedicated to it.
-
Diego, thanks for the question. The issue is complicated, so I'll try to summarize point by point.
Ideally, they would want to have the community in a separate domain. This domain wouldn't have the logo of the brand. This community wouldn't promote the brand itself.
First off, I have to question the brand strategy. WHY does your company not want to the community to build the brand directly? A good, positive online community -- when run well -- can do wonders for a brand over the long term. Hey, just look at how much people love Moz just because of the community. I see no benefits to your company's idea -- and I see a lot of negatives.
The reasoning of this approach is to not interfere in the way of the community users and also the fact that the branded traffic acquired doesn't end up buying at the store
I don't buy this premise. There are times when direct sales are not the best Key Performance Indicator (KPI) of a certain marketing tactic. An online community builds a brand for the long term -- the KPIs may be metrics such as reach and more rather than direct sales resulting from community traffic and posts.
I'd read or watch this Whiteboard Friday -- it's on content marketing, but the idea is relevant. Few people see a piece of content and buy. But that's not the point. The more that people see the content time and time and time again, then the more likely it is that they will remember you when they do want to buy. It's the same idea in advertising: no one buys Coke because of an ad that they saw yesterday -- they buy Coke because of the ads they have seen for their entire lives. Likewise, no one is going to buy after reading a single community post. But the more that people engage and engage and engage with the branded community, the more likely it is that they will buy in the future. It's a long-term play.
Ideally, they would want to have the community in a separate domain.
Do you mean an entirely-separate root domain or a subdomain of the main root domain?
Either way, the same argument below applies.
I am concerned because the brand is not that big to have two domains separated and lose all the authority associated with one strong domain. I would definitely have everything under the same domain, store and community, otherwise we would have to acquire traffic for two domains.
You are correct. As much as Google likes to say that subdomains are treated the same as root domains, most of the data we've seen suggests otherwise. It's best to keep everything under the same root domain. If someone links to a community post or discussion and it's on a subdomain or another domain, then the main website will get little benefit.
Point: However, there are two times when a subdomain (or another root domain) may be better:
1. Creating a part of the website that will be less secure than the main website. Common example: A website has very confidential information, so they add a blog by putting Wordpress on a subdomain because Wordpress is less secure.
2. Very different design. It's a lot easier to have a completely-different design on a subdomain rather than in a subfolder on the main website.
Still, I'd suggest putting everything under the same root domain whenever possible. I hope this helps!
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
-
Legacy domains
Hi all, A couple of years ago we amalgamated five separate domains into one, and set up 301 redirects from all the pages on the old domains to their equivalent pages on the new site. We were a bit tardy in using the "change of address" tool in Search Console, but that was done nearly 8 months ago now as well. Two years after implementing all the redirects, the old domains still have significant authority (DAs of between 20-35) and some strong inbound links. I expected to see the DA of the legacy domains taper off during this period and (hopefully!) the DA of the new domain increase. The latter has happened, although not as much as I'd hoped, but the DA of the legacy domains is more or less as good as it ever was? Google is still indexing a handful of links from the legacy sites, strangely even when it is picking up the redirects correctly. So, for example, if you do a site:legacydomain1.com query, it will give a list of results which includes pages where it shows the title and snippet of the page on newdomain.com, but the link is to the page on legacydomain1.com. What has prompted me to finally try and resolve this is that the server which hosted the original 5 domains is now due to be decommissioned which obviously means the 301 redirects for the original pages will no longer be served. I can set up web forwarding for each of the legacy domains at the hosting level, but to maintain the page-by-page redirects I'd have to actually host the websites somewhere. I'd like to know the best way forward both in terms of the redirect issue, and also in terms of the indexing of the legacy domains? Many thanks, Dan
Intermediate & Advanced SEO | | clarkovitch0 -
Redirecting main www. subdomain to new domain. Can you then create a new subdomain on the old domain?
Hi there, The scenario is this: We have been working on a rebrand and have changed the company name So, we want to redirect www.old-name.com to www.new-name.com However, the parent company is retaining the old brand name for corporate purposes So, in an ideal world, we'd be able to keep www.old-name.com active - but clearly that would sacrifice all of the authority built up over the years, so we do have to redirect the main www. subdomain in it's entirity. However - one suggested solution is to redirect www.old-domain.com to www.new-domain.com... but then create a new corporate subdomain: for example, business.old-domain.com business.old-domain.com will not be competing with the new site on any service/product related terms; it will only need to appear in SERPs for the company name I'd appreciate some thoughts on this, as I've not done this before or found any examples of anyone that has. Is that a massive risk in terms of sending a confusing message to Google? Thanks for your help
Intermediate & Advanced SEO | | edlondon0 -
What is better for web ranking? A domain or subdomain?
I realise that often it is better put content in a subfolder rather than a subdomain, but I have another question that I cannot seem to find the answer to. Is there any ranking benefit to having a site on a .co.uk or .com domain rather than on a subdomain? I'm guessing that the subdomain might benefit from other content on the domain it's hosted on, but are subdomains weighted down in any way in the search results?
Intermediate & Advanced SEO | | RG_SEO0 -
Microsites: Subdomain vs own domains
I am working on a travel site about a specific region, which includes information about lots of different topics, such as weddings, surfing etc. I was wondering whether its a good idea to register domains for each topic since it would enable me to build backlinks. I would basically keep the design more or less the same and implement a nofollow navigation bar to each microsite. e.g.
Intermediate & Advanced SEO | | kinimod
weddingsbarcelona.com
surfingbarcelona.com or should I rather go with one domain and subfolders: barcelona.com/weddings
barcelona.com/surfing I guess the second option is how I would usually do it but I just wanted to see what are the pros/cons of both options. Many thanks!0 -
Cross domain canonical and hreflang
Hi Guys, So we are close to launching our new site and just need to be sure that our canonical, duplicate issues are sorted before launch. So here is our current situation. The current site is on trespass.co.uk. Then new site will be on trespass.com. The new launch is global and we will have the 3 stores within magento all in english. Trespass.com for the UK
Intermediate & Advanced SEO | | Trespass
Trespass.com/US for US
Trespass.com/ROW for all other countries On trespass.com we have the following: On trespass.com/US we have the following: On trespass.com/ROW we have the following: This is how the magento developers.design company have set it up but am I right in saying the canonical tag for each store (/ROW and /US) should point to Trespass.com as the only difference is in the pricing £ $ and euros? Thanks for your help0 -
SEO for a redirected domain name
Our client is a law firm with a name that is challenging to spell. We have procured a domain name for them that is catchy, easy to spell, and plays well into their brand, or at least the current campaign. We're using the campaign domain to direct traffic to their website with a 301 redirect. We have placed the campaign domain in a variety of offline mediums including print and outdoor. The client is currently in the number 1 spot for a good number of our highest priority keywords, so I do not want to do anything to jeopardize that. I'm also not sure this campaign will be their "brand" long-term so I don't want to risk making a switch and making it back. So for now, I'm most comfortable leaving the campaign domain as a redirect to their primary domain. Recently, the client approached me complaining (legitimately) that when people google the campaign domain, they are brought to search results for an entirely different domain because Google "corrects" the domain name for them. This is obviously a bad thing, with many users defaulting to entering urls into Google instead of the address bar. If you tell Google that it was wrong about the autocorrection, our site is in the number 1 position. I liken the situation to Overstock.com using O.co as their offline domain, but overstock.com as their online domain. But imagine if you googled o.co and google brought you to a list of results for "on.co" because it assumed you fat-fingered it. Is there anything I can do to prevent the domain name from getting corrected by Google?
Intermediate & Advanced SEO | | steverobinson0 -
Aged domain and 301 redirect? (11 year old domain)
Hey everyone, I'm about to launch a new website for an accounting firm. They currently have a website, which has an 11 year old domain. They are doing very well locally for SEO, and i'm guessing it's because of the aged domain, as their website is very badly built, and contains almost no content. They would like to launch the new site with a simpler, easier to remember domain. If i launch the new site, point the aged domain using a 301 redirect, and do redirects for all of the old pages to the newer versions of them, is there a chance the company will lose their current SEO rankings? Thanks!
Intermediate & Advanced SEO | | RCDesign740 -
Moving to a new domain
We currently rank well in our niche on a long (and ambiguous) domain, but want to rebrand and have a shorter and more memorable domain. Keeping in mind we're already pointing good links at the new domain (301ing them to the old site), how long should we age the domain before switching the content and 301ing the old site?
Intermediate & Advanced SEO | | errspy0