Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Using hyphenated sub-domains or non-hyphenated sub-domains? What is the question! I Any takers?
-
For our corporate business level domain, we are exploring using a hyphenated sub-domain foir a project.
Something like www.go-figure.extreme.com
I thought from a user perspective it seems cluttered. The domain length might also be an issue with the new Algorithm big G has launched in recent past.
I know with past experience, hyphenated domains usually take longer to index, as they are used by spammers more frequently and can take longer to get out of the supplementary index.
Our company site has over 90 million viewers / year, so our brand is well established and traffic isn't an issue. This is for a corporate level project and I didn't have the answer!
Will this work? anyone have any experience testing this. Any thoughts will help!
Thanks, Rob
-
I agree - it was Google itself that suggested hyphenating keywords in url's.
Example - I was just using the Moz keyword tool on a site named sellmybusinesscolorado.com. The search term it was tuned to was "sell business colorado". The tool, and so likely the bots, did not recognize those very words in that long URL. Had it been hyphenated - they would have been recognized.
What brought me here was - is hyphenating, itself, non kosher in a sub domain? Thomas, coincidentally - the subdomain I was pondering is pest-control.straza.com. He is a business broker that sells a lot of pest control businesses. I also would do medical.straza.com. These subs will deal with their namesakes as if they were the only businesses they sell.
Google recognizes the hyphen as the universal word separator. I stopped using underbars ten years ago - a nasty habit I learned from programmers.
I think it is more the ABUSE of a good thing, as it always is, that should be avoided.
........... I didn't name that site, by the way ;-]
-
I agree (FWIW)
-
There will be no SEO fall out due to hyphen.
It's a personal preference.
I like: footballsport.mysite.com
I don't like: football-sport.mysite.com
No hyphen just seems to be more common. Users may get confused only upon remembering the subdomain. "uh... I think there is a silent hyphen in that URL...??? Or was it no hyphen?"
So if you use football-sport.mysite.com then redirect footballsport.mysite.com to football-sport.mysite.com.
-
Thanks. It was a little of both in terms of concerns. I didn't want indexing issues, and the hyphen just threw me off - as well as it impacting the usability of the page. As long as they hyphen will work in the sub-domain I'm good to go. I didn't want any issues later Thanks to all who replied!
-
I suppose that we're not understanding your concern. Is the concern over incorporating a keyword or is the question about whether a hyphen has negative consequences?
If it's a keyword issue you can use keyword.example.com or key-word.example.com. No difference from an SEO perspective. It's more about convenience/usability (ease of conveying the address via various media).
I doubt that one dash will cause indexation/ranking issues. I don't see this as an issue.
-
this is actuallly for the sub-domain, not the primary domain.
so football.mysite.com as opposed to something like football-sport.mysite.com
It's the hyphen that's throwing me out of whack..
Ideas? and thanks for the insights~!!
-
Sorry - should have said "not very friendly!"
-
You shouldn't experience any problems with a hyphen in the domain name. Exact Match domains seem to rank better, but most likely not directly associated with the exact match but the domain history and content. Even with a hyphen you get a close match. I have seen hyphen domains rank just fine.
The only concern I would have is consistency within the domain name. You may throw of users by adding a hyphen to an unhyphenated domain. Personally I would opt against using the hyphen. People have learned to read through domain names at this point.
If you do go with the hyphen make sure you redirect the unhyphenated version to the hyphenated version.
-
I agree. I'm still on the fence about the hyphenated sub-domain. I can't find too many sites that actually practice this technique. i'm looking for some references online.
This domain won't be spoken over the phone, and from a usability perspective, but very flashy r friendly.
I wanted to use something like say football.mysite.com instead of football-sport.mycompany.com
i'm still perplexed!! LOL
-
Avoid multiple hyphens (eg key-word-stuffed-subdomain.example.com). Your example only has one-not a concern. The SEs are able to read domains/subdomains with spacers or not. Not a concern there either. In the example you've provided, the issue is more about usability. If you ever have to speak a URL over the phone it'll be much easier without the dash.
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
-
Disavow to all domains?
Hi there, I have several versions of my domain setup in Webmaster tools. Should I upload my disavow file against all of these domains? For example.....
Technical SEO | | niallfred
If I find a link pointing to: http://www.mydomain.com from: http://www.somespammysite.com do I need to add a disavow file in Webmaster tools for all my domain versions or only the version the offending links points towards? So... Only
http://www.mydomain.com
Or
http://www.mydomain.com
http://mydomain.com
https://www.mydomain.com
https://mydomain.com0 -
What should I consider before setting up a sub domain?
Morning all! We've just been approached by IT. They've been asked to develop an online 'portal' where clients can upload and download materials. IT will be developing a portal that sits on the company network perimeter (hosted on our internal servers). The concept is that 3<sup>rd</sup> parties can get and update information in regards to progressing cases, the first use will be for agencies who will retrieve records via the portal and then post reports after a consultation. however I would like to have an automatic link to forward to the portal from the web address: oursite.com/dave We will look to create robot.txt and anything else to prevent from listings/indexes. Does any of the above mess with your SEO? The Directors have asked if they can have this on a sub-domain of our site. Is this wise? And, are there any major SEO considerations for my team to worry about? Better still, have any of you had to deal with this before? If so, what happened? All the best, John
Technical SEO | | Muhammad-Isap0 -
Moving from www.domain.com/nameofblog to www.domain.com/blog
Describe your question in detail. The more information you give, the better! It helps give context for a great answer I have had my blog located at www.legacytravel.com/ramblings for a while. I now believe that, from an SEO perspective, it would be preferable to move it to www.legacytravel.com/blog. So, I want to be able to not lose any links (few though they may be) with the move. I believe I would need to do a 301 redirect in the htaccess file of www.legacytravel.com that will tell anyone who comes knocking on the door of www.legacytravel.com/ramblings/blah blah blah that now what they want is at www.legacytravel.com/blog/blah blah blah Is that correct? What would the entry look like in the htaccess? Thank you in advance.
Technical SEO | | cathibanks0 -
One server, two domains - robots.txt allow for one domain but not other?
Hello, I would like to create a single server with two domains pointing to it. Ex: domain1.com -> myserver.com/ domain2.com -> myserver.com/subfolder. The goal is to create two separate sites on one server. I would like the second domain ( /subfolder) to be fully indexed / SEO friendly and have the robots txt file allow search bots to crawl. However, the first domain (server root) I would like to keep non-indexed, and the robots.txt file disallowing any bots / indexing. Does anyone have any suggestions for the best way to tackle this one? Thanks!
Technical SEO | | Dave1000 -
Referrals from widget domains
Let's say you are doing seo for a company that sells 5000 widgets. Let's call their site www.mainsite.com ... They have already set up ( purchased ) many domains such as www.widget1.com which is one of the widgets they have on their main site. so they might have several hundred of these domains. What is the best use of these domains? Would it be : Have those pages be landing pages with content and pictures and optimized with a link to their main site widget page? Or have that domain have a 301 redirect to go their main site, to the particular page showing that widget for sale off their main site? Miscellaneous sidebar question - Since both the main site widget page and the widget domain might be in competition and might have duplicate content, what are the ramifications of not using the canonical tag, and what other considerations might there be? How much must be duplicate content before considering using the canonical tag?
Technical SEO | | highersourcesites0 -
Sub domain versus sub directory
Hey all, Has Google finally grown up to treat sub-domains as they would sub directory? i.e: http://blog.example.com as opposed to http://example.com/blog I desperately wanted example.com/blog but we were forced to launch with blog.example.com because of WordPress limitations and our DNS and load balancing set up on our end. All searches lead me to old documentation 2010 and earlier. Wondering if anyone has any up to date information around this. Cheers, Croozie,
Technical SEO | | sichristie0 -
Domain Masking with New Keyword-Rich Domains
Hello, friends. We have an ecommerce site and we also own several keyword-rich domains but haven't done anything with them yet. Is there any value in using domain masking to point them to either product pages or special landing pages on our primary ecommerce site? Here's an example: Primary site is widgetzone.com Keyword rich URL is acmewidget.com (which is totally blank and isn't indexed) It could point to our category page for Acme Widgets: widgetzone.com/category/acme-widgets or it could point to a new landing page: widgetzone.com/acme-widgets My concern is that because the keyword-rich URL hasn't been utilized at all there's really no point in redirecting it. I'm of the mind that it's either going to be ineffective at best or a duplicate content issue at worst. What do you guys think? As a follow-up, if we don't redirect these domains, what should we do with them? Just try to sell them off rather than create totally new sites?
Technical SEO | | jbreeden0 -
New Sub-domains or New Directories for 10+ Year Domain?
We've got a one-page, 10+ year old domain that has a 65/100 domain authority that gets about 10k page views a day (I'm happy to share the URL but didn't know if that's permitted). The content changes daily (it's a daily bible verse) so most of this question is focused on domain authority, not the content. We're getting ready to provide translations of that daily content in 4 languages. Would it be better to create sub-domains for those translations (same content, different language) or sub-folders? Example: http://cn.example.com
Technical SEO | | ipllc
http://es.example.com
http://ru.example.com or http://example.com/cn
http://example.com/es
http://example.com/ru We're able to do either but want to pick the one that would give the translated version the most authority both now and moving forward. (We definitely don't want to penalize the root domain.) Thanks in advance for your input.0