How to Redesign Without Losing SEO: The 301 Map + Schema Migration Playbook

№ 01The 301 map: the artifact that prevents 90% of SEO loss

The 301 map is a CSV with three columns: old_url, new_url, http_status. Every URL Google has indexed on the existing site goes in column A. The exact destination URL on the new site goes in column B. 301 goes in column C unless the page is genuinely dead (then 410).

You build the map by exporting every indexed URL from Google Search Console (Pages report, 16-month range), every URL with traffic from GA4 (last 12 months, any sessions), and every URL with backlinks from Ahrefs or Semrush. De-dupe. That’s the master list. Every entry gets a destination before launch — not after.

№ 02The dip-and-recover curve, plotted

On a well-executed migration, the SERP curve looks like this:

• Days 0-3: Flat. Google hasn’t recrawled yet.
• Days 4-10: 2-3 spot dip on primary keywords. This is normal — Google is reprocessing signals.
• Days 11-21: Rankings start climbing back. Most pages back within 1 spot of baseline.
• Days 22-56: Surpass baseline on most pages. The new IA and improved CWV start outranking the old version.

If you don’t see this curve — if rankings stay 4+ spots down after week 3 — you have a broken 301, a missing schema block, or a server-side render problem. Diagnose in that order.

№ 03Schema markup migration: the silent killer

Schema (JSON-LD) is the second-most-common SEO loss vector. The existing site probably has LocalBusiness, Service, BreadcrumbList, and FAQPage schema. The new site needs all of it, ported and updated.

The pre-launch audit: run every important page through Google’s Rich Results Test on staging. Compare to the production site’s schema. Any block that exists on production but not on staging is a regression — fix before launch. Missing FAQ schema alone can cost you the snippet on 15-20% of long-tail queries.

№ 04The week-of-launch SEO checklist

Run all of these the morning of launch, in order:

1. Submit the new XML sitemap in Google Search Console.
2. Submit a Change of Address request if the domain changed (rarely, but if so).
3. Verify robots.txt allows crawling (the #1 launch-day mistake is leaving staging’s Disallow: / live).
4. Spot-check 20 random 301s with curl -I. Every one should return 301, not 302.
5. Verify Google Tag Manager, GA4, and Search Console are firing on the new site.
6. Check canonical tags on the top 50 pages. Each should self-canonicalize.
7. Submit the top 50 URLs through the Search Console URL Inspection tool for priority recrawl.

№ 05What WebFX and Blue Corona won’t tell you about migration risk

National agencies bundle redesigns into bigger retainer engagements, which means the 301 mapping is often handed to a junior on the SEO team after the design team has already launched. By then the indexing damage is locked in.

The way we run it: the senior dev who builds the new theme also owns the 301 map. They wrote the new URLs; they know which old URL maps where. Migration is a build-team responsibility, not an after-the-fact SEO patch. That’s the difference between an 87% surpass-baseline rate and a 50% one.

⚠What to avoid

• Letting the agency tell you ‘we’ll handle redirects at launch.’ Translation: they haven’t built the map yet. Demand to see the CSV at the end of week 1.
• Trusting a plugin to auto-redirect old URLs. Plugins like Redirection or Yoast Premium handle simple cases. They don’t catch URL-parameter variations, mixed-case duplicates, or trailing-slash mismatches. Build the map by hand.
• Launching on a Friday. Google’s recrawl cycle is faster mid-week. Friday launches mean Saturday and Sunday with no eyes on Search Console while the dip is forming.

Related questions

• Will My Google Rankings Drop After a Redesign?
• How Do 301 Redirects Work?
• What Happens to My Existing Traffic?

Go deeper

• Staging, QA, and Launch: Avoid a Friday Disaster
• Website Redesign Process: 14 Days
• Information Architecture for Redesigns