SEO Migration Planning: How to Redesign a Website Without Losing Rankings

The Risk No One Talks About Until It’s Too Late

A Texas business spends three years building organic search rankings. Traffic is steady. Leads are coming in. Then they commission a redesign, launch the new site without a proper SEO migration, and watch rankings crater over the following six weeks. It happens more often than most web design agencies will admit, and it’s almost always preventable.

The cause is usually one of three things: changed URLs without 301 redirects, missing or altered metadata, or lost internal link architecture. Any one of these can cause significant ranking losses. All three together can reset a domain to near zero for its best search terms.

This isn’t a theoretical risk. Google has to re-crawl and re-index your site after a redesign. When it encounters broken redirect chains, missing pages, or restructured content, it re-evaluates what your site is about and how much to trust it. A migration plan ensures that re-evaluation works in your favor instead of against you.

Pre-Launch: The Crawl and URL Mapping Phase

Before a single new design file opens, crawl the existing site with a tool like Screaming Frog or Sitebulb. Export every URL on the live site — pages, images, PDFs, anything that returns a 200 status. This becomes your migration map.

For each URL, document:

• The current URL path
• The page title and meta description
• The H1 and primary content topic
• Inbound links from other pages on the site
• Google Search Console impressions and clicks from the past ninety days

Pages that drive traffic or rankings deserve extra care in the migration. Pages that are orphaned or have zero search visibility may be good candidates for consolidation or retirement — but even retiring a page requires a plan if any external links point to it.

301 Redirect Mapping

If any URLs are changing in the redesign — and in most redesigns, some will — every changed URL needs a 301 redirect pointing from the old path to the new one. A 301 passes the ranking equity of the old URL to the new one. Without it, that equity evaporates.

Build the redirect map as a spreadsheet: old URL in column A, new URL in column B. Map every URL on your crawl list, even pages you think don’t matter. A forgotten orphan page may be the one that has a valuable external backlink you didn’t know about.

Test every redirect before launch. A redirect chain — where URL A redirects to URL B which redirects to URL C — loses equity at each hop. Chains longer than two hops are worth fixing to direct single redirects. And never redirect all old URLs to the homepage as a shortcut. That signals to Google that the old content is gone, not moved.

Metadata Preservation

In the excitement of a redesign, it’s easy to let metadata slip. A CMS migration that doesn’t carry over title tags and meta descriptions isn’t just an SEO problem — it means you’re launching without the on-page signals that Google used to rank your old pages.

Export all existing title tags and meta descriptions from your crawl or from your current CMS. Import them as defaults into the new CMS before launch. Then review them — a redesign is a good opportunity to improve weak metadata, but the baseline should be preserved, not erased.

Also check canonical tags, robots.txt, and XML sitemap settings. A staging site that was blocked from crawling (common and correct during development) must be unblocked before launch. Missing this step is one of the most common causes of post-launch ranking loss.

Schema and Structured Data Validation

If your existing site has LocalBusiness schema, service schema, or review markup, verify it carries over to the new site and validates correctly. Schema tells Google what type of business you are and where you’re located — losing it during a migration is losing a trust signal. Use Google’s Rich Results Test on key pages of the staging site before launch.

Post-Launch Monitoring: The 30/60/90-Day Protocol

Launch day is not the end of migration work — it’s the beginning of a monitoring period.

Days 1 to 7: Confirm the live site is crawlable, submit the new sitemap to Google Search Console, and run a spot-check crawl to catch any immediate redirect failures or missing pages.

Days 8 to 30: Monitor Google Search Console for crawl errors, coverage issues, and any drop in indexed pages. Watch organic traffic in Analytics daily. A 10 to 15 percent fluctuation is normal; a sustained 30 percent drop needs investigation immediately.

Days 31 to 60: Rankings for most terms should stabilize. Check target keyword positions for your most important service pages. Address any pages that lost significant ranking without an obvious explanation.

Days 61 to 90: Full ranking comparison to pre-launch baseline. Identify any URLs still generating 404 errors from external links and update redirects as needed.

A Redesign Is an SEO Opportunity, Not Just a Risk

Done well, a redesign with a thorough migration plan is an opportunity to fix structural SEO problems that existed in the old site, consolidate thin content, and improve the on-page signals that Google uses to rank your pages. The migration plan protects what you have. Good redesign architecture builds on it.

If you’re planning a website redesign and want to make sure your current rankings survive and improve through the transition, that’s exactly how we approach every build. Talk to us before the first design file opens — that’s when migration planning matters most.