Google has clarified its advice on separating words in website addresses, adding detail to a familiar technical SEO recommendation: use hyphens rather than underscores where possible.

The October 23, 2026 Search Central documentation update is relevant to developers and editors creating new URLs. It should not be mistaken for an announcement of a new ranking algorithm. Google Search Central documentation updates, October 23, 2026

What Changed in the Documentation

Google's update log says the revision clarifies word separation and brings the documentation into line with its “The Non-Canonical Cabinet” video series. Google Search Central documentation updates, October 23, 2026

The current URL guide recommends hyphens because they make word boundaries easier to identify. It explains that underscores have historically been associated with concepts that belong together, including names used in programming. The guide also encourages readable URLs and consistent handling of letter case. Google: URL Structure Best Practices

For example, a new page could use /marketing-automation-guide/ rather than /marketing_automation_guide/. That is an illustration of the naming convention, not a promise of a particular ranking result.

What Editors Should Do With New Pages

TechFullNews analysis: The easiest place to apply this clarification is the publishing workflow. Agree on a simple URL convention, make it the CMS default and let editors review the proposed slug before publication.

Keep the article title and URL separate. A title can use proper Title Case and punctuation while its slug remains short and consistent. Editors should not have to make a headline awkward just to produce a tidy address.

A useful CMS preview shows the final destination clearly. This is especially helpful when a website has categories and subcategories: an editor should know which parts of the address come from the category structure and which come from the article itself.

Do Not Turn a Naming Cleanup Into an Unplanned Migration

A business with established pages should first inventory the affected URLs. Record which pages attract visitors, which have internal links and which are used in campaigns, emails or printed material.

If a change is justified, treat it as a small migration project. Agree on the destination for each old address, prepare redirects and update the site's own links. Check that the article still opens correctly after the change rather than assuming the CMS has handled every reference.

The important editorial judgement is proportionality. A documentation clarification is a reason to review standards; it is not, by itself, a business case for rewriting every address on a working website.

Give One Person Ownership of the Convention

URL consistency can become difficult when editors, developers and marketing teams all create pages. Assign someone to maintain the convention and document the few cases where an exception is necessary.

For most publishing teams, a sensible immediate action is to use clear, hyphenated slugs for new pages and assess existing addresses separately. That keeps the response focused on an understandable publishing improvement rather than a hurried site-wide change.