How to Redesign a Website Without Losing SEO

A redesign is supposed to be good news. New look, faster pages, better messaging, a site you're finally proud to send people to. And then, two weeks after launch, someone opens Search Console and asks the question nobody wanted to hear: why is organic traffic down 40%?

It happens all the time, and it's rarely because of the design itself. Search engines don't care whether your new buttons are rounded. They care about URLs, content, titles, headings, internal links, and whether pages can still be crawled and indexed. A redesign touches almost all of those at once, often without anyone deciding to change them. That's what makes redesigns the single most common cause of sudden, self-inflicted traffic drops.

The fix isn't to avoid redesigning. It's to treat SEO as part of the project from the start, with one simple principle running through everything: record exactly how the old site looks to search engines before you change anything, then compare the new site against that record before and after launch. Everything in this guide is an application of that principle.

Why redesigns lose traffic#

It's worth knowing the specific failure modes, because each one maps to a check later in the guide.

URLs change without redirects. The new site uses cleaner URLs, a different folder structure, or a new platform with its own URL patterns. Every old URL that isn't redirected becomes a 404, and the rankings and backlinks attached to it are thrown away.

Content gets trimmed. Designers and copywriters love shorter pages. But the paragraphs that got cut may be the ones that answered the questions your pages ranked for. A page that loses half its content often loses its rankings with it.

Titles, meta descriptions, and headings change. New templates generate titles differently, the SEO plugin's settings don't come across, or headings get rewritten for style. Pages that ranked because their title matched the search suddenly don't.

Internal links disappear. New navigation menus are usually smaller. Footer links get cut. Related-content blocks vanish. Pages that used to be linked from every page on the site end up linked from almost nowhere, and search engines treat them as less important.

Staging settings leak into production. The new site was built on a staging server with "noindex" turned on so it wouldn't appear in Google. At launch, that setting comes along. This one can remove a whole site from search results within days.

Technical details break. Canonical tags point to staging URLs. The robots.txt file blocks a folder by mistake. Structured data disappears. Analytics isn't installed on the new templates, so you can't even see the damage clearly.

Performance gets worse. Heavier images, animations, and new scripts can make the new site slower than the old one, especially on phones.

Notice that almost none of these are deliberate decisions. They're side effects. Which is why the only reliable protection is checking for them systematically.

Before the redesign: record everything#

This is the most important phase, and the one most teams skip. Once the old site is gone, you can't go back and see how it was set up. Do all of this before a single page changes.

1. Crawl the entire old site#

Run a full crawl with a site crawler or SEO audit tool and export the results: every URL, its status code, title, meta description, H1, canonical, word count, and internal links. Save this file somewhere permanent. It's your reference for the whole project.

2. Export your SEO performance data#

From Google Search Console, export the last 12 to 16 months of performance data by page and by query. From your analytics, export traffic and conversions by landing page. This tells you which pages matter most, and gives you a clean "before" to compare against after launch.

3. Identify your most valuable pages#

Sort by organic clicks, conversions, and backlinks. Usually a small number of pages bring in most of the value: your homepage, key product or service pages, and a handful of top articles. Mark them. These pages get extra care throughout the project, and their content should not be cut without a very good reason.

4. List your backlinked pages#

Use a backlink tool to find which old URLs have links from other websites. Every one of these needs a redirect to its closest new equivalent, or the value of those links is lost.

5. Capture how your key pages look now#

Take screenshots and save the exact titles, meta descriptions, headings, canonicals, and main content of your most valuable pages. A crawl gives you the data. Screenshots and saved content give you the context, so later you can see not just that a title changed but what the page used to say around it.

During the redesign: build SEO into the new site#

6. Keep URLs the same wherever you can#

The safest redirect is the one you don't need. If the old URL structure works, keep it. Change URLs only when there's a real benefit, not for tidiness alone.

7. Build a complete redirect map#

For every old URL that will change, write down the new URL it should go to, in a spreadsheet. Use the crawl from step 1 as the list of old URLs. Rules for a good redirect map:

• Redirect each old page to its most relevant new equivalent, not to the homepage.
• Use 301 (permanent) redirects.
• Avoid chains: old URL should go straight to the final new URL in one hop.
• Include old URLs with backlinks even if they were already redirecting somewhere before.

8. Protect the content on your top pages#

For your most valuable pages, compare the planned new content with the current content, section by section. It's fine to improve writing and layout. Be very careful about removing the sections, questions, and details that match what the page ranks for. If something has to go, consider moving it rather than deleting it.

9. Carry over the on-page SEO#

Make sure titles, meta descriptions, H1s, and headings on the new site match or improve on the old ones, especially for top pages. If the new platform or theme generates titles automatically, check its settings. Carry over structured data such as product, FAQ, article, and organization markup.

10. Rebuild internal linking deliberately#

List the pages your old navigation, footer, and sidebars linked to. If the new menus are smaller, make sure important pages are still linked from somewhere prominent, such as category pages, related-content blocks, or links within content.

11. Check performance on real phones#

Test key templates with PageSpeed Insights and on a mid-range phone. A redesign should make the site faster, not slower. Watch image sizes, fonts, and third-party scripts.

12. Block staging correctly, and plan to unblock it#

Staging should be hidden from search engines, ideally with password protection rather than only noindex. Write "remove noindex and staging blocks" on the launch checklist in capital letters. It's the single most expensive thing to forget.

Launch day: the checks that matter most#

