Part of the 20–26 October editorial series. Prepared and source-checked on 26 October 2026.
A naming recommendation is not a migration instruction
Use descriptive hyphen-separated words when creating new URLs. For an established page, first identify the problem a URL change would solve and the work required to preserve its entry points. A documentation clarification alone is a weak reason to rename a working archive.
Google's 23 October 2026 change-log entry says it clarified hyphens versus underscores in its URL structure guidance. That is a documentation update, not an announced ranking-system change. The useful business decision is whether changing a particular existing URL provides enough value to justify the migration and verification work.
Set a simple policy for new pages
Choose a slug that describes the page's subject in the audience's language. Separate words consistently and avoid adding a date or tool version unless it is part of the page's durable purpose. Apply the policy before creating internal links and preview assets.
Keep editorial judgment in the process. A short ambiguous slug can be less helpful than a slightly longer descriptive one. An AI assistant can suggest candidates and check them against existing routes, while a person confirms that the chosen URL describes the content readers will find. Do not turn a naming convention into a claim about guaranteed visibility.
Define the benefit for an existing URL
Inspect whether the current URL creates a real problem: confusing identity, an incorrect subject, a broken routing pattern or a planned consolidation. Changing underscores may be part of a justified wider move. It need not become a separate project simply because a best-practice page was refreshed.
Use a small decision record with current URL, proposed URL, reader benefit, dependencies, owner and verification plan. If the benefit cannot be described beyond following the newest advice, defer the move and use the improved convention for new content. This is my operational recommendation, not a quantitative estimate of search risk.
Map the paths that already lead to the page
Inventory navigation, related articles, service links, sitemaps, canonical references, structured data and downloadable materials that name the existing URL. Include external links you control and references you cannot update. A migration changes a destination that other people and systems may already use.
For a fictional consultancy, a service guide might be linked from proposal PDFs and partner pages. The new slug can look cleaner while creating avoidable maintenance work. That does not forbid the change. It makes the requirements visible before someone asks an automated editor to replace strings across the website.
Write the migration checks before authorising the move
If the move is worthwhile, define what should happen at both old and new URLs. Plan the redirect, the canonical destination and the discovery updates together. Record expected status codes, relevant page content and the URLs that need to remain reachable.
Run those checks in a local or staging environment before an authorised deployment. Then verify the public paths separately after deployment. A generated sitemap and a local HTTP success do not establish that the uploaded production files are complete. Keep a recovery plan suited to the change, especially when shared templates or rewrite rules are involved.
Keep the checkpoint proportionate to the change
After the move, review errors, indexing and relevant traffic evidence over an appropriate period. Avoid attributing every change to the separator: content, demand, seasonality and other site work can also differ. Preserve the original decision so later reviewers know what benefit was expected.
The SEO Engine case study describes a checkpoint discipline useful for this work. If you are planning a larger redesign, include URL policy in the web design scope. If you are simply adding an article this week, choose a descriptive hyphenated slug and put the remaining effort into a useful answer.
Link Map
Sources and editorial review
Sources checked on 26 October 2026. The publication date is assigned to the 20–26 October editorial series; this edition was prepared and reviewed on 26 October 2026. Proposed workflows and illustrative examples are JQ AI SYSTEMS editorial analysis, not reports of completed client tests.
- Google Search Central: URL structure best practices (23 October 2026; Official documentation clarified on this date).
- Google Search Central: Latest documentation updates (23 October 2026; Official dated changelog).