How to redesign a website without losing SEO

You can redesign a website without losing search traffic if you treat the project as a migration, not just a new look. The biggest risks are changed URLs without redirects, deleted pages that were earning traffic, and launch mistakes like a leftover "noindex" tag. Inventory what ranks today, map every old URL to a new one, and check the launch carefully, and most sites come through steady or better.

Why redesigns lose traffic

Search engines and AI answer engines have learned what your site is about from its URLs, content, links and structure. A redesign can change all four at once. The common failure points we see:

• URLs change with no redirects. Old links and rankings point to pages that now return 404 errors.
• Content gets cut. A new design with "less text" quietly removes the paragraphs that answered the questions people searched for.
• Pages get merged or dropped without anyone checking which ones brought in leads.
• Metadata disappears. Title tags, meta descriptions, canonical tags and schema markup are not carried over.
• Staging settings go live. A "discourage search engines" setting or a robots.txt block from the staging site ships to production.
• Performance gets worse. Heavy animations, unoptimized images and new scripts hurt Core Web Vitals.
• Internal links break because navigation and in-content links were rebuilt by hand.

Each of these is preventable. The work is mostly in the planning.

Before you design: build the inventory

Start with what you have. You cannot protect what you have not measured.

1. Crawl the current site. Use a crawler to export every URL, its status code, title tag, meta description, H1, canonical tag and word count.
2. Pull performance data. From Google Search Console, export pages and queries with clicks and impressions for the last 12 to 16 months. From your analytics, export landing pages with sessions and conversions.
3. Find your linked pages. Use a backlink tool or Search Console's links report to see which pages other sites link to. Those links carry authority you want to keep.
4. Flag your money pages. Service pages, location pages and articles that bring leads or sales get special protection.
5. Benchmark. Record rankings for your priority terms, Core Web Vitals and organic conversions so you can compare after launch.

Put it all in one spreadsheet. Every row is an old URL, and you will decide its fate in the next step.

Decide each page's fate

A few rules we hold to:

• Keep URLs when you can. The safest redirect is the one you never need. If your current URL structure is reasonable, keep it, even on a new platform.
• Redirect to the closest match, not the homepage. Sending every old page to the homepage is treated a lot like a 404.
• Avoid redirect chains. If page A already redirects to B, and B moves to C, point A straight to C.
• Use 301s for permanent moves. See 301 redirect in our glossary.

During design and build: protect the content

The design team and the SEO plan need to talk early. Some practical guardrails:

• Write content before or alongside design, not after. Designing around placeholder text is how useful content gets cut.
• Carry over the substance of pages that rank. You can tighten the writing, but keep the questions it answers and the terms people actually search for.
• Keep heading structure meaningful. One H1 per page, descriptive H2s. This helps search engines and screen readers alike.
• Rebuild structured data. If the old site had LocalBusiness, Product, FAQ or Article schema, the new one needs it too.
• Answer the question first. If you are rewriting anyway, lead pages with a direct answer. That is how pages earn citations in AI results, which we covered in answer engine optimization.
• Budget for speed. Set performance targets and test templates on real devices. Our Core Web Vitals guide explains what to measure.

If you are also changing platforms

Platform changes (WordPress to Webflow, Squarespace to WordPress, WordPress to a Next.js front end) are common in redesigns and perfectly safe if handled as a migration. Watch for:

• Different URL patterns. Some platforms force folder structures for blog posts or collections. Map those patterns before you commit.
• Redirect management. Know where redirects will live: a WordPress plugin, the Webflow redirect panel, or a config file on Netlify or Vercel (see Netlify vs Vercel).
• Media URLs. Images often move to a new CDN path. Important images that rank in image search may deserve redirects too.
• Feature parity. Forms, search, gated content and integrations need a plan on the new platform.

If you are weighing platforms, our posts on WordPress for content sites, Webflow for design-led sites and Next.js for business websites explain where each one fits.

Launch day checklist

Run this on the live site, not staging.

• Robots.txt allows crawling and does not block CSS or JavaScript.
• No "noindex" tags on pages that should be indexed. Check templates, not just the homepage.
• Every redirect in the map works, returns a 301 and lands on a 200 page. Test the full list with a crawler.
• The XML sitemap lists only live, indexable, canonical URLs and is submitted in Search Console.
• Canonical tags point to the correct live URLs, not staging.
• HTTPS works everywhere with no mixed content. See SSL/TLS.
• Analytics and conversion tracking fire on key pages and forms.
• Title tags, meta descriptions and Open Graph tags are present.
• Structured data validates.
• Internal links point to new URLs directly, not through redirects.

If your domain is changing too, use Search Console's change of address tool after redirects are live, and keep the old domain registered and redirecting for the long term.

After launch: watch and fix

The first weeks matter most.

• Check Search Console daily for the first two weeks. Look at crawl errors, pages not indexed and any manual actions.
• Crawl again a few days after launch to catch broken links and redirect chains.
• Watch 404s in your analytics or server logs. Redirect any that have links or traffic.
• Compare against your benchmark at 30, 60 and 90 days. Some movement is normal while Google processes changes. A sustained drop on specific pages points to a specific cause, usually a missing redirect or missing content.
• Keep the redirect map permanently. Redirects should stay in place for as long as anyone might follow an old link.

What a redesign can improve

Done carefully, a redesign is a chance to gain ground, not just hold it:

• Faster templates that pass Core Web Vitals.
• Cleaner information architecture with stronger internal linking.
• Consolidated content that ranks better than several thin pages did.
• Better structured data and clearer answers that AI tools can cite.
• Fewer plugins and scripts, which also helps security. Our WordPress security guide covers that side.

The short version

Inventory everything, decide every URL's fate, keep content that earns traffic, redirect with 301s to the closest match, and check the launch on the live site. Then monitor for three months. The platform you move to matters far less than the discipline of the migration.

Planning a redesign? See our SEO and AEO services or talk to us about your project.