Information checked: 21 July 2026.
No redesign can promise unchanged rankings. The controllable goal is to preserve valuable URLs, content, internal relationships and technical signals while improving the site. Most avoidable losses come from unrecorded URL changes, missing content, blocked crawling, weak redirects or several major migrations launched at once.
In brief: Inventory the current site, change as little as the project requires, map every valuable old URL to its closest new equivalent, test redirects and monitor both versions after launch.
Build a baseline before changing anything
- Crawl all public URLs and save titles, headings, canonicals, status codes and internal links.
- Export Search Console performance and indexing data.
- Record landing-page enquiries, sales and other business outcomes.
- List external links to important pages where data is available.
- Save the current XML sitemap, robots.txt and redirect rules.
- Create a tested full backup and rollback plan.
Decide which changes are necessary
If a URL is clear and already performs, keeping it is safer than changing it for visual tidiness. When a change is necessary, prepare a one-to-one mapping from each old URL to the closest useful new page. Do not redirect every removed article to the homepage or a broad category that does not answer the old intent.
| Change | Preferred handling | Main risk |
|---|---|---|
| New visual design, same URL | Retain content purpose and metadata | Important text or links disappear |
| URL renamed | Permanent direct redirect to equivalent page | 404, chain or irrelevant destination |
| Several pages merged | Preserve useful sections and redirect each source | New page no longer satisfies old queries |
| Page genuinely removed | Return 404/410 unless a real replacement exists | Soft 404 from blanket homepage redirect |
| CMS, domain and design all changing | Split changes where practical | Diagnosis becomes difficult |
Test the new site while keeping it out of the index
Use access control for staging rather than relying only on robots.txt. Crawl the staging site and compare it with the approved URL map. Check canonical URLs, headings, metadata, structured data, mobile content, images, internal links, forms and HTTP status codes. Remove temporary noindex directives only as part of a controlled launch checklist.
Implement direct permanent redirects
Use server-side permanent redirects for genuinely moved URLs. Each old URL should resolve in one step to the final canonical page. Update internal links, navigation, canonicals and sitemap entries to the new URLs rather than depending on redirects indefinitely.
Launch and monitor
Google recommends preparing the new site, mapping URLs, configuring redirects and monitoring traffic on old and new URLs. For larger or riskier sites, changing one major element at a time can make problems easier to diagnose. After launch, monitor server logs, crawl errors, index coverage, performance by landing page and business conversions. Keep redirects in place for the long term.
Acceptance check
- Every valuable old URL has a documented outcome.
- Redirects are direct, permanent and point to relevant pages.
- Important content and internal links remain available on mobile.
- Canonical, sitemap and navigation use final URLs.
- Staging blocks have been removed from production.
- Search and conversion baselines are being monitored.
- A tested rollback exists for critical technical failure.
Next practical step
Do not approve a redesign launch until the old-to-new URL map, redirect test and content comparison have named owners and written evidence. Visual approval alone is not sufficient.
Sources and date checked
Migration and redirect guidance was checked against current primary Google documentation. Search performance can fluctuate during processing, so monitor actual results after launch. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.