Technical SEOWeb development

Redesign without the traffic crash: the 2026 website migration guide

How to redesign or migrate a site in 2026 without losing traffic: benchmark, map every URL, redirect properly, test on staging and monitor after launch.

By TRAGAUpdated Advanced14 min read

Guide cover for 'Redesign without the traffic crash', TRAGA 2026 guide pack: white headline and cover lines on a dark carbon background beside a large oxide red letter A

Short answer: most traffic losses after a redesign come from a short list of avoidable mistakes: old URLs that do not redirect, valuable content removed or rewritten badly, pages accidentally blocked from search engines, and slower templates. Avoid them by benchmarking first, mapping every old URL to its new equivalent, testing the new site on staging, launching with 301 redirects in place and monitoring closely for at least six weeks.

A website migration is any major change that can affect how search engines see your site: a new design, new CMS, new URL structure, new domain or new hosting. Each carries risk, and combining several at once multiplies it. Google’s documentation on site moves with URL changes is the neutral reference for much of what follows.

Why redesigns lose traffic

Search engines rank individual URLs based on their content, links and history. When a redesign changes those URLs or their content without telling search engines what happened, that history can be lost. The most common causes:

  1. Missing or wrong redirects. Old URLs return 404 errors, so links and rankings are lost.
  2. Content changes. Pages are shortened, merged or rewritten, and lose the content that ranked.
  3. Blocked crawling. A staging robots.txt rule or noindex tag goes live by mistake.
  4. Internal linking changes. Important pages lose links from navigation and related content.
  5. Slower templates. New designs add heavy scripts, images or fonts that hurt Core Web Vitals.
  6. Rendering problems. Content that relied on server-rendered HTML now depends on JavaScript that crawlers struggle with. See JavaScript SEO.

Phase 1: plan and benchmark

Decide what is changing. List every change: design, CMS, URL structure, domain, hosting, content. If possible, avoid changing everything at once. For example, migrate the platform first and the URLs later, so problems are easier to trace.

Benchmark current performance. Export from Google Search Console and GA4:

  • Clicks, impressions and positions by page and query for the last 12 months
  • Landing pages by sessions and conversions
  • Pages with the most backlinks
  • Core Web Vitals by template

Crawl the current site. Use a crawler to capture every URL, its status code, title, meta description, H1, canonical, word count and internal links. Save it. This crawl becomes your record of what existed before.

Phase 2: map every URL

The redirect map is the single most important document in a migration.

  1. List every URL from your crawl, sitemap, analytics and backlink data. Include images and PDFs that get traffic or links.
  2. For each old URL, choose the most relevant new URL. A product page should redirect to the same product, not the home page.
  3. Where content is being merged, redirect each old page to the new combined page.
  4. Where content is being removed with no equivalent, redirect to the closest relevant category, or let it return 404 or 410 if nothing fits.
  5. Avoid redirect chains: old URLs should point straight to their final destination.
Old URL New URL Type Notes
/services/seo-services /services/seo 301 Same content, cleaner URL
/blog/what-is-dmarc /glossary/dmarc 301 Merged into glossary
/team/old-staff-member /about 301 No direct equivalent

Redirecting many unrelated pages to the home page is treated like a soft 404 and wastes the value of those pages.

Phase 3: protect the content that ranks

Compare old and new versions of your top 50 pages by traffic and conversions. Check that the new versions keep:

Design teams often shorten content for visual simplicity. If a page ranks because it thoroughly answers a question, cutting that content can cost rankings. Use layout, such as accordions that remain in the HTML or tabs that render server-side, to keep content without clutter.

Phase 4: test on staging

Build the new site on a staging environment protected from indexing, ideally with password protection rather than robots.txt alone. Before launch, crawl staging and check:

  • Every important page returns a 200 status
  • Redirects from the map work and resolve in one hop
  • Canonical tags point to the correct live URLs, not staging URLs
  • No unintended noindex tags
  • Titles, descriptions, H1s and structured data are present
  • Internal links point to new URLs, not old ones that redirect
  • Pages render fully without relying on client-side JavaScript for key content
  • Speed and Core Web Vitals on key templates meet thresholds documented on web.dev
  • Accessibility basics, such as headings, contrast and keyboard navigation, meet WCAG

