Website Redesign SEO Checklist: Before and After Launch
Treat the existing URLs and customer pathways as part of the project.
A website redesign needs a migration plan as well as a design plan. Inventory existing pages, record search and inquiry baselines, map any changed URLs, preserve useful content and test the new site's indexing signals. Redirects and a sitemap help communicate changes, but no process can guarantee that search visibility never fluctuates.
At a glance
Before design
Inventory current URLs, content, search visibility and customer actions.
Before launch
Test redirects, metadata, canonicals, indexing rules and the actual forms.
After launch
Check HTTP responses, Search Console coverage and completed inquiries.
| Stage | Check | Evidence to save |
|---|---|---|
| Baseline | Existing pages and search/conversion performance | URL inventory and dated exports |
| Mapping | Each old URL kept or assigned a relevant destination | Redirect map with exceptions recorded |
| Preview | Readable content, titles, canonicals and indexing rules | Local build and crawl checks |
| Launch | Real page responses, redirects and form submissions | HTTP checks and controlled submission evidence |
| Monitoring | Indexing, broken links and inquiry changes | Search Console and analytics comparisons |
Inventory the current site
Record the pages that exist and which ones receive useful search traffic or inquiries. Include older pages that have incoming links even if they are absent from the main navigation.
A redesign should not delete a valuable service page because its old layout is inconvenient. Decide what to retain, improve or move, and record the reason for each change before the new design determines the information architecture.
Map changed URLs to relevant destinations
Keep a useful URL when possible. When a page moves permanently, redirect it to the closest relevant replacement. Sending unrelated retired pages to the homepage does not give the visitor an equivalent answer.
Test the map against the old URL list. Check for loops, chains and destinations that return errors. Google documents redirects and related technical work in its guidance for site moves with URL changes.
Inspect what search engines receive
Check the rendered page and the delivered HTML. Important service text and navigation should be present, each page should identify itself clearly, and canonicals should point to the intended production URL.
Preview environments need appropriate indexing controls. Before production launch, check that the intended public pages have not inherited a noindex rule or crawl restriction. Update the sitemap to the final indexable URLs and preserve intentional exclusions.
Test the inquiry path and monitor the change
A successful build does not prove the contact form delivers a lead. Test the submission, the receiving system and the success/error states with a controlled process. Analytics should record completed inquiries separately from clicks on a telephone or email link.
After launch, compare indexing, relevant queries and qualified inquiries with the baseline. Keep the redirect map and test evidence so an unexpected drop can be investigated against the actual changes rather than assumptions about the new design.
Frequently asked questions
Should every old page redirect to the homepage?
No. Keep useful pages or map a moved page to a relevant replacement. A generic homepage redirect may not satisfy the visitor's original request. Record intentional removals and check the resulting responses.
Does a redesign guarantee better rankings?
No. Better content and technical delivery can improve the site, but rankings depend on the wider search system and competition. Preserve a baseline and monitor indexing, queries and qualified inquiries after launch.