Hyphens (The Standard Separator) vs Underscores (The Connector): which should you choose?

Yes, Google's core recommendation has not changed. While their algorithms have become significantly more sophisticated at understanding natural language and context, the hyphen remains the explicit signal for a word separator in a URL.

In my practice, I have observed that adhering to this standard reduces the risk of indexing errors. When you use hyphens, you are following a documented process that Google has supported for over a decade.

This consistency is vital for maintaining visibility in competitive, regulated markets where every technical detail contributes to the overall authority of the entity.

Using underscores is unlikely to cause a manual penalty or a total loss of rankings, but it can lead to suboptimal performance. The primary risk is that Google might not correctly identify the individual keywords within your URL.

If your URL is 'best_tax_attorney', there is a small but measurable risk that it won't be as strongly associated with the search term 'best tax attorney' as a hyphenated version would be. In the context of compounding authority, you want to eliminate these small technical hurdles. We prefer to use hyphens to ensure the system is as efficient as possible.

This depends on the existing authority of the pages. If the pages are already ranking well and have significant backlink profiles, the risk of a temporary dip during the redirect process might outweigh the benefits of the change.

However, for new content or pages that are underperforming, migrating to a hyphenated structure as part of a broader technical audit is often advisable. What I've found is that a clean, consistent URL structure is easier to manage and scale over time. If you do make the change, you must use 301 redirects to ensure no equity is lost.

AI search models and Large Language Models (LLMs) rely on tokenization to understand text. Hyphens are a clear signal to these models that the words are separate tokens. When an AI assistant like Google's SGE or an LLM like GPT-4 parses a URL to cite a source, the clarity provided by hyphens helps it accurately attribute the content to the correct keywords.

In a reviewable visibility framework, we ensure that every element of the page, including the URL, is optimized for these new search environments. Hyphens provide a cleaner, more reliable signal for these AI systems.

Underscores are better only in non SEO contexts. For example, if you are a developer managing internal API endpoints or database queries where the URL is never intended to be indexed by a search engine, underscores are a standard and acceptable choice.

They are also useful in URL parameters for tracking, such as 'utm_source' or 'campaign_id'. In these cases, the underscore helps distinguish the technical data from the content slug. For any part of the URL that you want a human to read or a search engine to index, hyphens are the superior choice.

Hyphens themselves do not significantly impact URL length more than underscores would, as both are single characters. However, the goal should always be to keep URLs concise and descriptive. In my experience, a URL that is too long can be truncated in search results, which reduces the click through rate.

Whether you use hyphens or underscores, the focus should be on including the most important keywords and removing unnecessary filler words. A hyphenated URL that is structured around a clear hierarchy is the most effective way to communicate the page's topic to both users and crawlers.