SEO · Web Design

How to redesign your website without losing SEO.

The step-by-step process that preserves your organic traffic during a site overhaul — because a redesign that kills your rankings isn't a redesign, it's a reset. // April 2026

The Stakes

A bad redesign can erase years of SEO progress in a single deploy.

It happens constantly. A business spends $15K on a beautiful new website, launches it on a Friday afternoon, and watches organic traffic drop 40–60% over the next two weeks. By the time they realize what happened, the damage is baked into Google's index.

The most common causes of post-redesign traffic loss:

  • Changed URLs without redirects: Every URL that ranked is now a 404. Google drops those pages from the index within days. Backlinks pointing to old URLs become worthless.
  • Removed content that was ranking: The new design is "cleaner" so they cut 60% of the content. That content was generating 60% of the organic traffic. Clean design, empty pipeline.
  • Broke internal linking structure: The old site had 200 internal links distributed across a logical hierarchy. The new site has a flat navigation with 15 links. Google can't find or prioritize your pages anymore.
  • Killed page speed: The redesign added a heavy JavaScript framework, large hero videos, and animation libraries. Core Web Vitals went from passing to failing. Rankings follow within weeks.

None of these are inevitable. They're all preventable with a structured migration plan. Here's the process we use for every website redesign project.

Step 1–2

Crawl everything. Map everything. Before you touch a line of code.

Step 1: Full crawl of the existing site. Use Screaming Frog or Sitebulb to crawl every URL on your current site. Export the complete list. For each URL, record: the page title, meta description, H1, word count, internal links pointing to it, and external backlinks (from Ahrefs or Semrush). This is your baseline.

Also pull from Google Search Console: every URL that received organic clicks in the last 12 months, with impressions, clicks, and average position. Sort by clicks descending. These are your money pages — the ones that absolutely cannot break during migration.

Step 2: Create the URL mapping spreadsheet. Every old URL gets mapped to its corresponding new URL. Three possible outcomes for each:

  • 1:1 redirect: Old URL maps to an equivalent new URL. This is the ideal case. The 301 redirect transfers approximately 90–99% of link equity.
  • Consolidation: Multiple old pages merge into one new page. Each old URL gets a 301 to the consolidated page. Make sure the new page contains the valuable content from all merged pages.
  • Intentional removal: The page is genuinely outdated or irrelevant. Redirect it to the closest relevant page, not the homepage. Homepage redirects for everything is a signal to Google that you don't know what you're doing.

This spreadsheet is the single most important document in any redesign. If you skip it, you're gambling with every ranking you've earned.

Step 3–4

Preserve the content that earns traffic. Improve everything else.

Step 3: Content migration with intent preservation. For every page that ranks, the new version must contain at least the same topical coverage. You can rewrite, restructure, and improve — but don't remove the sections that Google matched to search queries.

Practical approach: for each money page, check which queries it ranks for in Search Console. Read through those queries and verify the new page content directly answers them. If the old page ranks for "cost of commercial painting Los Angeles" and the new version removes the pricing section, you'll lose that ranking.

A redesign is the perfect opportunity to improve content — add depth, update statistics, improve structure. Just don't subtract what's already working.

Step 4: Implement 301 redirects before launch. Every redirect from your URL mapping spreadsheet needs to be configured and tested before the new site goes live. Not after. Before.

  • Implement redirects at the server level (.htaccess for Apache, nginx.conf for Nginx) — not with JavaScript or meta refresh tags
  • Test every redirect with curl -I to verify 301 status codes and correct destinations
  • Handle trailing slashes consistently — /about and /about/ should both resolve correctly
  • Don't chain redirects — A should redirect to C directly, not A to B to C. Chains lose link equity at each hop and slow down crawling

For large sites (500+ pages), use redirect pattern rules where possible instead of individual rules. A single regex rule can handle hundreds of URLs if the URL structure changed predictably.

Step 5–6

