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.
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.
Best posts made by Oversteer
-
RE: Using hyphenated sub-domains or non-hyphenated sub-domains? What is the question! I Any takers?
-
RE: Using hyphenated sub-domains or non-hyphenated sub-domains? What is the question! I Any takers?
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.
-
RE: There's a website I'm working with that has a .php extension. All the pages do. What's the best practice to remove the .php extension across all pages?
SEs read .php files so this change probably isn't necessary. If you did, you might establish rewrite rules in .htaccess and add 301 redirects. But again, why mess with the file extensions? Are they having indexation issues?