Practical guide
Website redesign SEO checklist
Before a redesign, record current URLs, rankings and links; map redirects; test on staging; and monitor closely after launch.
The work to plan together
A scope shaped around this requirement.
- Crawl and save current URLsScope
- Map every old URL to a newReview
- Keep important contentCheck
The useful starting point
Record the current website before design decisions remove its useful parts. Save priority URLs, search data and links, then agree which content stays and how changed URLs are mapped. Test the new website before launch.
What to review
- Crawl and save current URLs
- Map every old URL to a new one
- Keep important content
- Test on staging
- Monitor after launch
A practical sequence to follow
Inventory the current site
Save existing URLs, important pages and available search or enquiry evidence. Identify content worth retaining and pages being intentionally removed. A visual sitemap alone does not show which URLs already help people find the business.
Map each move
Assign an appropriate destination to each URL that changes. Preserve useful content where its purpose remains. Do not send every removed page to the homepage: the destination should explain the same or a closely related need.
Check staging journeys
Review headings, canonical URLs, navigation, images and contact paths on staging. Verify that public launch pages will be crawlable and that temporary staging restrictions will be removed. Keep private data and test submissions controlled.
Review after release
Test representative old URLs, the new sitemap and real enquiry journeys after launch. Compare indexing and performance with the saved baseline, allowing for seasonality and normal variation. Investigate errors rather than treating a new design as proof of improvement.
What to avoid or interpret carefully
A checklist reduces risk but cannot guarantee unchanged rankings. Monitor after launch and keep an accountable owner for fixes.
Practical detail
Review one service journey before launch
Use a representative page with known business importance to test the redesign’s content and technical route.
| Part of the work | Example output | How to review it |
|---|---|---|
| Inventory | Old URL, intended new URL and keep/change reason | Account for important existing content. |
| Page review | Title, main heading, service facts and next action | The new layout has not removed the useful explanation. |
| Functional review | Mobile navigation, enquiry, redirects and tracking | A polished screen is not accepted without a working journey. |
Assign the writer, developer and launch approver. Keep staging exclusions separate from the live indexing setup and review the deployed version after launch.
Approve preservation work before the new design goes live
A redesign checklist should identify what matters on the existing site and how the new build preserves or improves it. Useful URLs, content and contact journeys need deliberate decisions. Visual approval alone is not launch sign-off.
Inventory and mapping
Mark important pages to retain, improve, merge or retire. Give changed URLs relevant destinations. Do not redirect every removed article or service to the homepage by default.
Staging review
Check content, navigation and important template behaviour. Include redirects, canonical references and indexing controls in the release plan. Name the developer and approval owners.
Live validation
Test important destinations and contact paths after deployment. Keep recovery and monitoring responsibilities clear. Search changes need context and cannot be guaranteed away by a checklist.
How to interpret this guidance
Keep the checklist tied to evidence and the actual release. A completed document without live validation can miss a production-only problem.
Who signs off SEO checks during a redesign?
The nominated release owner should coordinate content and technical reviews. Each supplier needs explicit responsibilities. Sign-off should include the published journey and controls, not merely agreement on a design screenshot.
Does a redesign require new copy on every page?
No. Preserve accurate useful copy and improve identified gaps; changing wording for its own sake can discard clarity.
Can Tangensys help with the next step?
Yes. Share your website, goal and the issue you are investigating. We can discuss the relevant service and provide a custom quote within 2 working days.
Further reading
Consult the relevant platform documentation for current requirements: official documentation. Examples explain an approach; platform interfaces and policies can change.
Related reading and services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days