All posts
Platform migrations

Why Traffic Drops After a Website Migration (and How to Fix It)

Traffic drop after website migration? Check tracking, redirects, indexing and lost content in that order, then follow a week-by-week recovery plan.

By Mehdi Hassan6 min read

The short answer

A traffic drop after website migration usually comes from one of four causes: broken analytics tracking, missing or wrong redirects, pages blocked from indexing, or content that didn't make it to the new site. Check them in that order, because the first is the cheapest to rule out and the last is the slowest to fix.

Key takeaways

  • Rule out broken tracking before anything else. Many scary dips turn out to be a missing tag.
  • Search Console clicks are the truth test, because they don't depend on your new analytics setup.
  • Redirect errors show up as 404s on old URLs that used to earn clicks.
  • A noindex tag or blocked robots.txt left over from staging can wipe out a whole site.
  • Lost copy, headings and internal links cause slow declines that redirects can't fix.

Part of Website Migration SEO Checklist: Keep Your Rankings When You Switch Platforms

Why does traffic drop after a website migration?

Traffic drops after a website migration because search engines and analytics both have to relearn the site. Some dip is normal while Google recrawls and processes redirects. A sharp or lasting drop almost always means something specific broke, and it can usually be found.

Threads like "90% drop in traffic after domain move" show up on the Webflow community forum, and the answers tend to land on the same few causes. If you haven't launched yet, our website migration SEO checklist prevents most of them. If you have, work through the diagnosis below before changing anything.

The order matters. Panicked teams rewrite pages or rebuild redirects when the real issue was a missing analytics tag. Diagnose from cheapest to most expensive.

What should you check first when SEO drops after migration?

Check your tracking first, because a measurement problem looks exactly like a traffic problem. Compare Google Analytics with Search Console clicks for the same dates. If Search Console clicks are steady and analytics fell, the traffic is fine and the tag is broken.

Order

What to check

Where to look

Signs it's the cause

1

Tracking

Analytics vs Search Console clicks

Clicks steady, sessions down

2

Redirects

Crawl of old URL list

Old URLs return 404 or chains

3

Indexing

Search Console pages report, robots.txt, meta robots

Pages excluded or noindexed

4

Content loss

Old vs new page comparison

Rankings slip on specific pages over weeks

5

Technical changes

Rendering, speed, canonicals

Pages indexed but ranking lower

Common tracking breaks include a tag that wasn't added to the new template, a consent banner that now blocks analytics by default, a new domain missing from the analytics property, and cross-domain settings that split sessions. Each is a quick fix once spotted.

How do you tell if redirects caused the drop?

Redirects caused the drop if old URLs that used to earn clicks now return 404s, redirect to the wrong page, or chain through several hops. The test is mechanical: take the list of old URLs and request every one.

  1. Get the old URL list

    Export top pages from Search Console for the months before launch, plus your pre-migration crawl and pages with backlinks.

  2. Crawl the list

    Run it through a crawler in list mode and record status code, hop count and final URL for each.

  3. Flag the failures

    Mark every 404, every chain of two or more hops, every 302 that should be a 301, and every redirect to the homepage.

  4. Fix by value

    Fix the URLs that earned the most clicks or links first. Point each at its closest matching new page.

  5. Re-crawl

    Run the list again until every row ends in a 200 after one hop.

The platform guides cover the mechanics: Webflow 301 redirects, Framer redirects and redirects in Next.js. If you never built a redirect sheet, start one with our 301 redirect map template.

Could indexing problems be the cause?

Indexing problems are the cause when Search Console shows pages excluded, blocked or marked noindex. This is the most dramatic failure because it can hit every page at once, and it's often a leftover from the staging site.

  • Meta robots noindex carried over from staging, often set at site level in the builder's settings.
  • robots.txt disallow that blocked the staging domain and launched with the real one.
  • Canonical tags pointing at the staging domain or the old URL.
  • Sitemap that still lists old URLs, or isn't submitted for the new domain.
  • Client-side rendering that leaves the main copy out of the HTML. Our guide on React SPA SEO migration covers this one.

