VANKPA
The short answer
A redesign should account for the pages customers and search engines already use. Preserve valuable information, map changed URLs, and test the migration before launch. No process guarantees unchanged rankings, but a documented transition reduces avoidable broken links and lost context.
Inventory the old site
Collect existing URLs from the website, sitemap, analytics, and Search Console where available. Mark pages that receive useful traffic, earn links, or support sales. Record titles, important content, forms, and downloadable resources. Do not remove a page simply because it does not fit the new navigation; first understand what it contributes.
Map each meaningful change
For changed URLs, choose the closest relevant destination. Google advises against sending many unrelated old pages to the home page. Preserve a useful page when no equivalent exists, or make a deliberate retirement decision. Keep redirects direct rather than creating chains through several historic addresses.
Check the release carefully
Review canonical links, indexability, internal links, image paths, and sitemap entries. Confirm that staging restrictions are not carried into production. Test redirects with actual old URLs rather than reviewing only a spreadsheet. The person approving visual design may not be the person responsible for these technical checks; assign both roles.
Monitor after the move
Google notes that search visibility can fluctuate during a site move. Track missing-page errors, indexing, important landing pages, and inquiry delivery. Keep a record of launch changes so performance reviews have context. Google's guidance generally recommends keeping redirects for at least a year; retaining useful redirects longer can also serve visitors with old links.
When to take the next step
Start migration planning as soon as the redesign might change page addresses or information structure. Do not leave the URL map until release week. If the site already receives useful search traffic, include someone responsible for that evidence in design reviews so visual simplification does not accidentally remove valuable answers.
- AnalystInventories urls
- EditorMaps content
- DeveloperTests redirects
- OwnerReviews signals
Adapt these responsibilities to your team and project scope.
Before you start
- Map old URLs to relevant destinations.
- Verify production pages can be indexed.
- Keep a postlaunch issue log and owner.
Questions clients ask
Can a redesign guarantee no ranking loss?
No. Search visibility depends on many factors, and Google may need time to process changes.
Should every old page redirect home?
No. Relevant page-level destinations provide a more useful transition for visitors and search engines.
Sources & context
References checked October 6, 2026. The planning recommendations are VanKpa editorial guidance; individual project requirements vary.
Turn the question into a plan
Discuss your next step.
Bring your current setup and the requirements above to a project conversation.