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
-
In writing the url, it is better to use the language used by the people of my country or English?
We speak Persian and all people search in Persian on Google. But I read in some sources that the url should be in English. Please tell me which language to use for url writing?
Technical SEO | | ghesta
For example, I brought down two models: 1fb0e134-10dc-4737-904f-bfdf07143a98-image.png https://ghesta.ir/blog/how-to-become-rich/
2)https://ghesta.ir/blog/چگونه-پولدار-شویم/0 -
Does having a sub-domain on a different server affect SEO?
I'm working with a company that has a hard-coded website on the root domain, and then a WordPress blog on a subdomain on a separate server. We're planning on implementing a hub and spoke model for their content, hosting the main hubs on the root domain and the linked articles on the blog. Is having the blog on a different server going to hinder our SEO efforts?
Technical SEO | | KaraParlin0 -
English and French under the same domain
A friend of mine runs a B&B and asked me to check his freshly built website to see if it was <acronym title="Search Engine Optimization">SEO</acronym> compliant.
Technical SEO | | coolhandluc
The B&B is based in France and he's targeting a UK and French audience. To do so, he built content in english and french under the same domain:
https://www.la-besace.fr/ When I run a crawl through screamingfrog only the French content based URLs seem to come up and I am not sure why. Can anyone enlighten me please? To maximise his business local visibility my recommendation would be to build two different websites (1 FR and 1 .co.uk) , build content in the respective language version sites and do all the link building work in respective country sites. Do you think this is the best approach or should he stick with his current solution? Many thanks1 -
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 -
Moving my domain to weebly
I am thinking of moving my html website to weebly. They offer a 301 redirect for my domain name. Is that ok for SEO?
Technical SEO | | bhsiao0 -
Correct linking to the /index of a site and subfolders: what's the best practice? link to: domain.com/ or domain.com/index.html ?
Dear all, starting with my .htaccess file: RewriteEngine On
Technical SEO | | inlinear
RewriteCond %{HTTP_HOST} ^www.inlinear.com$ [NC]
RewriteRule ^(.*)$ http://inlinear.com/$1 [R=301,L] RewriteCond %{THE_REQUEST} ^./index.html
RewriteRule ^(.)index.html$ http://inlinear.com/ [R=301,L] 1. I redirect all URL-requests with www. to the non www-version...
2. all requests with "index.html" will be redirected to "domain.com/" My questions are: A) When linking from a page to my frontpage (home) the best practice is?: "http://domain.com/" the best and NOT: "http://domain.com/index.php" B) When linking to the index of a subfolder "http://domain.com/products/index.php" I should link also to: "http://domain.com/products/" and not put also the index.php..., right? C) When I define the canonical ULR, should I also define it just: "http://domain.com/products/" or in this case I should link to the definite file: "http://domain.com/products**/index.php**" Is A) B) the best practice? and C) ? Thanks for all replies! 🙂
Holger0 -
Does image domain name matter when using a CDN?
Has anyone does studies on using a different CDN domain name for images on a site? Here is an example:
Technical SEO | | findwellor http://cdn.mydomain.com/image.jpg> mydomain.com ranks highly and many images show up in Google/Bing image searches. Is there any actual data that says that using your real domain name for the CDN has benefits versus the default domain name provided by the CDN provider? On the surface, it feels like it would, but I haven't experimented with it.
0 -
What is the best method to block a sub-domain, e.g. staging.domain.com/ from getting indexed?
Now that Google considers subdomains as part of the TLD I'm a little leery of testing robots.txt with something like: staging.domain.com
Technical SEO | | fthead9
User-agent: *
Disallow: / in fear it might get the www.domain.com blocked as well. Has anyone had any success using robots.txt to block sub-domains? I know I could add a meta robots tag to the staging.domain.com pages but that would require a lot more work.0