A redesign does not need to change every URL to improve a website. Before a migration, record what exists, decide what genuinely needs to move, and check the new site against that plan. The checklist below focuses on reducing avoidable disruption to useful pages.
Record Existing URLs and Search Performance
Export important URLs from your site, sitemap, analytics, and Search Console. Note the pages receiving relevant traffic or links and capture their purpose, titles, and content. This baseline helps you protect useful material and identify what needs extra checking after launch.
- List current URLs and page roles.
- Record existing organic visibility.
- Keep a copy of important page content.
Map Only the URLs That Need to Change
Keep an established URL when the page can continue serving the same need. When a URL must change, map it to the closest relevant replacement and plan a permanent server-side redirect. Avoid sending unrelated deleted pages to the homepage simply to eliminate error reports.
- Map old URL to final destination.
- Check that the replacement answers the same need.
- Plan appropriate handling for genuinely removed content.
Check Content, Metadata, and Internal Links
A new design can accidentally omit headings, copy, or links that helped visitors understand the old page. Review the important content and search intent before approving the replacement. Update internal links and canonical information to the intended URLs, including links in menus and reusable components.
- Compare priority pages side by side.
- Check titles, descriptions, and H1s.
- Verify important child pages still have relevant links.
Test the Release Before Going Live
Use the staging or preview site to check the new routes, forms, mobile layout, and redirects. Keep preview pages out of indexing, then explicitly check that production will have the correct indexing instructions. A successful visual review does not replace route and form testing.
- Check page status and canonical URLs.
- Test form confirmation and delivery.
- Confirm tracking and verification tags remain present.
Monitor the New Site After Launch
Check that the intended URLs are accessible and the sitemap reflects the live structure. Review Search Console, analytics, and error reports for unexpected issues, comparing the affected pages with your baseline. Some visibility fluctuation can occur after substantial changes, so investigate evidence before making another broad change.
- Inspect priority URLs after release.
- Check old-to-new redirects where required.
- Record the release date and investigate unexplained losses.