Hyphenated Domain Names and SEO: Do Hyphens Hurt Rankings?

Updated September 17, 2026: This article has been repositioned as an evergreen domain-selection guide. It separates Google’s documented position on hyphenated domains from URL-path guidance and explains when a domain change is, and is not, worth considering.

A hyphen in a domain name is not, by itself, a Google ranking penalty. Google has said this directly in its SEO Office Hours documentation, and John Mueller reaffirmed the point in June 2026. That settles the narrow SEO question.

It does not settle the domain decision. A domain still has to work as a brand, be easy to communicate, avoid unnecessary confusion, and remain suitable as the business grows. Those are business and usability considerations, not hidden Google penalties.

The most useful approach is therefore to separate three questions that are often mixed together: whether Google penalises a hyphenated domain, whether Google recommends hyphens inside page URLs, and whether an existing site should migrate to remove a hyphen. The answers are different.

Table of Contents

Google’s Position Is Clearer Than the SEO Myth

Google’s formal documentation provides the strongest starting point. In the December 2022 Google SEO Office Hours transcript, a site owner asked whether having two hyphens in a domain name had a negative effect on rankings. Google’s answer was that multiple dashes in the domain do not have a negative effect.

On June 8, 2026, Google Search Advocate John Mueller revisited the same subject on Bluesky and again said that dashes in domain names are fine for SEO. The post attracted attention because the misconception remains common, but it should be classified correctly: it was a clarification from a Google representative, not a newly announced ranking system or Search policy.

This distinction matters. A social clarification can help explain Google’s position, but it should not be presented as evidence that Google changed how it ranks domains in June 2026. The documented answer predates that post.

Do Not Confuse a Domain Name with a URL Path

One reason this topic becomes muddled is that Google does recommend hyphens in another context. Its URL structure documentation recommends using hyphens rather than underscores to separate words in URLs because the separation makes concepts easier for users and search engines to identify.

That recommendation applies to readable URL construction, such as:

example.com/summer-clothing/

It does not mean that a domain such as summer-clothing.com receives a ranking advantage over summerclothing.com.

The two decisions operate at different levels. Page-path hyphens are a documented formatting recommendation. A hyphen inside the registered domain is primarily a naming decision once the misconception about a direct ranking penalty has been removed.

A Keyword-Rich Hyphenated Domain Is Not an SEO Shortcut

The opposite misconception also needs correcting. If hyphens are not penalised, that does not mean separating several keywords with hyphens is a useful ranking strategy.

Google’s SEO Starter Guide says that keywords in a domain name or URL path alone have hardly any ranking effect. When choosing a site name, Google recommends doing what makes sense for the business rather than treating the domain as a keyword-ranking device.

Google also documents an exact match domain system designed to prevent domains that closely match a query from receiving too much ranking credit merely because of the words in the domain.

So neither side of the old argument is particularly useful. A hyphen does not create an automatic penalty, and inserting more search terms into a hyphenated domain does not create an automatic advantage.

When a Hyphenated Domain Can Be a Reasonable Choice

For a new site, I would evaluate the hyphen only after checking whether the domain works without SEO mythology attached to it. A hyphen can be reasonable when it makes two words substantially easier to distinguish, matches the established brand spelling, or provides the clearest available domain without creating confusion with another organisation.

The important questions are practical:

Reading: Does the hyphen clarify the name or interrupt it?
Speech: Can someone say the domain aloud without having to explain repeatedly where the hyphen appears?
Typing: Is the address reasonably easy to enter on mobile and desktop?
Email: Will email addresses using the domain remain easy to communicate and verify?
Brand conflict: Does the non-hyphenated version belong to another active business that users could confuse with yours?
Expansion: Does the name still work if the organisation adds products, markets, or topics later?

None of these is a Google ranking factor. They are reasons to judge the domain as part of the wider business rather than as a single SEO field.

When I Would Prefer the Non-Hyphenated Version

If both versions are genuinely available, legally safe, affordable, and equally clear, I would normally prefer the simpler version. Not because Google rewards the missing hyphen, but because every extra element in a brand address has to justify itself.

The difference becomes more important when people are expected to remember the domain from speech, advertising, events, packaging, podcasts, video, sales calls, or email. In those situations, the domain has a job outside Search.

A hyphen can also become awkward when the unhyphenated version belongs to a competitor or an unrelated company with a similar name. The problem is not an algorithmic penalty. The problem is that the business may continually need to clarify which domain belongs to it.

This is why a domain-selection discussion should include brand, legal, communication, security, and market teams where those functions are relevant. SEO can rule out the false penalty claim, but it cannot make the complete naming decision alone.

Do Not Migrate an Existing Site Just to Remove a Hyphen

This is the most important distinction for an established website. If the current hyphenated domain is already indexed, linked, recognised by customers, used in email, and integrated into company systems, the question is no longer simply which name looks cleaner. It is whether the benefits of a domain migration justify the migration itself.

Google supports domain changes, but its site-move documentation treats them as real technical projects. A migration requires URL mapping, permanent redirects, updated internal references, testing, monitoring, and time for Search systems to process the move.

Google has also advised keeping an existing domain where possible. That does not mean domains should never change. Rebranding, trademark issues, mergers, international strategy, a confusing name, or a serious business problem can make a move worthwhile. Removing a hyphen because someone believes Google penalises it is not a sound reason, because the premise itself is wrong.

Situation	Likely decision	Why
New project, both versions available	Compare brand and usability, with a preference for simplicity when all else is equal.	There is no ranking penalty to solve, so the naming decision can focus on the business.
New project, only the hyphenated version is practical	Use it if the name is clear and there is no confusing brand conflict.	The hyphen itself is not a Google ranking problem.
Established hyphenated site performing normally	Keep the domain unless another business reason justifies a move.	A migration creates work and risk without fixing a confirmed SEO penalty.
Existing domain conflicts with a rebrand, trademark, merger, or market strategy	Assess a migration as a wider business and technical project.	The justification comes from the business change, not from punctuation.
Keyword-heavy domain with several hyphens chosen mainly to rank	Reconsider the naming strategy before launch.	Google says keywords in the domain alone have little ranking impact, and exact-match domains do not receive unlimited credit.

The Domain Check I Would Run Before Making the Decision

For a new domain, the order of checks matters more than a universal rule about punctuation.

Check the brand first. Confirm the name is appropriate for the organisation and does not create an obvious conflict with an existing brand.
Compare the actual alternatives. Do not compare a good hyphenated name with an imaginary perfect domain that is unavailable.
Test communication. Read the domain aloud, type it on a phone, put it in an email address, and check whether people remember the separator.
Check market and language fit. Evaluate how the words, script, transliteration, and punctuation work for the audience that will actually use the address.
Remove ranking myths from the decision. Do not reject a usable domain because of a penalty Google has said does not exist, and do not select a keyword-heavy domain because you expect the words in it to create rankings.
If the site already exists, assess migration separately. Domain selection for a new site and changing the domain of an established site are different risk decisions.

The useful conclusion is narrower than the old SEO rule: hyphenated domain names are not inherently bad for Google rankings. Once that misconception is removed, choose the domain that best fits the brand and its users. If the site already has history, do not turn a punctuation preference into a migration project without a stronger reason.