Website Redesign Without Losing SEO: The Migration Checklist We Run
The exact before, during, and after checklist we run on every rebuild, and the mistakes behind the typical 20–40% post-launch traffic drop.
The most expensive part of a website redesign is usually invisible on launch day. The new site looks right, loads fast, and everyone celebrates — and over the following three weeks, organic traffic slides 20, 30, sometimes 40 percent. By the time anyone connects the drop to the launch, the rankings that took years to earn have already been re-assigned.
It doesn't have to happen. Rankings don't attach to your design; they attach to URLs, content, and the signals around them. Preserve those through the move and you keep your positions. This post is the literal checklist we run on every rebuild, in the order we run it, the same process we used to migrate our own site with a one-to-one redirect map covering 212 legacy URLs.
Quick answer: A redesign only loses SEO when the migration is incomplete. A safe migration means: crawl and export every indexed URL, baseline current rankings and traffic, build a one-to-one redirect map, preserve title tags, meta descriptions and schema, test every redirect before cutover, resubmit sitemaps immediately, and monitor Search Console closely for 90 days.
Why redesigns lose rankings
Google doesn't rank your website; it ranks individual URLs. Each one carries its own history: content, links pointing at it, and a track record of satisfying searches. A redesign threatens that history in a handful of specific ways, and almost every post-launch traffic drop traces to one of them:
Where the traffic drop comes from
- URLs change without redirects. The old URL 404s and its history evaporates. The biggest cause: one audit of a failed migration found 163,000+ URLs with no redirect.
- Redirects map many-to-one. Fifty old pages pointed at the homepage tells Google the content is gone, not moved.
- Titles, headings, and schema rewritten wholesale. The copy refresh deletes the phrases pages ranked for.
- Content trimmed. "Redundant" sections were carrying long-tail rankings.
- URL structure and content changed at the same time. The cardinal error.
- Mechanical mistakes: a staging noindex carried to production, robots blocks, a slower template.
How bad does it get? Vendor studies put a normal post-launch dip at 5–15% for a few weeks; incomplete redirects commonly produce 30–40% drops; and one analysis of 892 migrations found 17% of sites never recovered their pre-migration traffic at all. The spread between a wobble and a disaster is almost entirely process.
The one rule that outranks the rest
Never change URL structure and content in the same release. When both change at once, Google has to re-evaluate everything simultaneously, and you lose the ability to diagnose what caused any drop. If the redesign requires new URLs, migrate the structure first with content as close to unchanged as possible, let rankings settle, then revise content in a second pass. One variable at a time.
The checklist
| Phase | Focus |
|---|---|
| 1 — Before | Inventory, baseline, and map, weeks ahead of launch |
| 2 — During | Preserve signals, test every redirect, launch in sequence |
| 3 — After | Watch Search Console like a hawk for 90 days |
Phase 1: Before the redesign starts
- Crawl the live site with a crawler like Screaming Frog and export every URL that exists.
- Export every URL Google actually knows about: Search Console (16 months of pages with impressions), Google Analytics landing pages, and every URL with external links from your backlink tool. The union of these lists is your migration inventory; it is always longer than the crawl alone.
- Baseline performance per URL: clicks, impressions, position, and conversions for the last 90 days. Without a baseline you can't tell a seasonal dip from a migration problem.
- Inventory on-page signals: title tag, meta description, H1, and structured data for every ranking page. These transfer as requirements, not suggestions.
- Build the one-to-one redirect map: every old URL and its exact new destination. Retired pages redirect to their closest surviving relative, never the homepage. This document is the migration.
- Freeze content changes: the map is only valid while both sides hold still.
Phase 2: During the build and at cutover
- Carry titles, metas, H1s, and schema over verbatim for every ranking page. Improvements come later, measured, one template at a time.
- Keep URL structure wherever possible. The cheapest redirect is the one you don't need.
- Test the redirect map against staging with a script before cutover: every row, not a sample. A redirect map that has never been executed is a hypothesis.
- Check staging for carried-over blockers: noindex tags, robots disallows, canonicals pointing at staging.
- Launch-day sequence: cut DNS, crawl the live site immediately, hand-check the top-traffic redirects, resubmit the XML sitemap in Search Console.
Phase 3: The first 90 days
- Week 1, daily: coverage report for a 404 spike; crawl stats; top-20 pages' redirects re-verified.
- Weeks 2–6, weekly: positions vs. baseline, per template, because template-level drops point at template-level problems. Watch Core Web Vitals.
- Weeks 6–12: clicks and impressions vs. baseline. A one-to-two-week wobble is normal recrawl behavior; a sustained template-wide drop is a defect to find.
- Keep the redirect map live forever. Old URLs earn links and clicks for years.
What a safe migration looks like from the inside
When we rebuilt elevatodigital.com, the redirect map covered 212 legacy URLs one-to-one: every old WordPress path to its exact new home. The map lives in the deploy configuration: version-controlled, testable, permanent. That is the standard this checklist produces, and it is why SEO migration that protects your existing rankings is a named line in every rebuild we scope rather than an upsell.
Frequently Asked Questions
Will a website redesign hurt my SEO?
Only if the migration is mishandled. Rankings attach to URLs and content, not to designs. A redesign with a complete one-to-one redirect map, preserved titles and schema, and tested redirects typically sees at most a brief wobble of one to two weeks, and often improves rankings afterward because the new site is faster.
What is a redirect map?
A spreadsheet listing every URL on the old site next to the exact URL that replaces it on the new site. It is the core deliverable of a safe migration: each old page passes its ranking history to its specific successor via a 301 redirect, instead of 404ing and starting from zero.
Do I need redirects if my URLs aren't changing?
Far fewer, which is why keeping URL structure is the single cheapest SEO decision in a redesign. You still verify every URL resolves after launch, and you still need redirects for any pages being merged or retired.
How much traffic is normal to lose after a redesign?
With a complete, tested migration: little to none beyond a short recrawl wobble. Industry studies show the damage comes from skipped steps: incomplete redirects commonly cost 30–40% of organic traffic, and one analysis of 892 migrations found 17% of sites never fully recovered.
How long does Google take to process a migration?
Google recrawls and re-indexes most well-migrated sites within a few weeks; positions typically stabilize inside 4–6 weeks. The 90-day monitoring window exists to catch the slow-burn problems (orphaned pages, template-level issues) while they are still fixable.
Spend 30 minutes with our owner.
Book a Strategy CallPrefer to see a number first? Try the pricing calculator.