Prepare the new XML sitemap and robots.txt.

Phase 5: launch day

Choose a quieter period for your business, not the week before a big campaign or seasonal peak. On launch day:

  1. Remove staging protections and confirm the live robots.txt allows crawling.
  2. Deploy redirects and test a sample of old URLs immediately.
  3. Submit the new XML sitemap in Search Console. Keeping the old sitemap available for a short time can help search engines discover redirects.
  4. If the domain changed, verify the new domain in Search Console and use the Change of Address tool, as described in Google’s site move guide.
  5. Check analytics and tag manager are firing on the new site, including key events.
  6. Update important external links you control, such as social profiles, directory listings and your Google Business Profile.

Phase 6: monitor and fix

For the first few weeks, check daily, then weekly:

  • Search Console: page indexing report, crawl errors, sitemap status, and clicks and impressions compared with your benchmark.
  • 404 reports: find old URLs that were missed in the map and add redirects.
  • Rankings: for your top queries and pages.
  • Analytics: traffic and conversions by landing page.
  • Server logs if available, to see how search engines crawl the new site. See log file analysis.

Some fluctuation is normal for a few weeks while search engines process the changes. A sustained drop on specific pages usually points to a specific cause, such as a missing redirect or removed content, which you can fix.

Keep redirects in place for at least a year, and ideally permanently. Google recommends keeping them for as long as possible.

Choosing a platform that helps SEO

If you are changing platforms, it is a chance to build on strong foundations. Look for:

  • Fast output, such as static site generation or efficient server rendering, served from a CDN
  • Full control over titles, descriptions, canonicals, redirects, structured data and sitemaps
  • Clean, semantic HTML and good accessibility
  • An editing experience your team will actually use

Our approach to SEO-first web development builds these into the templates from day one.

Who should be involved

Migrations go wrong most often when SEO is brought in at the end. Involve the right people from the planning stage:

  • Project owner: sets the timeline and makes trade-off decisions, such as delaying launch if critical checks fail.
  • SEO lead: owns the benchmark, redirect map, staging checks and post-launch monitoring.
  • Developers: implement templates, redirects, rendering and performance.
  • Content owners: confirm which pages are kept, merged or removed, and protect content that ranks.
  • Analytics owner: makes sure tracking, key events and consent work on the new site from the first minute.

Agree in advance on a short list of launch blockers, such as missing redirects for top pages or a sitewide noindex, that stop the launch if found. Having that agreement before launch day prevents difficult conversations under time pressure.

A professional services firm redesigned its website and moved to a new CMS. The first attempt launched without a redirect map, and organic traffic fell by about half within two weeks. Search Console showed hundreds of 404 errors from old blog and service URLs that still had backlinks.

The firm built a full redirect map from its old crawl and backlink data, restored the detailed content that had been cut from service pages and fixed canonical tags that pointed to staging. Traffic recovered over three months. For its next project, a domain change two years later, it followed the process above and saw only a brief dip before traffic returned to normal.

Migration checklist

  • Changes listed and, where possible, phased
  • 12-month performance benchmark saved
  • Full crawl of the old site saved
  • Redirect map covering every valuable URL
  • Top pages’ content, metadata and schema protected
  • Staging crawl passed: status codes, redirects, canonicals, noindex, speed
  • Launch-day checklist completed, sitemap submitted
  • Daily then weekly monitoring for six weeks

Planning a redesign? Our web development and SEO teams run migrations end to end. Request a free audit before you start.

FAQ

Frequently asked questions

Will a website redesign hurt my SEO?

It does not have to. Traffic drops after redesigns usually come from missing redirects, changed content, blocked pages or slower templates. Careful planning avoids most of them.

How long does traffic take to recover after a migration?

With good planning, fluctuations usually settle within a few weeks. Poorly planned migrations can take months to recover, and some never fully do.

Should I keep my URLs the same?

If your current URLs are clean and descriptive, keeping them is the safest option. Change them only when there is a clear benefit, and redirect every old URL.

Do I need to tell Google about a domain change?

Yes. Use the Change of Address tool in Search Console after setting up 301 redirects from the old domain to the new one.

Free audit

Find out where you stand in search and AI answers.

Get a free audit of your SEO, AI visibility and email setup. We send a short, specific report with the three changes that would move the needle most.