A title change does not always require a new slug. Keep an accurate old URL; when it becomes misleading, redirect it directly to the new canonical address.
The useful answer depends on the purpose of the page, the people allowed to edit it and the cost of an error. A reliable workflow separates editorial decisions, technical delivery and final verification instead of hiding all three inside one automated operation.
The decision to make first
Editorial title quality and technical URL stability are different concerns. Change the URL only when the benefit exceeds migration cost.
A practical method
- Inventory old URLs before editing.
- Choose one final target URL.
- Add a direct 301 without a chain.
- Update internal links, canonical, sitemap and hreflang.
- Keep the rule while the old URL receives requests.
Checks before publishing
- The source of truth is explicit and can be restored.
- URLs, dates and visible claims match the delivered page.
- A human reviewer can reproduce the check without a hidden service.
The main pitfall
Deleting the old page or redirecting everything to a generic category loses context and harms users.
Recommended next step
Maintain slug history by immutable article ID so each rename creates the correct redirect.
Verification workshop: evidence before a decision
A proposed exercise on a chosen scope, using fictional data where needed. Record what you observe; this scenario describes no test already performed on your website.
- Action to try
Change an article title in a working copy without changing its URL. Then decide whether a new address is actually needed.
- Record to retain
Keep old and new titles, retained URL and checked incoming links. If the address changes, map it to equivalent content.
- What this evidence does not establish
A new title does not require a new slug. Redirecting to a generic page does not automatically preserve the expected answer.
Decide what follows a title change
An article about preparing images receives a clearer title but still answers the same question. Keeping its URL avoids needless migration. If the address must change, the old URL should lead directly to the equivalent new page.
Update internal links, canonical and sitemap, then test the redirect and translated version where present. Avoid a new redirect chain with every title change. A page retired without an equivalent needs a different decision from a simple rename.
