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
-
Canonical homepage link uses trailing slash while default homepage uses no trailing slash, will this be an issue?
Hello, 1st off, let me explain my client in this case uses BigCommerce, and I don't have access to the backend like most other situations. So I have to rely on BG to handle certain issues. I'm curious if there is much of a difference using domain.com/ as the canonical url while BG currently is redirecting our domain to domain.com. I've been using domain.com/ consistently for the last 6 months, and since we switches stores on Friday, this issue has popped up and has me a bit worried that we'll loose somehow via link juice or overall indexing since this could confuse crawlers. Now some say that the domain url is fine using / or not, as per - https://moz.com/community/q/trailing-slash-and-rel-canonical But I also wanted to see what you all felt about this. What says you?
Technical SEO | | Deacyde0 -
Should a sub domain be a separate property in the Search Console?
We're launching a blog on a sub-domain of a corp site (blog.corpsite.com). We already have corpsite.com set up in the Search Console. Should I set up a separate property for this sub-domain in the Search Console (WMT) in order to manage it? Is it necessary? Thanks, JM
Technical SEO | | HeroDesignStudio0 -
Redirect typo domains
Hi, What's the "correct" way of redirecting typo domains? DNS A record goes to the same ip address as the correct domain name Then 301 redirects for each typo domain in the .htaccess Subdomains on typo urls still redirect to www or should they redirect to the subdomain on the correct url in case the subdomain exists?
Technical SEO | | kuchenchef0 -
Domains
My questions is what to do with old domains we own from a past business. Is it advantages to direct them to the new domain/company or is that going to cause a problem for the new company. They are not in the same industry.
Technical SEO | | KeylimeSocial0 -
Mobile Domain Setup
Hi, If I want to serve a subset of pages on my mobile set from my desktop site or the content is significantly different, i.e. it is not one to one or pages are a summarised version of the desktop, should I use m.site.com or is it still better to use site.com? Many thanks any help appreciated.
Technical SEO | | MarkChambers0 -
Any way around buying hosting for an old domain to 301 redirect to a new domain?
Howdy. I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway! Basically DomainA.com is being retired, and DomainB.com is going to be launched. We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately. Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com? Thanks!
Technical SEO | | SamTurri0 -
Subdomain and Domain Rankings
I have read here that domain names with keywords might add a boost to your search rank For instance using a completely inane example monkey-fights.com might get a boost compared to mfl.com (monkey fighting league) when searching for "monkey fights" There seems to be a hot debate as to how much bonus the first domain might get over the second, but leaving that aside for the moment. Question 1. Would monkey-fights.mfl.com get the same kind of bonus as a root domain bonus? Question 2. If the answer to 1 above was yes would a 301 redirect from the suddomain URL to root domain URL retain that bonus I was just thinking on how hard it is to get root domains these days that are not either being squatted on etc. and if this might be a way to get the same bonus, or maybe subdomains are less bonus prone and so it would be a waste of time Thanks
Technical SEO | | bThere0 -
Hyphenated Domain Names - "Spammy" or Not?
Some say hyphenated domain names are "spammy". I have also noticed that Moz's On Page Keyword Tool does NOT recognize keywords in a non-hyphenated domain name. So one would assume neither do the bots. I noticed obviously misleading words like car in carnival or spa in space or spatula, etc embedded in domain names and pondered the effect. I took it a step further with non-hyphenated domain names. I experimented by selecting totally random three or four letter blocks - Example: randomfactgenerator.net - rand omf act gene rator Each one of those clips returns copious results AND the On-Page Report Card does not credit the domain name as containing "random facts" as keywords**,** whereas www.business-sales-sarasota.com does get credit for "business sales sarasota" in the URL. This seems an obvious situation - unhyphenated domains can scramble the keywords and confuse the bots, as they search all possible combinations. YES - I know the content should carry it but - I do not believe domain names are irrelevant, as many say. I don't believe that hyphenated domain names are not more efficient than non hyphenated ones - as long as you don't overdo it. I have also seen where a weak site in an easy market will quickly top the list because the hyphenated domain name matches the search term - I have done it (in my pre Seo Moz days) with ft-myers-auto-air.com. I built the site in a couple of days and in a couple weeks it was on page one. Any thoughts on this?
Technical SEO | | dcmike0