Google’s October URL Guidance: How to Review Slugs Without Breaking Useful Pages

SEO Edge insights

Google’s October URL Guidance: How to Review Slugs Without Breaking Useful Pages

Review Google URL guidance without unnecessary migrations. Plan clear slugs, justified redirects and useful post-change checks for WordPress websites.

6 min readRead the guide

Google recorded an update to its URL structure documentation on 23 October 2026, clarifying guidance about separating words with hyphens and underscores. That is a useful prompt to review publishing habits, not a reason to rename every established page. A small business can cause more trouble through an unnecessary URL migration than it solves through tidier slugs. The useful decision is whether a proposed change improves clarity enough to justify its implementation and monitoring. This guide explains a conservative review process for existing WordPress websites and new articles, with the emphasis on maintaining useful destinations and measuring what actually happens.

Treat a documentation change as guidance, not a penalty notice

A documentation update does not establish that a particular website has been penalised or that its recent traffic decline was caused by punctuation. Begin with the actual affected page and query data. Identify whether clicks fell, impressions changed or a new mix of searches altered the average position. Keep those questions separate from the appearance of the address. A page can have a plain, readable URL and still answer the wrong question. Another page can have an imperfect legacy slug and continue to serve visitors well. Prioritise observed defects over cosmetic uniformity, and do not promise a ranking uplift from a punctuation edit.

Choose clear addresses for new content

For a new page, describe its principal subject in a short, understandable slug. Make the address useful to a person reading a link, rather than inserting every keyword variant. Decide the topic before the URL. If the proposed article overlaps an existing service page, resolve the purpose first; a different slug does not create a different intent. Avoid including a year unless the content genuinely needs a year-specific role and there is a plan to maintain it. Check the final address before publication, along with the title, canonical and navigation links, so the first public version is coherent.

Inventory an existing URL before changing it

Record the current destination, internal links, known external references and recent search performance. Note whether the page is included in a sitemap and whether it redirects already. Check the page's actual content, not only the historic title in a report. A renamed or consolidated page may still appear in older Search Console rows. That is not enough to establish that the live redirect failed. Review the current behaviour and the dates of the reporting window together. When the old address has a clear continuing purpose, preserving it is often the simplest implementation decision.

Write a migration decision before implementing one

If a change is justified, record the old address, intended replacement and reason for equivalence. The replacement should satisfy the same user need. Do not route unrelated articles to the homepage simply to remove an error from a report. Define which internal links, canonical references and sitemap entries need updating. Include a recovery plan and an owner for post-release checks. This short decision record prevents a tidy-looking change from becoming an undocumented chain of redirects. It also makes later investigation easier if the destination is changed again by a different editor.

Check the result as a visitor and a maintainer

After an authorised change, verify the original address reaches the intended final page and that the page is usable. Check visible headings, forms, links and mobile behaviour. Inspect the final canonical and indexability settings separately. Do not confuse a successful public response with confirmation of Google's selected canonical or index state; those require their own evidence. Update internal links to the final destination where appropriate instead of relying permanently on redirects. Record the result and time of verification. If any essential check fails, use the recovery plan rather than making another unrecorded change.

Measure the affected cohort, not a whole-site average

A URL change should be evaluated with the pages and queries it actually affects. Compare equivalent settled periods and note major content or design changes occurring at the same time. Small click counts are volatile, so report the absolute numbers alongside percentages. Do not declare success because impressions increased while the intended commercial queries lost visibility. Conversely, a worse overall average position can reflect exposure to additional lower-ranked searches rather than a uniform decline. Keep the test interpretable by changing only what is justified and retaining the original baseline and implementation notes.

A practical review checklist

Use a short release checklist for each approved URL change. Record the original address and the intended final page before implementation. Check the response from the original address, the final page's canonical and the relevant internal links afterward. Confirm that a visitor can still complete the intended enquiry or navigation task. Keep the result with the change record so a later editor does not mistake the old address for an unexplained defect.

When a change is not justified, record that decision too. A retained legacy URL can otherwise be repeatedly raised by different audits, generating the same discussion without improving the website. Distinguish an acceptable historical convention from an actual fault, such as an internal link pointing at a missing destination. Fix the fault that has evidence behind it. Avoid treating every difference from a preferred convention as a technical emergency.

For reporting, give the business owner a small set of meaningful measures: affected pages, verified implementation checks and later settled performance for relevant queries. Explain the limitations of small samples and overlapping changes. The most defensible improvement may initially be reduced maintenance ambiguity or a repaired navigation path rather than an immediate rise in clicks. That is still useful work, provided the report describes it accurately and does not present an expected benefit as an observed ranking result.

Consider a service company with a guide whose address contains underscores. The guide receives a small amount of useful traffic and is referenced from several service pages. An editor suggests changing the URL to match the newest publishing convention. First ask what problem the change solves for the reader. If the content is accurate, the address is understandable and there is no operational defect, document the decision to retain it. Apply the preferred convention to new content instead. That avoids creating migration work without a clear business benefit.Now consider a different page with an obsolete campaign address and content that has been consolidated into a genuinely equivalent guide. Map the old destination to the replacement, review the proposed redirect and update the relevant internal links. Check that the final guide answers the original question and does not simply promote a different service. Keep the old and new performance records together. A report containing historic impressions for the old page is expected to need interpretation; it is not by itself proof that another change is required.For your next editorial meeting, review three proposed article topics before reviewing their slugs. Give each topic a distinct reader question, an existing related service page and a reason it deserves its own URL. Then choose the address and prepare the metadata. This order keeps URL housekeeping in service of a useful content architecture. The goal is a website that remains understandable and maintainable, not a collection of addresses repeatedly renamed in pursuit of an unverified ranking benefit.

Source date: 23 October 2026. This article was prepared on 31 October 2026; the source development is dated separately.

Primary source: Official guidance and background.

Related services and practical resources

Contact SEO Edge Brisbane

SEO Agency Brisbane | Local & Technical SEO Services | SEOEdge

Local SEO reporting QA checklist: ten checks before you call the month

Your next step

Turn useful advice into a clear plan.

Tell us about your website and the customers you want to reach. We’ll help you identify where to focus.

Let’s talk about your site
Keep exploring

Choose your next step.

Explore SEO services

Understand the work behind local visibility, useful content and a stronger website.

See how we can help

More practical guides

Find clear explanations for your next search, website or marketing decision.

Browse all insights