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.
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
-
I have a question about the impact of a root domain redirect on site-wide redirects and slugs.
I have a question about the impact (if any) of site-wide redirects for DNS/hosting change purposes. I am preparing to redirect the domain for a site I manage from https://siteImanage.com to https://www.siteImanage.com. Traffic to the site currently redirects in reverse, from https://www.siteImanage.com to https://siteImanage.com. Based on my research, I understand that making this change should not affect the site’s excellent SEO as long as my canonical tags are updated and a 301 redirect is in place. But I wanted to make sure there wasn’t a potential consequence of this switch I’m not considering. Because this redirect lives at the root of all the site’s slugs and existing redirects, will it technically produce a redirect chain or a redirect loop? If it does, is that problematic? Thanks for your input!
Technical SEO | | mollykathariner_ms0 -
Forwarding a .org domain to a .com domain: any negative impact to consider?
Hello! I have a question I've been unable to find a clear answer to. My client's primary domain is a .com with a satisfactorily high DA. My client owns the .org version of its domain (which has a very low DA, I suppose due to inactivity) but has never forwarded it on. For branding/visibility/traffic reasons, I'd like to recommend they set up the .org domain to forward to the .com domain, but I wanted to ask a few questions first: 1. Does forwarding low-value DA domains to high-value DA domains have any negative authority/SEO impact? 2. If the .org domain was to be forwarded, am I correct that an SSL cert is not necessary for it if the .com domain has an SSL cert? Thanks in advance!
Technical SEO | | mollykathariner_ms1 -
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 -
When you change your domain, How much time do I have to wait for google to return the traffic used to have?
Hello. 20 days ago, I changed my domain from uclasificados.net to uclasificados.com doing redirect 301 to all urls, and I started to loose rankings since that moment. I was wondering if changing it back could be the solutions, but some experts recommend me not to do that, because it could be worse. Right now I receave almost 50% of traffic I used to receave before, and I have done a lot of linkbuilding strategies to recover but nothing have worked until now. Even though I notified google of this change and I send again my new sitemap, I don't see that have improve my situation in any aspects, and I still see in webmastertools search stats from my last website (the website who used to be uclasificados.com before the change). What should I do to recover faster?
Technical SEO | | capmartin850 -
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 | | findwell
or
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 -
Tutorial For Moving Blogger Blog From Sub-Domain to Sub-Directory
Does anyone know where I can find a tutorial for moving a blogger.com (blogspot) blog that's currently hosted on a subdomain (i.e. blog.mysite.com) to a subdirectory (i.e. mysite.com/blog) with the current version of blogger? I'm working on transferring my blogger blogs over to wordpress, and to do so without losing link juice or traffic, this is one of the steps I have to take. There's plenty of tutorials that address moving from blogspot.mysite.com to wordpress and I've even found a few that address moving from blog.mysite.com (hosted on blogger) to a root domain mysite.com. However, I need to move from blog.mysite.com (blogger) to mysite.com/blog/ - subdirectory (wordpress). Anyone who knows how to do this or can point me in the right direction?? Thanks.
Technical SEO | | ChaseH0 -
Multiple Domains, Same IP address, redirecting to preferred domain (301) -site is still indexed under wrong domains
Due to acquisitions over time and the merging of many microsites into one major site, we currently have 20+ TLD's pointing to the same IP address as our "preferred domain:" for our consolidated website http://goo.gl/gH33w. They are all set up as 301 redirects on apache - including both the www and non www versions. When we launched this consolidated website, (April 2010) we accidentally left the settings of our site open to accept any of our domains on the same IP. This was later fixed but unfortunately Google indexed our site under multiple of these URL's (ignoring the redirects) using the same content from our main website but swapping out the domain. We added some additional redirects on apache to redirect these individual pages pages indexed under the wrong domain to the same page under our main domain http://goo.gl/gH33w. This seemed to help resolve the issue and moved hundreds of pages off the index. However, in December of 2010 we made significant changes in our external dns for our ip addresses and now since December, we see pages indexed under these redirecting domains on the rise again. If you do a search query of : site:laboratoryid.com you will see a few hundred examples of pages indexed under the wrong domain. When you click on the link, it does redirect to the same page but under the preferred domain. So the redirect is working and has been confirmed as 301. But for some reason Google continues to crawl our site and index under this incorrect domains. Why is this? Is there a setting we are missing? These domain level and page level redirects should be decreasing the pages being indexed under the wrong domain but it appears it is doing the reverse. All of these old domains currently point to our production IP address where are preferred domain is also pointing. Could this be the issue? None of the pages indexed today are from the old version of these sites. They only seem to be the new content from the new site but not under the preferred domain. Any insight would be much appreciated because we have tried many things without success to get this resolved.
Technical SEO | | sboelter0