Website redesign SEO checklist: what to protect before you relaunch.
A redesign can improve clarity, credibility and conversion. It can also lose useful search signals when the transition is handled casually. This guide keeps the business, user experience and SEO migration in the same plan.
Start with the site that already exists.
Before changing pages, document what is working today. Review which URLs receive impressions or clicks, which pages generate enquiries, which content is still useful and which external links point to the site. Also confirm the forms, analytics events and conversion paths that must continue working after launch.
The goal is not to preserve everything. It is to avoid deleting value by accident.
Decide what stays, what moves and what can genuinely disappear.
When a URL already has value, keeping it is often the simplest choice. If it must change, map a permanent redirect to the closest relevant new page. Avoid sending every old URL to the homepage because that removes context for people and search engines.
If a page is being retired because there is no meaningful replacement, document the decision instead of improvising on launch day.
Protect the signals that explain what each page is about.
A visual redesign does not require removing useful titles, headings, content, internal links, canonical tags or language signals. If positioning changes, update those elements deliberately while keeping the purpose of every important URL clear.
For bilingual sites, also verify that English and Spanish versions still point to each other correctly and that each language has its own indexable URL.
Test the relaunch as both a user and a search engine.
Before publishing, validate response codes, canonicals, robots directives, noindex rules, sitemap entries, internal links, mobile navigation and redirects. A site can look perfect while sending contradictory technical signals.
Also test 404 pages, forms, thank you pages and any flow that depends on JavaScript or integrations.
Do not launch without knowing whether enquiries still arrive.
Confirm Analytics, Tag Manager, conversion events, UTMs and forms before switching the site. After launch, you need to distinguish between a traffic problem, an experience problem and a measurement problem.
When everything changes at once and there is no baseline, that distinction becomes much harder to make.
Monitor before drawing conclusions.
Review Search Console, indexing, 404 errors, important pages, queries and conversions during the weeks after launch. Google needs time to crawl and process changes, so early movement does not always represent the final outcome.
The priority is finding avoidable problems quickly and confirming that new pages are replacing old ones as intended.
Do not confuse redesign with a complete rebuild.
If the content, platform and structure still serve the business, a focused refresh may solve the problem with less risk. If the current system restricts navigation, performance, content or growth, a rebuild may be cleaner.
The better option is the one that solves the actual problem with the least unnecessary change.
Clarify the decision before expanding the scope.
Do I need to keep every old URL?
No. Keep or redirect the URLs that carry value or have a clear new equivalent. A URL with no meaningful purpose does not need to live forever.
Can a website redesign affect SEO?
Yes, especially when URLs, content, internal links or technical signals change. The risk is lower when the migration is planned and validated before launch.
Should I change platforms during a redesign?
Only when the current platform creates a real limitation. A technology change adds complexity and should solve a specific problem.
When is a migration finished?
Not on launch day. Continue monitoring indexing, traffic and conversions until the new behavior is stable and understood.
Planning a redesign and want to protect what already works?
We can review the current site, define the right scope and plan the transition before pages start moving.
TALK ABOUT THE REDESIGN →