Protect crawl budget and monitor like it's launch week — because it is.

Step 5: Crawl budget preservation. Google allocates a finite crawl budget to your site. During a redesign, you need Google to recrawl and reindex your new pages quickly. Don't waste that budget:

  • Submit the new sitemap.xml to Search Console immediately after launch. Remove the old one.
  • Keep robots.txt clean — don't accidentally block CSS, JS, or image directories that Googlebot needs to render pages
  • Eliminate soft 404s — pages that return 200 status but show "page not found" content. Google hates these.
  • Use noindex on staging/development environments to prevent Google from indexing your unfinished site before launch
  • Use the URL Inspection tool in Search Console to request indexing of your most important pages first

Step 6: Post-launch monitoring. The first 30 days after launch are critical. Set up monitoring for:

  • Daily crawl stats in Search Console — crawl rate should increase after launch, not decrease
  • Index coverage report — watch for spikes in "Excluded" or "Error" pages
  • Organic traffic in Analytics — compare week-over-week to the same period before launch
  • Run a fresh crawl with Screaming Frog 48 hours post-launch to catch broken links, missing redirects, and new 404s
  • Monitor Core Web Vitals in the field (CrUX data) for the first 28 days

If traffic drops more than 10% in the first week, investigate immediately. Check for missing redirects, deindexed pages, or crawl errors. Most post-redesign SEO damage is reversible if caught within the first two weeks.

Common Mistakes

The five redesign mistakes we see every month.

After handling dozens of SEO recovery projects, these are the redesign mistakes that cause the most damage:

  • Launching without redirect testing: "We'll fix the redirects after launch." By then, Googlebot has already crawled your 404s and started deindexing pages. You have hours, not days.
  • Switching to a JavaScript framework without server-side rendering: React and Vue are great for web apps. For content sites, a client-rendered SPA can destroy your organic traffic because Googlebot struggles with JavaScript-heavy pages, despite what Google says about being able to render them.
  • Removing structured data: The old site had schema markup for products, reviews, FAQs. The new design team didn't implement any. Rich snippets disappear, CTR drops 15–30%.
  • Changing the domain without a plan: Moving from oldbrand.com to newbrand.com requires Google's Change of Address tool, site-wide 301s maintained for at least a year, and updated backlinks where possible. Skip any step and traffic tanks.
  • Ignoring internal linking: The old site had deep internal linking from years of content. The new site starts with a clean navigation and no cross-links. Orphaned pages lose rankings because Google can't discover them. A technical audit catches this before it hurts.

Every one of these is preventable with planning. The redesign itself is the easy part. Preserving what you've built in search is the real work.

The Checklist

Pre-launch, launch day, post-launch — the full sequence.

Pre-launch (2–4 weeks before):

  • Complete crawl of existing site exported to spreadsheet
  • URL mapping document finalized with old URL, new URL, and redirect type for every page
  • Content audit confirming all ranking content is preserved or improved in new versions
  • Redirects implemented and tested on staging environment
  • New sitemap.xml generated and validated
  • Schema markup verified on all key page types
  • Core Web Vitals tested on staging — all metrics passing

Launch day:

  • Deploy new site, verify redirects are live with curl -I on 20+ old URLs
  • Submit new sitemap to Google Search Console
  • Request indexing for top 10 revenue-generating pages
  • Run a full crawl of the live site — compare page count, status codes, and internal links to pre-launch baseline

Post-launch (30 days):

  • Daily: check Search Console for crawl errors and index coverage changes
  • Weekly: compare organic traffic and rankings to pre-launch baseline
  • Day 7: full crawl to catch any redirects that were missed or broken
  • Day 30: comprehensive comparison — if traffic is within 5% of pre-launch levels, the migration succeeded

Planning a redesign? Let's make sure your rankings survive it.

We'll audit your current SEO equity and build a migration plan that preserves every ranking you've earned.

botless.systems encrypted · los angeles
Botless Systems_