On launch day, work through these before celebrating:

• Indexability: view source on key pages and confirm there's no noindex. Check robots.txt isn't blocking anything important. If you password-protected staging, confirm protection didn't carry over.
• Canonicals: make sure canonical tags point to the live domain, not staging.
• Redirects: test a sample of old URLs from your redirect map, especially your top pages and backlinked pages. Each should land on the right new page in one hop with a 301.
• Status codes: check that key new pages return 200 and that nothing important returns 404 or 500.
• Titles and meta: spot-check that titles and descriptions on key pages are the ones you intended.
• Analytics and tracking: confirm your analytics tag, tag manager, conversion tracking, and any pixels load on the new templates.
• Sitemap: generate a new XML sitemap with the new URLs and submit it in Search Console.
• Search Console: make sure your property still covers the site. If the domain or protocol changed, verify the new version.

After launch: compare against your baseline#

The first four to six weeks after launch are when problems surface. Some dip in rankings after a big redesign is common as search engines recrawl and re-evaluate the new pages. What you're watching for is a dip that doesn't recover, or one concentrated on specific pages.

13. Re-crawl the new site and compare#

Crawl the new site and compare it with your saved crawl of the old one. Look for pages that disappeared, titles and headings that changed, word counts that dropped sharply, and internal link counts that fell.

14. Watch Search Console by page#

Compare clicks, impressions, and positions per page with the same period before launch. When a specific page drops, compare its old and new versions directly: title, headings, content, links, canonical, indexability. The difference usually explains the drop.

15. Watch for 404s and redirect problems#

Check Search Console's "Not found (404)" report and your analytics 404 page views for old URLs you missed in the redirect map. Add redirects as you find them.

16. Keep checking after the launch rush#

Redesigns don't end at launch. The weeks after are full of fixes, tweaks, and "small" changes, each of which can reintroduce the problems you just checked for. Keep comparing key pages against your approved new baseline for a while after launch, not just on launch day.

If traffic dropped after your redesign#

If you're reading this after the fact, here's the fast path:

1. Check for noindex, robots.txt blocks, and staging canonicals first. They're the most damaging and the quickest to fix.
2. Test your old top URLs. Are they redirecting to the right new pages in one hop?
3. Compare old and new versions of your biggest losing pages: content, title, headings, internal links.
4. Restore the content and links that were cut from pages that lost rankings.
5. Request indexing in Search Console for fixed key pages.

Post 1 in this series, on why website traffic drops, walks through the full diagnosis. And if you didn't save a crawl of the old site, the Wayback Machine may have archived versions of your old pages to compare against.

Where MyKavo fits into this#

MyKavo is our product, and the "record before, compare after" principle this guide is built on is exactly how it works, so I'll be specific.

Before the redesign, add your site to MyKavo and approve baselines for your most valuable pages. MyKavo captures a screenshot of each one plus its SEO tags, content, links, scripts, and performance. That's your step 5 done, and stored somewhere that won't disappear with the old site.

At and after launch, MyKavo compares each page against its approved baseline and shows every difference side by side, ranked by severity: a page flipped to noindex or a canonical pointing to staging is critical, a missing analytics script or internal links that now return 404 are high, a changed title or trimmed content is flagged with the old and new values. Deploy checks (Pro and Agency plans) run a comparison automatically every time you ship, triggered from GitHub Actions, Netlify, Vercel, or any CI with one curl command, and report "Deploy verified" or a list of changes with screenshots. Once you've reviewed the new site, approve the new versions as the baseline, and from then on MyKavo protects the new site the same way.

Connect Search Console, and MyKavo matches traffic drops on each page against the changes it detected beforehand, which makes step 14 a lookup instead of an investigation. The Site Audit crawls the whole new site for broken pages, redirect chains, noindex mistakes, and duplicate titles, and the free Redirect Chain Checker lets you test redirects from your map one by one.

Honest limits: MyKavo monitors the pages you choose (5 on the free plan, 15 per site on Pro, 25 per site on Agency) and doesn't replace a full crawl of a large site or a backlink tool for finding linked old URLs. Use a crawler for the full inventory and MyKavo for the pages where a mistake would cost you the most.

Your redesign SEO checklist#

Before

1. Crawl the old site and save the export.
2. Export Search Console and analytics data by page.
3. Mark your most valuable pages.
4. List pages with backlinks.
5. Capture screenshots and SEO details of key pages.

During 6. Keep URLs where possible. 7. Build a complete one-hop 301 redirect map. 8. Protect content on top pages. 9. Carry over titles, meta, headings, and structured data. 10. Rebuild internal links deliberately. 11. Test performance on real phones. 12. Plan to remove staging blocks at launch.

Launch day Indexability, canonicals, redirects, status codes, titles, tracking, sitemap, Search Console.

After 13. Re-crawl and compare with the old crawl. 14. Watch Search Console by page. 15. Fix 404s and missed redirects. 16. Keep comparing key pages against the new baseline.

The bottom line#

Redesigns don't lose traffic because they look different. They lose traffic because things that search engines care about change without anyone deciding to change them. Record how your key pages look before you touch anything, carry the important parts across deliberately, and compare the new site against that record at launch and for weeks after.

MyKavo makes that record for you: approve baselines on your key pages before the redesign, and every difference on the new site shows up with before-and-after evidence, on launch day and on every deploy after. Start free before your redesign starts, while the old site is still there to capture.