Website redesign SEO checklist before you relaunch
A redesign can improve the brand and destroy rankings at the same time if SEO migration is ignored. This checklist shows what to protect before launch so the new site can look better without losing search visibility.
Key takeaways
- Never change URLs without a redirect plan.
- Carry important titles, descriptions, headings and content intent into the new structure.
- Check analytics, indexing and performance before and after launch.
Senior planning brief
Use this as a project decision guide, not a generic blog post.
This guide is for businesses redesigning an existing website with search traffic or lead generation value. The goal is to help you turn a vague idea into a clearer scope, safer launch plan and better conversation with a developer.
Read it with a notes document open. Capture what is already clear, what still needs a decision and what should be part of the first release instead of becoming expensive rework later.
Map old URLs before design decisions go final
Every valuable URL needs a destination in the new site. Some pages should stay, some should merge and some should redirect. The map should be ready before launch day, not patched afterwards.
How to use this in the project
Use this section as a decision checkpoint, not just background reading. If the details here are unclear, pause the project conversation and clarify them before approving a quote.
- Export existing URLs
- Mark pages with organic traffic
- Plan one-to-one redirects where possible
Protect page intent
A page ranks because it satisfies a search intent. A redesign should improve clarity, not accidentally remove the content that made the page useful. Keep the core answer, then improve layout and conversion flow.
How to use this in the project
Ask the developer how this will be handled in the actual build. A strong answer should mention process, risks, tradeoffs and who owns the work after launch.
- Preserve strong headings
- Keep important FAQs
- Improve internal links
Test the technical basics
Before launch, verify metadata, canonicals, sitemap, robots rules, structured data, tracking, image weight, mobile layout and redirects. Small mistakes can create large SEO problems.
How to use this in the project
Turn these points into a short written requirement. Written requirements prevent design approvals from hiding operational problems that appear later.
- Crawl staging
- Check mobile rendering
- Confirm analytics events
Protect the pages that already earn trust
Not every old page deserves to survive, but pages with impressions, backlinks, conversions or strong topical value should be handled carefully. A redesign should improve these pages instead of replacing them with thinner, prettier versions.
How to use this in the project
Compare proposals against this section. The better proposal will usually explain what is included, what is excluded and what should wait for a later phase.
- Backlink review
- Conversion page review
- Content depth retained
Decision framework
What a serious buyer should check before moving forward
Decide first
- Old URL export complete
- Redirect map complete
- Titles and descriptions reviewed
- Canonical tags correct
Ask directly
- Never change URLs without a redirect plan.
- Carry important titles, descriptions, headings and content intent into the new structure.
- Check analytics, indexing and performance before and after launch.
Avoid this
- A price is promised before the scope, content, integrations and launch responsibility are understood.
- The proposal talks about visuals but ignores redirects, tracking, performance, forms, security or maintenance.
- There is no clear owner for QA, deployment, post-launch fixes and future improvements.
Before you request a quote
Send a cleaner brief and you will get a better answer.
Most weak proposals happen because the request is too thin. Before asking for pricing, collect the information below so the developer can estimate the real work instead of guessing.
- The main business goal and what should improve after launch.
- Current website, store or workflow problems with examples.
- Must-have pages, features, user roles and integrations.
- Content ownership, timeline pressure and budget range.
- Any SEO, analytics, hosting, access or maintenance constraints.
Practical answers before you commit
Yes. Rankings can drop when URLs, content, metadata, internal links or performance change without a migration plan.
Only when there is a clear reason. Valuable pages should be preserved, improved, merged or redirected carefully.
From the planning stage. Waiting until launch week usually creates avoidable ranking and tracking risks.