A redesigned website can look dramatically better and perform worse in organic search. The problem is rarely the new colours or typography. It is what disappears underneath the redesign, from established content and internal links to indexed URLs that other websites already reference.
For an established business, website migration SEO should begin before development is complete. Fixing a broken launch after traffic has fallen is much harder than preserving proven assets throughout the process.
The costly mistake is treating an established site like a blank canvas
Developers naturally focus on design systems, speed, mobile layouts and cleaner code. Those priorities matter, but an existing website also contains years of accumulated search signals. Page text, URLs, topical coverage and links may all support visibility for valuable searches.
At Lead Experts, founder Vaibhav Kandpal has repeatedly seen aesthetic priorities overtake SEO considerations during redesign projects. His strongest recommendation is to preserve existing text-based content and URL relationships whenever they still serve a purpose. New material can be added where it improves the page, but large unreviewed deletions can change the meaning of the page for both users and search systems.
A redesign is also different from a domain migration. Moving to a new domain changes the URLs across the site and requires extra mapping and monitoring, even if the design stays the same.
Create a reliable record of the existing website
Before changes go live, separate the production website from a staging version that the team can review. Protect the staging site from unintended indexing while ensuring reviewers and crawlers can inspect it.
Crawl the current live site with a tool such as Screaming Frog. Export URLs, response codes, canonical tags, indexability, titles, meta descriptions, headings, internal links and other relevant fields. Save the current XML sitemaps and a list of the pages attracting organic traffic and backlinks.
This baseline becomes the reference for spotting unintended changes. Without it, teams may not even know which pages disappeared when the new site launches.
Compare staging with live, page by page
Next crawl the staging environment. Find pages whose paths, canonical URLs, headings or titles changed. Check whether important text has been shortened or removed and whether navigation still leads to commercially valuable pages.
An AI-assisted comparison can highlight large text differences, but it should not decide automatically whether those differences are beneficial or harmful. The SEO team needs to understand why the original content performed, whether the replacement satisfies the same intent and what has been lost.
Kandpal’s workflow includes preparing a missing-keyword and phrase report for later editorial review. This is best treated as a coverage check, not as an instruction to reproduce a particular keyword density. Search intent and relevance matter more than an arbitrary repetition target.
Build redirect mapping before launch
Whenever a URL must change, map its old address to the most appropriate new destination. Closely corresponding pages generally need direct permanent server-side redirects rather than generic redirection to the homepage.
For a domain move, Google recommends preparing URL mapping, testing the new site, configuring redirects and monitoring both old and new properties. The Change of Address tool may be relevant to eligible domain moves, but it is not a replacement for correct redirects or page-level preparation.
Check important inbound links and high-traffic URLs especially carefully. A useful guide linked from another website should not unexpectedly become a 404 or redirect to an unrelated sales page. Preserve internal links and update canonical references, XML sitemaps and structured data to reflect the intended final URLs.
Test technical SEO without mistaking every warning for a crisis
Review indexing directives, robots rules, canonical signals, schema, pagination where applicable, broken links, mobile usability and important templates. Confirm that forms and calls work on the staging version as well.
Technical audits can also surface issues such as unused scripts, image formats or code minification. Prioritize them against observed performance and business impact. An automated score should not override the more fundamental need to preserve accessible, useful pages.
Avoid using robots.txt as the only method for protecting sensitive staging environments. Authentication or appropriate access controls are often better because blocked pages can still be discovered through external links.
Launch with an accountable migration checklist
A controlled release should include coordination between SEO, development, content and business owners. Verify redirect rules on production, site availability, canonical tags, metadata, tracking tags, Search Console verification, sitemaps and lead forms.
Google advises caution about changing many major elements at once. Where practical, splitting a domain move, CMS change and full design overhaul reduces the number of unknowns if something goes wrong.
Immediately after launch, crawl the new production website again. Compare it against both staging and the original baseline. Test old URLs in a browser or crawler to confirm that redirects resolve correctly and do not chain unnecessarily. Inspect the pages that generated the most leads or search visibility before the migration.
What should be monitored after the migration?
Watch indexing, crawl errors, Search Console impressions and clicks, high-value keyword groups, organic landing pages and actual inquiries. Investigate meaningful deviations while allowing for normal processing and reindexing time.
Do not mistake a day of volatile rankings for proof that the entire redesign failed. At the same time, avoid waiting weeks to investigate important redirect or noindex errors that can be fixed immediately.
When content was intentionally improved, compare the page’s coverage and business value rather than expecting every old term to remain untouched. A successful migration preserves relevant equity while allowing the site to evolve.
Website redesign SEO requires shared responsibility
A migration can require development work beyond ordinary monthly SEO maintenance. The SEO team should define what needs protection and review the implementation, while developers and stakeholders need to budget for necessary technical changes.
The strongest SEO consulting and implementation engagement is one where each team understands what it owns before the go-live date. For an established website, the real goal is not to preserve every line of old code. It is to protect search value, retain useful content and give the redesigned site a stable foundation for growth.
Research references
Google Search Central: Site moves with URL changes
Google Search Central: Debugging drops in Search traffic
Reddit SEO discussion: A difficult domain migration
