How do I preserve SEO during a site migration?

A site migration, whether it's a redesign, a platform change, a rendering architecture change, or a domain change, puts existing search rankings at risk because search engines have indexed your current URLs, content, and structure, and a migration can change all three at once. The single biggest cause of lost rankings after a migration is broken or missing redirects: a URL that used to exist and ranked, now returns a 404 or redirects to an unrelated page, and the ranking history attached to that URL is effectively lost.

The first step, done before any development work, is a full inventory of every indexed and ranking URL on the current site, along with its traffic, rankings, and backlinks. This becomes the map for what needs to exist, in some form, on the new site. Every URL on that list needs a clear destination on the new site and a 301 redirect pointing to it. A redirect to the homepage or a generic category page when a specific match exists is a common shortcut that costs rankings.

Content and structure matter as much as the redirect map. If a page that used to rank for a specific topic gets thinner content, a different heading structure, or gets merged into a broader page that no longer targets that topic directly, rankings can drop even with a correct redirect in place. The safest approach is treating existing high-performing pages as a floor to match or exceed, not a template to casually rewrite.

Technical elements need to carry over deliberately: structured data (schema markup), canonical tags, internal linking patterns, XML sitemaps, and robots.txt rules. These are easy to lose in a rebuild because they live in configuration rather than visible content, and no one notices they're missing until rankings drop. If the migration includes a rendering architecture change, for example from a client-rendered setup to server-side rendering, verify that the new pages actually return full content in their initial HTML response, not just that they look right in a browser.

Timing and monitoring reduce risk further. Migrating in a low-traffic period, submitting the new sitemap to Google Search Console immediately at launch, and watching indexing status and rankings daily for the first few weeks lets you catch problems, like an accidentally noindexed section or a broken redirect pattern, before they cause lasting damage. Some ranking fluctuation immediately after a migration is normal; a sustained drop that doesn't recover within a few weeks usually points to a specific, fixable technical issue.

There's no version of a migration with zero risk. Search engines have to recrawl and reprocess the entire site, and that process takes time even when everything is done correctly. The realistic goal is minimizing avoidable losses through redirect mapping, content parity, and technical carryover, then monitoring closely enough to catch and fix the issues that do come up quickly.