What's better .NET or a hyphenated.COM domain
-
What's better .NET or a hyphenated .COM domain
I know this is simple but in selecting a domain for my current project and I only have two options.
firstname-lastname.COM or
firstnamelastname.NETI'm leaning to the .COM as after reading the how to choose a domain name post.
http://www.seomoz.org/blog/how-to-choose-the-right-domain-name
Thanks
-
Thanks for the responses, its sounds like the SEO programatic stuff is all about even.
It the human factor that is really up for grabs here, what's easier to read, remember, speak, and trust.
In my case its all about personal brand so a hyphenated .com maybe easier to remember and trust then a non-hyphenated .net which could get confused for a .com
Sounds like i'm still choicing between two good options but not the best option
And yes I'm looking at ronsparks.net vs ron-sparks.com and other future domains with a simliar issue.
ps @EGOL ronskickasssite.com is available tho its a bit hard to read with all those S's
-
I have really strong feelings about hyphen domains and domains other than .com. Most of this is from running retail sites on hyphen domains and trying to explain to people by phone about the hyphen and hearing from them how they went to the wrong domain when trying to visit. The last customers I want going to the wrong domain are the people who are typing it in!
So, after hearing this stuff for a long time I paid hideous sums to get the unhypenated domains and the guys who I bought them from told me that their typein traffic was rising every year.
But, I have those domains now and am happy... well... there is one more that I would like to get.
They say that converts are the worst type of fanatic.
-
EGOL,
While I do not think your response is without merit and I do sometimes consider the issue of which is easier to remember, I am not sure it is as relevant as it was when Rand made that post in 2007. As we see so many sites today with hyphens, I think more people are used to them. But, that does not mean it won't happen.
I think, once someone has seen it visually it is not an issue. If I am doing radio it is. With a non visual medium, you are forced to spell it out and say something like (remember to put in a hyphen between Rons and kickass and Site.net!) That is not a great option.
With most of our sites, people are clicking the link organically for our eCommerce where there are return customers, we are leaving cookies and bookmark options.
As to spending money to get the site you want, it is relative depending on the client. If a client is new (I have a small client who came from a relative that is two ladies who do baby sitting and pet sitting and we are building a 5 to 6 page site for) to business and has a low budget, getting the dream domain is sometimes not possible. Yes, for Fortune 500 they will likely blow a bunch for insuring a branding option.
But, again, it is two sides to a very interesting coin.
Always appreciate your opinions as you think before you write.
Best -
I agree they are equal in SEO, but I also agree you will get differing opinion about looking spammy. i think hythens look spammy, but are coming a bit more normalized as time goes on, but anouther reason is that they are hard to say, image a radio ad, the reader having to explained the hythens
at coca hythen cola dot com
-
I used to have sites with hyphens... and all of my hard work was enriching the guys who owned the domains without a hyphen. The harder I worked to make my site popular the more they enjoyed it. I finally gave in and paid big bucks to get those domains.
So when you are workin hard to make Rons-KickAss-Site.com AND RonsKickAssSite.net huge successes they guy who owns RonsKickAssSite.com will be smiling as lots of your customers land on his spammy site and click ads to sorry domains. Not a good customer experience and not good for your wallet - because the people who remember the name of your site well enough to type it in without a hyphen were probably going to buy something. Nice you just lost that $2000 sale to someone else - and he thinks you went out of business.
So, spend a little more time coming up with a kickass domain or be willing to spend some money to get the domain that you want. Because if you own RonsKickAssSite.com I doubt that anyone is going to look for you at Rons-KickAss-Site.com
Here's a couple of quotes from Rand's post..... at http://www.seomoz.org/blog/how-to-choose-the-right-domain-name
and while directing traffic to a .net or .org (as SEOmoz does) is fine, owning and 301'ing the .com is critical.
Both hyphens and numbers make it hard to give your domain name verbally and falls down on being easy to remember or type.
-
I agree with Robert. The ranking difference between .com / .net and no-hyphen / one-hyphen is going to be minimal. So go for the domain that is easier to read. That will probably benefit you in the long run.
-
My personal opinion is that you can do either, but I would go with the hyphen.com. The reason for me is simple it is easier to read. That said, you will shortly have other opinions and they will revolve around being spammy. There is no increase or decrease in SEO value and I have yet to see any quantification of the spammy factor and any effect on CTR or conversions. But, I don't think the hyphen will out perform the non hyphen.net. I think all things being equal, they will be equal.
Best
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
-
Is it necessary to have unique H1's for pages in a pagination series (i.e. blog)?
A content issue that we're experiencing includes duplicate H1 issues within pages in a pagination series (i.e. blog). Does each separate page within the pagination need a unique H1 tag, or, since each page has unique content (different blog snippets on each page), is it safe to disregard this? Any insight would be appreciated. Thanks!
Algorithm Updates | | BopDesign0 -
SEO threats of moving from [.com.au] domain to [.com] domain for a 15yr old SAAS company.
Hey Guys. I work for a 15 yr old SAAS company which originally started with a country-specific [.com.au] domain and later got a [.com] domain as the business grew. The AU website has a DA:56 while the [.com] has as DA: 25. Now we are looking to have everything migrated to the [.com] domain. But, my concern is that we might lose the SEO value of the AU domain. I was wondering if anyone has any experience in this or recommend a case study on this topic. Thanks! Allan
Algorithm Updates | | allanhenryjohn0 -
Sub domains take away the pagerank/link juice of main website?
Hi all, I would like to know how sub domains will be collaborated with domain or main website in terms of authority, backlinks, link juice, etc...Link juice will be passed to sub domains from domain or vice versa? If there are large number of pages in sub domain, will that going to impact the ranking of main domain? Backlinks of sub domain are going to be a deciding factor for website ranking too? Thanks
Algorithm Updates | | vtmoz0 -
Duplicate content on a sub domain
I have two domains www.hairremoval.com and a sub domain www.us.hairromoval.com both sites have virtual the same content apart from around 8 pages and the sub domain is more focused to US customers so the spelling are different, it is also hosted in the states. Would this be classed as duplicate content ? (The url’s are made up for the question but the format is correct)
Algorithm Updates | | Nettitude0 -
301 a purchased domain
I've purchased a competitor. They rank well organically for keywords that I target, and I want to optimize the way I get value from their current rankings and traffic (and customers -- we will obviously market to their email/customer list). Which is better: (1) use a 301 redirect for any access to their domain and point it to my home page. I think this would force Google to de-index all of their pages, right? (2) put up a stub page as their homepage that announces the site has been bought, and have a do-follow link to my home page (which maybe is auto-redirected after 10 seconds or something)? Maybe this is better to keep their home page in Google's index for a while? As for option (1), I thought I read somewhere recently that 301'ing a domain to the home page of another domain would no longer pass link juice (?). Maybe I should 301 the newly purchased domain to a sub-page on my site that explains the acquisition and asks them to sign up on my site? Both sites are legit. No spamming happening here; just industry consolidation as one competitor acquires another. Thanks in advance...!
Algorithm Updates | | scanlin0 -
Re-direct domain ranking higher than main domain 6 months later
Hello, I have a question regarding a couple of our in-house domains & rankings. We have our main site which we've had for 3+ years, moderately optimised. And our separate site for another publication, this was it's own stand-alone site but now that site has been removed off our servers & the old domain a straight forward http re-direct via 1&1 to the main website. The old site was removed & forward set up before October 2011, however when searching Google for 'specification online' the old domain appears position #1. We have many other domains which are http re-directs with 1&1 and none of these have causes us this issue. What else can I do to get the old domain to stop showing up on Google? Domains in questions: Main site: http://specificationonline.co.uk Old site: http://housingspecification.com If you need any further info I'll be happy to provide as we owned both domains & hosting from day 1 so can access anything required.
Algorithm Updates | | thestudio40 -
Was Panda applied at sub-domain or root-domain level?
Does anyone have any case studies or examples of sites where a specific sub-domain was hit by Panda while other sub-domains were fine? What's the general consensus on whether this was applied at the sub-domain or root-domain level? My thinking is that Google already knows broadly whether a "site" is a root-domain (e.g. SEOmoz) or a sub-domain (e.g. tumblr) and that they use this logic when rolling out Panda. I'd love to hear your thoughts and opinions though?
Algorithm Updates | | TomCritchlow1