The new website looks better. The navigation is clearer, the service pages are stronger and the team is ready to announce it. Then an old proposal link opens a missing page.

A redesign changes more than what visitors see on the homepage. Existing URLs may be saved in bookmarks, emails, search results and customer documents. Plan what happens to those routes before replacing the old site.

Inventory the pages that already exist

Collect the current URLs and identify pages with important traffic, enquiries, links or business relevance. Include downloadable resources and campaign pages that may not appear in the main navigation.

For each URL, decide whether it stays, moves, combines with another page or is intentionally removed. Put the decision in a mapping document that someone can review. A list of old pages and their intended destinations is easier to test than a general instruction to “set up redirects.”

Match destinations to the original intent

An old service page should lead to the closest relevant replacement. Sending every retired URL to the homepage can leave people searching again for the information they expected.

Google's migration guidance describes redirecting old URLs to their new destinations as part of a site move. Choose the redirect behavior with your developer and verify the actual response. A rule that looks correct in configuration still needs testing against the deployed site.

Update the links you control

Navigation, page content, image references and canonical URLs should point to the intended locations. Avoid relying on redirects to repair every internal link. Update sitemap generation so it reflects the pages you want available.

Check contact forms, analytics configuration and verification settings during the same release review. A successful visual launch can hide a broken enquiry path if the team only reviews screenshots.

Keep a launch checklist with owners

Someone should verify the URL mappings. Someone should submit a real test enquiry. Someone should inspect important pages on a phone. Assign these checks explicitly and record the results.

Prepare a recovery plan proportionate to the change. Know how to restore a previous build and how to correct an individual redirect quickly. Keep the old URL inventory available after launch so problems can be traced.

Watch what happens afterward

Review missing-page reports, enquiry behavior and indexing signals over the following weeks. Search engines need time to process a move, so avoid treating launch-day appearance as the entire migration result.

  • Map old URLs before changing the route structure.
  • Test important redirects and direct page visits.
  • Verify forms, internal links and the generated sitemap.
  • Monitor unexpected missing pages after launch.

A redesign is ready when the new experience works and the useful routes into it still make sense. Detailed reference: Google Search Central's site-move guidance.