In 14 years of doing this, the pattern is consistent: a business spends 18 months building organic traffic, hands the site to a designer, and three months after launch the traffic graph looks like a cliff. Not because anything was done maliciously. Because nobody thought about SEO during the redesign until it was too late.

A site migration or redesign is one of the highest-risk SEO events you can go through. It is also entirely manageable if you treat SEO as part of the project from day one instead of an afterthought at go-live.

Why Redesigns Kill Rankings

Rankings live in specific URLs. Google has indexed those pages, evaluated the content and authority signals pointing at them, and decided they deserve to rank. Those rankings are often a business’s most cost-effective traffic channel — one reason the comparison between SEO and social media consistently favors organic when a redesign is on the table. When you redesign without a plan, several things break that ranking equation simultaneously.

URL structures change. A page that lived at /services/seo-consulting/ now lives at /what-we-do/search-engine-optimization/, and the old URL returns a 404. Every link pointing at that old URL from external sites, every piece of Google authority built up over years — gone, unless you redirect it.

Content gets removed or thinned. Designers want clean pages. Clean pages often mean removing the detailed copy that was actually driving rankings. A 1,200-word service page gets redesigned into an 80-word layout with some icons. Rankings for the terms that page owned disappear within weeks.

Technical signals break. Canonical tags, hreflang, structured data, robots.txt, internal linking structures — these are invisible to designers and developers who are not thinking about SEO, and they frequently get broken in migrations.

The crawl budget gets wasted. If the new site structure is significantly different, Google has to re-crawl and re-evaluate everything. During that re-evaluation period, rankings often dip — and if redirects are missing or the new content is weaker, that dip becomes permanent.

The Pre-Redesign Audit You Cannot Skip

Before a single wireframe is designed, pull a complete picture of your current SEO state. This is the baseline you are protecting.

Export every URL on your current site, along with organic traffic data from Google Analytics and rankings data from your rank tracker. Identify which pages are actually driving traffic and conversions — not which pages you think matter, but which ones the data shows are performing. Often the pages that drive the most traffic are not the ones the business considers important.

Map every external link you have earned to its destination URL. Tools like Ahrefs or Semrush can pull this. Every URL that has inbound links is a URL you need to either preserve exactly or redirect perfectly.

Document your current technical setup: title tags, meta descriptions, canonical tags, structured data, robots.txt, sitemap. You will need this to verify the new site matches or improves on these.

What to Preserve and What You Can Change

The goal is to preserve the SEO signals while changing the design. Not all changes are equal risk.

High risk to change: URL structures for pages with organic traffic or inbound links. The main navigation hierarchy. The volume of content on high-performing pages. Internal link anchor text patterns that have built authority to specific pages.

Lower risk to change: Design, visual layout, colors, fonts. Template structure as long as content is preserved. Footer links and secondary navigation. Images and media (with proper alt text maintained).

Where I push back on clients: The instinct to clean everything up and start fresh. A blank slate feels good in a redesign meeting. It is a disaster for organic traffic. If the site genuinely is starting over, the guidance in SEO for a brand new website applies — but that is a different situation than migrating an existing content library. The content and URLs that have been earning authority for years are assets. Treat them that way.

Redirect Strategy: The Most Critical Piece

If any URLs are changing — and in most redesigns, some will — you need a complete redirect map before launch. Not after. Before.

Map every old URL to its new destination. 301 redirects for permanent moves. Every page with organic traffic or inbound links must be accounted for. Orphaned URLs that 404 are lost authority.

Redirect chains are a second problem. If URL A already redirects to URL B, and now URL B redirects to URL C, you have a three-step chain. Google will follow it, but it loses signal with each hop. Clean this up at migration time.

Test every redirect before launch. Not a sample — every one. Tools like Screaming Frog can crawl your redirect map and flag anything that does not resolve correctly. Do this on a staging environment before the new site goes live.

The Pre-Launch Checklist

The week before a migration launch, I go through the same checklist on every project:

  • All 301 redirects mapped and tested
  • Robots.txt verified — staging environment should have been blocked from indexing; production must not be
  • XML sitemap generated with all new URLs and submitted to Google Search Console
  • Canonical tags correctly implemented on every page template
  • Structured data validated for all page types that had it before
  • Internal links updated to new URL structure (not relying on redirects)
  • Page titles and meta descriptions migrated and verified
  • Analytics and conversion tracking verified on the new environment
  • Core Web Vitals measured on the new site before launch
  • Crawl of the new site on staging to surface any 404s, redirect errors, or missing pages

Skipping steps here is how you end up discovering a problem three weeks after launch when rankings have already dropped.

Post-Launch Monitoring

The launch is not the end of the process. The 30 days after a migration launch are when most problems surface.

Watch Google Search Console daily for crawl errors, indexing issues, and coverage drops. Compare organic traffic week-over-week and page-by-page against your pre-migration baseline. Set up alerts for any sharp traffic drops. If you see a page losing traffic significantly, check it immediately: does it exist at the right URL, does it redirect correctly, is the content intact, is it indexed?

Some ranking fluctuation after a migration is normal and expected. Google needs time to re-crawl and re-evaluate the new site. If traffic is down 10 to 20% for 2 to 4 weeks and then recovers, that is typical. If traffic is down 40% after 6 weeks and not recovering, something is broken — and you need to find it fast before the loss becomes permanent. A migration that goes badly is also a reasonable moment to apply the framework in when to fire your SEO — mismanaged migrations are one of the clearest signs a practitioner is out of their depth.

When to Bring SEO Into the Redesign Process

The answer is: at the same time you bring in the designer. Not after wireframes are done, not at QA, not two weeks before launch. Retrofitting SEO requirements into a design that is already built is expensive and often incomplete.

The SEO input at the design stage is mostly about information architecture, URL structure decisions, and making sure no high-value content is being removed or buried. That input takes a few hours in the early phase and can save months of recovery work later. Whether you bring in outside help or handle this internally, the post on DIY SEO vs hiring a consultant helps clarify where the break-even actually falls for a project like this.

If you are going into a redesign soon and want to make sure you come out the other side with your rankings intact, the SEO consulting page explains how I typically scope migration work.