Should you keep old URLs or redesign URL structure in a migration?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 51
Keep them unless the new structure fixes a real problem. Every URL you change needs a redirect, a recrawl and a period while Google moves its signals to the new address, and Google’s site-move guide says to expect temporary ranking fluctuation while that happens. A cleaner-looking path is not a reason to pay that cost on pages that already rank. A structure that blocks growth, breaks the site’s hierarchy or mixes unrelated content can be.
Change or keep, URL by URL
| Situation | Keep or change |
|---|---|
| The URL ranks, has links and describes the page well enough | Keep |
| The URL is ugly but works (dates, IDs, an old category name) | Keep; the gain is cosmetic |
| The path puts pages under the wrong section, and the site is being reorganized | Change, with a redirect for each URL |
| Duplicate URL versions exist (parameters, mixed case, trailing slashes) | Pick one version and redirect or canonicalize the others |
| A section is being merged or split | Change, mapping each old URL to the page that now covers its content |
| The domain or protocol is changing anyway | Keep the paths the same, so only one part of the URL changes |
The last row is a practical way to limit risk: if the move already changes the domain, keeping the paths identical makes the redirect map a one-to-one rule and makes errors easy to spot.
If you do change the structure
Google’s guide to moving a site with URL changes asks for a complete mapping of old to new URLs before the move, and for updating internal links on the new site to point at the new URLs rather than relying on redirects. Build the map from every source of old URLs you have, test it on staging, and recheck it after launch. Once the map is live, the question becomes how long the redirects stay; how long old redirects should stay live after a migration answers it.
Decide with a short list
Write down each URL change you are considering and the problem it solves. Any change whose only justification is that the new URL looks neater should come off the list. What remains is the set of changes worth the redirect work, and keeping that set small is the simplest protection a migration has.
Add a comment