What if the content changed during the migration?

If content changed during the migration, rankings tend to slide gradually rather than fall off a cliff. Redirects pass signals to a URL, but the new page still has to answer the query as well as the old one did.

Compare old and new versions of your top pages side by side. Look for shortened copy, missing H2s, removed FAQ sections, dropped internal links, lost alt text and missing schema. Redesigns trim words for looks, and those words were often what ranked. The fix is to restore the substance, not to revert the design.

Hypothetical example: diagnosing a slow slide

For example, suppose a SaaS site moves from WordPress to Webflow. Analytics and Search Console agree that clicks fell, redirects all resolve in one hop, and nothing is noindexed. Yet a handful of guide pages keep slipping.

The side-by-side comparison shows each guide lost its comparison table and FAQ in the redesign, and the new template dropped the related-articles links. The team restores the tables and FAQs as real HTML, adds the internal links back, and requests reindexing. That's a content fix, and no redirect change would have solved it.

How long does migration traffic recovery take?

Migration traffic recovery after a fix depends on how often Google recrawls the affected pages. Fixes to tracking show up immediately, redirect and indexing fixes start showing within days to weeks, and content fixes take longest because pages have to be re-evaluated.

When

Focus

What good looks like

Days 1–3

Tracking and indexing

Tags firing, no noindex, sitemap submitted

Week 1

Redirects

Every old URL resolves in one hop

Weeks 2–4

Top pages

Content restored on pages that lost rankings

Weeks 4–8

Watch and adjust

Impressions recovering on fixed pages

Week 8+

Long tail

Remaining 404s and orphan pages cleaned up

This is our working plan, not a guarantee. Large sites and domain changes take longer. If several things broke at once, our 30-day website migration recovery plan gives a fuller triage order.

How do you avoid a traffic drop next time?

You avoid a traffic drop by benchmarking before launch, mapping every URL, and checking the live site within hours of going live. Most migration losses come from steps that were skipped, not from steps that were hard.

Capture a baseline of rankings, clicks and crawl data before you touch anything, keep content parity on pages that earn traffic, and run a crawl on launch day. If you're also redesigning, read our guide on how to redesign a website without losing SEO before you cut copy.

Frequently asked questions

Is some traffic loss normal after a migration?
A short wobble is normal while Google recrawls the site and processes redirects, especially for large sites or domain changes. What isn't normal is a sharp drop that keeps going, or losses concentrated on specific pages. Those point to a concrete cause such as missing redirects, noindex tags or lost content, and they're worth diagnosing straight away.
Should I roll back to the old site if traffic drops?
Rarely. Rolling back creates a second migration, more redirects and more confusion for search engines. In most cases the cause is fixable on the new site within days. Consider a rollback only if the new site is fundamentally broken for crawlers, such as content that doesn't render, and you can't fix it quickly.
Can a new design alone cause lost rankings?
A design change alone rarely hurts rankings, but what changes alongside it often does. Shorter copy, fewer headings, removed internal links, hidden text in tabs, slower pages and dropped schema all affect how pages rank. Compare the content of old and new pages rather than how they look.
Does requesting reindexing in Search Console help?
It helps for a handful of important pages after you've fixed them, because it prompts Google to recrawl sooner. It doesn't scale to a whole site and won't fix an underlying problem. For site-wide issues, fix the cause, submit an updated sitemap and let Google recrawl on its own schedule.

· CEO & Design Director

Copywriter, designer and developer, and founder of Designify Studio. Over five years, 60+ projects across 14+ industries, for startups that have raised $300M+.

Want this done for you? Website, $8,000.

A multi-page marketing site, designed by us, developed in Next.js and animated. $8,000, one-time, up to 6 pages. Book a free 30-minute call to see if it fits.

Schedule Call