The quick answer
What should you protect first?
Keep the addresses of important pages wherever possible. If a page has to move, give it a direct permanent redirect to the closest replacement. Preserve the content that answers the original question, update internal links and test real enquiries before launch. A redesign can still cause temporary changes in search visibility, even with a careful migration.
Make a list of pages that already work for you
Combine your sitemap, Search Console landing-page data and the URLs customers or partners use. Add pages that produce enquiries, pages linked from your Google Business Profile, case-study links in proposals and old URLs listed on other websites. Include downloadable files and important images if they have public links. Record what each page helps someone do, alongside its title and traffic. A low-traffic quote page can still be commercially important.
| Existing address | Planned action | What to test |
|---|---|---|
| /website-design | Keep the URL and improve the layout | Existing links still work and the enquiry path completes |
| /our-services/websites | Redirect to the main website service | Old address permanently redirects in one step |
| /seasonal-offer-2024 | Retire if no meaningful replacement exists | Correct unavailable response rather than a misleading homepage redirect |
| Profile website link | Keep or update to the right landing page | A phone visitor reaches the correct location or service |
Preserve the useful content and the route to it
A new layout can keep the same search intent and enquiry journey. Compare old and new headings, pricing context, examples, location information and actions. If you merge several pages, make sure the destination still answers the questions that justified their separate URLs. Update your own menus, article links and image references to point directly to the final addresses. Ask the developer how the new canonical URL and sitemap will be set.
Build and check the redirect map
Use an individual mapping for valuable pages and a pattern only when the old and new structures actually match. Avoid chaining old paths through intermediate URLs. Test the status code and final destination for samples from every group. Wix documents its URL Redirect Manager, including cases where redirects need to be entered manually. Test the behaviour on the published URL because an editor preview may not have the same redirects.
Rehearse launch using real tasks
Have a colleague find a service, enter a valid test enquiry in an approved test environment, open the contact details and check the confirmation. Repeat on mobile. Compare key pages with their old versions for titles, descriptions, headings, visible content and internal links. Keep preview indexing restrictions until release, then check that the public pages are discoverable. Confirm the public sitemap contains the final addresses. Google offers a migration checklist and recommends monitoring the old and new URLs.
Give one person ownership of the first two weeks
Save a dated baseline with Search Console pages and queries, inbound leads and any known errors. On launch day check the highest-value URLs and conversions. Over the next weeks look at indexing signals, changed URLs, broken links and enquiry quality alongside traffic. If a specific page drops, inspect that page before changing the whole site. A short-term fluctuation on its own is a poor reason to reverse the redesign.
Common questions
Do I have to change URLs for a new design?
Usually not. Keep a working URL when the page still serves the same purpose.
Should all old URLs redirect to the homepage?
Use the closest useful replacement. Leave genuinely retired content unavailable when a relevant equivalent does not exist.
Does a permanent redirect guarantee the same position?
No. It helps people and search engines reach the successor, while visibility also depends on the new content and site.



