A redesign changes more than appearance. Navigation, page addresses, headings and the content customers rely on can all move at once. The safest starting point is to understand what the existing site already does well, then carry that value into the new experience.
Inventory the pages before designing replacements
Export your current URLs and identify pages that receive search traffic, generate enquiries or explain important services. Include useful downloads and campaign landing pages. Save the current page titles and a copy of meaningful content so the team can compare old and new versions.
Give every important page a decision: keep it, improve it, merge it into a genuinely relevant page, or retire it. A shorter navigation menu does not automatically require deleting useful pages. Sometimes the right solution is simply a clearer information hierarchy.
Make a page-by-page migration map
If a URL changes, record its intended destination before launch. Google recommends permanent server-side redirects when moving URLs permanently. Match old pages to relevant new equivalents; sending every old address to the homepage loses the specific journey the visitor expected.
- Keep existing addresses where they still make sense.
- Map changed pages to their closest useful replacements.
- Update navigation and internal links to the final destinations.
- Check images, documents and enquiry links as well as pages.
- Give genuinely removed content an appropriate response rather than a misleading replacement.
Protect the meaning of each page
A visually cleaner page can still become less useful if it removes the details people need. Compare the old service page with its replacement: does the new one explain the same scope, answer key questions and preserve relevant evidence? Rewrite for clarity instead of keeping text simply because it contains a keyword.
Review the mobile version early. Long headings, hidden navigation and oversized media can change the journey substantially. Test the complete enquiry path with realistic information, not just the first screen of the homepage.
Use a launch checklist and monitor afterwards
Before release, test priority old URLs, redirects, page responses, titles, links and the intended indexing settings. Confirm staging restrictions have not accidentally carried over to the public site. Retain a record of the old site and agree who can fix urgent problems.
After launch, check priority pages in Search Console and monitor errors, traffic and qualified enquiries. Google notes that search visibility can fluctuate during a site move, so no migration plan can promise zero change. A documented map and clear monitoring make problems easier to identify and resolve.
Need a starting inventory? Follow the SEO audit checklist before setting the redesign scope.
Technical references: Google: site moves with URL changes.