Here is the uncomfortable truth about redesigns: Google ranked your old website, not your business. The rankings live in specific URLs, the content on them, the links pointing at them, and the signals they have accumulated. Change all of that on launch night without a plan, and Google meets a stranger wearing your domain.
We are writing this as a team that recently rebuilt and migrated our own agency website, every page, new structure, new design, which is exactly the scenario where an agency either proves it can protect rankings or quietly demonstrates it cannot. The checklist below is the process we use on client redesigns and used on our own, organized by phase so you can run it top to bottom.
Phase 1: Before Anyone Designs Anything
Crawl and inventory the current site. Export every URL from a crawler (Screaming Frog or similar) plus Google Search Console and analytics. You cannot protect what you have not listed. Note each URL’s traffic, rankings, and backlinks.
Identify your money pages. Sort by organic traffic and conversions. Typically 10 to 20% of pages produce 80%+ of organic value. These pages get preserved with the most care: their URLs kept where possible, their content carried over fully, never trimmed for aesthetics.
Benchmark everything. Screenshot Search Console performance, export ranking positions for target keywords, record Core Web Vitals. Post-launch arguments about “did we lose traffic” are settled by benchmarks taken now, not memories.
Map old URLs to new URLs, one to one. This spreadsheet is the single most important SEO artifact of the whole project. Every old URL gets a destination: kept as is, redirected to an equivalent page, or consciously retired. “Redirect everything to the homepage” is not mapping; it is how link equity dies.
Decide URL structure once, before design. If URLs must change (new hierarchy, new slugs), change them deliberately and only where the new structure earns it. Every changed URL is a redirect, and every redirect is a small toll on equity.
Phase 2: During Design and Build
Carry over the content that ranks, then improve it. Redesigns fail SEO most often not through redirects but through content slimming: a 1,800-word service page that ranked becomes 300 words of elegant whitespace. Design around the content that earned the rankings; do not amputate it to fit a template.
Preserve heading structure and internal links. Rebuild H1s and H2s carrying target keywords, and re-create internal links between related pages; they are how authority flows. A new nav that orphans old money pages demotes them.
Build the redirect file during development, not launch week. Every mapped URL becomes a 301 (permanent) redirect. Avoid chains (A to B to C) and never use 302s for permanent moves.
Keep the staging site out of Google. Password-protect staging or noindex it properly, then, critically, remember to remove the noindex at launch. Both directions of this mistake are common, and one of them de-indexes your new site.
Bake in speed from the start. Compressed images, minimal scripts, decent hosting. Core Web Vitals are a ranking input and a conversion input; our free Core Web Vitals ebook covers the three metrics to hit. A beautiful redesign that doubles load time is a downgrade in Google’s eyes.
Rebuild the SEO furniture. Title tags and meta descriptions carried over or improved (not regenerated as defaults), image alt text, schema markup re-implemented, XML sitemap regenerated, canonical tags checked. This is standard technical SEO work, and it is where template-swap redesigns silently drop the ball.
Phase 3: Launch Day
Run this sequence in order:
- Deploy the site and the full 301 redirect file together, not hours apart
- Remove noindex/staging blocks and confirm pages render for Googlebot
- Spot-check the top 50 old URLs by hand: each should land on its mapped page
- Verify analytics and conversion tracking fire on the new templates (forms, calls, purchases)
- Submit the new XML sitemap in Search Console
- Crawl the live site for 404s, redirect chains, and broken internal links
- Check robots.txt is not blocking anything it should not
Launch on a low-traffic day for your business, with the person who can fix server issues actually available. Friday 5 pm launches are how small problems get a weekend to compound.
Phase 4: The 90 Days After
Watch Search Console like it owes you money. Coverage errors, 404 spikes, and dropped pages show up here first. Expect some ranking wobble for 2 to 6 weeks as Google recrawls; a wobble is normal, a cliff that persists past a month means something on this checklist was skipped.
Fix the 404s that appear. Old URLs you missed will surface (from external links, bookmarks, Google’s memory). Add redirects as they appear; each one recovered is equity saved.
Compare against your benchmarks at 30, 60, 90 days. Page by page, not just sitewide. One money page quietly losing half its traffic can hide inside a flat sitewide number.
Update external links you control. Google Business Profile, social bios, directories, ad campaigns: point them at the new URLs directly rather than through redirects.
What Migrating Our Own Site Taught Us
Three lessons from rebuilding our own agency website that the standard checklists undersell. First, the URL inventory always finds pages you forgot existed: old campaign landing pages, tag archives, PDFs collecting backlinks. Budget a full pass for the long tail, because the strangest old URLs are often the ones other sites link to. Second, the self-referencing links inside your own content are a hidden migration surface: posts linking to other posts, service pages linking to each other. We found and fixed a systemic internal-link error across more than a dozen of our own posts during ours, the kind of template-level bug that a redirect map alone never catches, so crawl your internal links after launch, not just your redirects. Third, the discipline of changing one variable at a time is worth real money: because we migrated structure first and rewrote content in scheduled passes afterwards, every ranking movement had one candidate cause instead of three.
The Five Mistakes That Cause Most Redesign Traffic Losses
- No redirect map, or homepage-only redirects
- Content trimmed to fit the design, deleting what ranked
- Noindex left on from staging
- URL structure changed everywhere for tidiness rather than necessity
- Tracking never re-verified, so nobody notices the loss until it is a quarter old
Notice none of these are exotic. Redesign SEO is not a dark art; it is a checklist executed with discipline, which is precisely why skipping it is so expensive.
Frequently Asked Questions
Some short-term movement over 2 to 6 weeks is normal while Google recrawls. Sustained losses come from skipped steps, missing redirects, thinned content, blocked pages, not from redesigning itself. Done properly, many sites end up ranking better, because speed and structure improve.
Every URL with traffic, rankings, or backlinks: yes, mapped to its closest equivalent. True dead weight (expired promos, empty tags) can 404 or 410 deliberately. The sin is not retiring pages; it is retiring them by accident.
Treat them as permanent. Google recommends at least a year; in practice, external links keep pointing at old URLs for many years, and redirects cost nothing to keep.
Yes, and for large sites a section-by-section migration is lower risk: smaller redirect batches, easier diagnosis when something dips. The checklist applies per stage.
Improve, yes; replace wholesale at launch, carefully. Changing design, URLs, and content simultaneously makes diagnosis impossible if traffic drops. Where content needs major rework, prefer launching with preserved content and upgrading pages in the weeks after, one variable at a time.
The same work cuts both ways. AI Overviews and answer engines cite pages that are crawlable, fast, well-structured, and rich in clear answers, so a redesign that preserves content and improves structure typically helps. One addition worth making during the rebuild: proper schema markup and question-shaped headings, since those are exactly what AI-era optimization feeds on.
One named person, with both skills in the room. This is the strongest argument for a company that does design and SEO under one roof: when they are separate vendors, the redirect map is always the other guy's job.
