BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Expected Traffic Loss During a Domain Migration, and the Recovery Timeline
You move a site to a new domain, the redirects go in clean, and then traffic falls off a cliff. That dip is the question every domain migration eventually raises: how much will you lose, and how long until it comes back?
The honest answer has two halves. A move done well loses a contained slice of traffic for two to three weeks and recovers inside a quarter. A move done badly loses far more, for far longer, and a fraction of those sites never fully return. The gap between the two outcomes is not luck. It is the quality of the execution and the quality of the domain you move onto.
This guide gives you the expected loss bands, a week-by-week recovery curve, and a way to tell a normal dip from a real problem, every figure attributed to a named source. It also draws the line the panic guides miss. The target domain, the one you move equity onto, is the variable under every recovery. SEO Domains operates the curated marketplace where aged and expired domains are screened for a clean history before they are listed, so the domain you migrate onto starts as an asset instead of a buried liability.
Will you lose traffic in a domain migration?
Yes. A temporary drop in organic traffic is the normal, expected behaviour of a domain migration, because Google has to recrawl and reindex the site under its new URLs before rankings settle. The question that matters is not whether you lose traffic, but how much, for how long, and whether the curve is recovering.
The dominant version of this search is a worried one. The community threads behind it read the same way every time: a site moved, traffic dropped, and the owner wants to know if this is a disaster or a phase. The reassuring part is that the dip itself is built into how search engines process a move.
What Google says about the dip
Google’s own documentation on site moves with URL changes is direct about it. The guidance describes the visibility of your content in Search as something that can fluctuate temporarily during the move, and adds, in its words, that “this is normal and a site’s rankings will settle down over time.” Google frames the fluctuation as a processing artefact, not a penalty.
That distinction is the whole game. A penalty is a judgement on quality. A migration dip is the search engine catching up to a change of address. One requires a fix to the site. The other requires a clean move and patience while the index updates.
The honest reality: done well versus done badly
Here is the part the cheerful guides skip. The dip is normal, but the size of it is not fixed. A move with complete redirects, an unchanged content structure, and a clean target domain loses a contained slice and recovers fast. A move with broken redirects, dropped pages, or a target domain carrying toxic history loses far more and can stall for over a year. Both are migrations. The execution and the raw material decide which one you get.
Why migration traffic drops: the seven causes
Migration traffic drops for seven identifiable reasons: redirect gaps that create 404 errors, the crawl-and-reindex lag while Google reprocesses URLs, content or structure changes that strip ranking signals, robots and noindex rules leaking from staging, lost on-page metadata, page-speed regressions, and broken inbound backlinks. The bulk of avoidable loss traces to the first two, and the rest stack on top.
Knowing the cause is what lets you separate the unavoidable from the self-inflicted. Daniel Bianchini, a UK technical SEO consultant, frames the recurring failures as basic issues that come back because teams overlook small details during a complex move. Shopify’s enterprise migration guidance reaches a similar list from the platform side. The seven causes below combine both accounts.
1. Redirect gaps and 404 errors
Old URLs that lack a 301 to their new equivalent return a 404. The page loses its rankings and the link equity pointing at it has nowhere to flow. This is the single largest cause of avoidable loss.
2. Crawl and reindex lag
Even with perfect redirects, Google has to recrawl every URL and reassign signals to the new address. This lag is unavoidable and accounts for the baseline dip on a clean move.
3. Content and structure changes
A migration bundled with a redesign that removes pages, merges sections, or rewrites content strips the exact signals those pages ranked on. The drop here is a content loss wearing a migration costume.
4. Robots and noindex leaking from staging
A staging site is blocked from crawling during the build. When that robots.txt block or noindex tag ships to the live site by accident, Google is told to stay out, and traffic collapses to zero.
5. Lost on-page metadata
Title tags, meta descriptions, headings, and canonical tags that fail to carry across the move change how pages are understood and clicked. Small individually, additive across a catalogue.
6. Page-speed regression
A new platform or template that loads slower degrades Core Web Vitals and user behaviour. The new domain inherits a performance problem the old one did not have.
7. Broken inbound backlinks
External links pointing at old URLs pass full value only when those URLs redirect. A redirect gap on a heavily linked page wastes the strongest equity the site owns.
The pattern across the seven is worth naming. Cause 2 is the price of admission you pay on every move. The rest are choices. The 301 mapping that prevents causes 1 and 7 is documented in Building the 301 mapping sheet, and the staging gate that catches cause 4 before launch is covered in Testing migrations on staging.
How much traffic you should expect to lose
A clean, well-mapped move typically loses 10 to 30 percent of organic traffic in the first month, per agency case data. A sloppy move with redirect gaps or a content overhaul loses 30 to 50 percent or more. A botched move, or one onto a domain with toxic history, has been documented losing up to 80 or 90 percent. The magnitude is a direct function of execution quality and target-domain health.
The numbers cluster by how the move was run. Fountain Partnership, a UK digital agency, puts a typical first-month drop “between 10% and 30%,” and Numen Technology, another UK agency, reports the same band. At the failure end, iO Digital states that a poorly managed migration risks losing “up to 80% of your organic traffic.” The widely cited first-person case documented by SEO writer Daniel Hooshmand lost close to 90 percent after a technically correct .net to .com move, falling from roughly 3,000 daily pageviews to around 50.
The expected-loss bands by execution quality
The table below converts those cited figures into bands keyed to how the move was executed. Treat them as reference ranges from documented cases, not a forecast for your specific site, because Google notes the speed of a move “largely depends on the number of URLs and your server speed.”
| Execution quality | What it looks like | Expected peak drop | Cited basis |
|---|---|---|---|
| Clean | Full 301 map, unchanged structure, clean target domain, staging-tested | 10-20% | Fountain Partnership, Numen Technology (10-30% band, clean end) |
| Standard | Mostly complete redirects, minor structure changes | 20-30% | Fountain Partnership, Numen Technology (10-30% band, upper end) |
| Sloppy | Redirect gaps, a bundled redesign, metadata not carried | 30-50%+ | Extrapolated from the documented failure cases below |
| Botched | Broken redirects, noindex leak, or a toxic target domain | Up to 80-90% | iO Digital (up to 80%), Hooshmand case (~90%) |
The cost dimension follows the percentage. The Hooshmand case put the revenue lost across its recovery at around 50,000 US dollars, against pre-move earnings of roughly 3,000 to 5,000 dollars a month. The lesson buyers take from that figure is that the loss band is not abstract. It is the difference between a quarter of soft revenue and a year of it.
The recovery timeline, week by week
On a clean move, traffic troughs in the first one to two weeks, shows a first partial recovery around weeks five to six, and returns to baseline within one to three months. Google describes the processing window as roughly two to four weeks for a small to medium site, longer for large ones. A botched move follows a far slower, phased curve that has run 12 to 18 months in documented cases.
Google’s guidance sets the official expectation: a small to medium-sized website can take two to four weeks for the bulk of its pages to move in the index, and larger sites take longer. That window matches the agency reports of a one to three month recovery on a clean move. The week-by-week shape below combines Google’s processing window with the recovery curves documented by Fountain Partnership and the Hooshmand case study.
Cutover. Google starts recrawling under the new URLs. The dip begins and deepens as old URLs drop out of the index faster than new ones enter. Source: Google site-move processing window.
The trough. Traffic hits its low point on a clean move. This is the moment owners panic and the moment to hold steady if the redirects are verified clean. Source: Hooshmand case (initial full drop), Google reindex lag.
First partial recovery. The new URLs are indexed and signals start transferring. The Hooshmand case logged its first bounce here. A clean move recovers a visible share of traffic in this window.
Full recovery on a clean move. Fountain Partnership reports a typical recovery window of one to three months, with one case curve running month 1 at minus 23 percent, month 2 at plus 76 percent, and month 3 at plus 230 percent against the old baseline.
Growth above baseline, if the move was paired with genuine improvement. The same Fountain case reached plus 600 percent by month 6. A move done well is a reset that can climb past where it started.
The botched curve. When redirects fail or the target domain carries toxic history, recovery stretches into phased steps over a year or more. The Hooshmand case recovered across 18 months in unexplained increments, and a fraction of botched moves never fully return.
The takeaway for buyers is that the first fortnight is uninformative on its own. A deep dip in week one is normal on both curves. The signal that you are on the clean path is movement back up by weeks five to six. The post-move monitoring cadence that watches for it is set out in Post-migration monitoring for 6 months.
How the type of migration changes the loss
The expected loss depends on what kind of move it is. An HTTP-to-HTTPS migration risks almost nothing. A like-for-like domain change risks the baseline dip. A migration bundled with a redesign or a content overhaul risks far more, because the URL change and the content change compound. A multi-domain consolidation or a full rebrand carries the highest exposure of all.
iO Digital flags mergers, takeovers, and name changes as the highest-risk category for exactly this reason: they rarely change only the address. The cleaner you keep the move, the more it behaves like the address-only case and the smaller the dip.
| Migration type | What changes | Loss exposure |
|---|---|---|
| HTTP to HTTPS | Protocol only, URLs otherwise identical | Minimal. Google notes this case does not even require the Change of Address tool |
| Like-for-like domain change | The domain, with paths and content held constant | The baseline dip, 10-30% on a clean move |
| Domain change plus redesign | The domain and the site structure or content together | Compounded. The URL change and content change stack into a deeper, longer drop |
| Multi-domain consolidation | Several domains merged into one | High. Mapping every source URL across domains multiplies the chance of a gap |
| Full rebrand | Domain, brand, and often structure at once | Highest. Brand-search recovery lags, and the move touches every signal |
The strategic move is to change one thing at a time. Moving the domain this quarter and redesigning next quarter keeps each dip contained and diagnosable. The exposure of merging multiple domains is treated in Multi-domain consolidation into one brand, and the brand-equity side of a full rebrand in Rebranding without losing SEO equity.
Is your drop normal, or a real problem?
A drop is normal when it troughs early, holds the expected band, and shows recovery by weeks five to six, and your redirects, indexing, and target domain all check out clean. A drop is a real problem when traffic stays at zero, keeps falling past month one, or a verification check fails. The triage below tells the two apart so you act on evidence instead of fear.
The reason buyers panic is that the chart looks the same for a normal dip and a fatal one in the first fortnight. The way to break the tie is to stop watching the graph and run the checks. Each row below pairs a symptom with whether it is normal and the action it warrants.
| Symptom | Normal, or a problem? | What to do |
|---|---|---|
| Traffic drops 10-30% in week one | Normal on a clean move | Hold. Verify redirects and indexing, then wait for the week 5-6 recovery |
| Traffic falls to near zero immediately | Problem | Check for a noindex tag or robots.txt block leaked from staging. This is cause 4, and it is urgent |
| Specific high-value pages return 404 | Problem | A redirect gap. Add the missing 301s from the mapping sheet before equity bleeds further |
| Drop keeps deepening past month one | Problem | The move is not recovering on the clean curve. Audit redirects, content parity, and the target domain’s history |
| Brand searches recover slower than the rest | Normal on a rebrand | Expected when the brand name changed. Track it separately and give it longer |
| No recovery signal by week 6-8 | Problem | Escalate. Re-verify the Change of Address submission and the full redirect map |
How to protect equity through the move, step by step
Protecting equity through a migration comes down to six disciplined steps: map every old URL to a 301, test the whole move on staging, choose and verify a clean target domain, submit the Change of Address tool, hold content and structure constant, then monitor against the recovery curve. Each step closes one of the seven causes of loss. The sequence is the difference between the clean band and the botched one.
This is the practical part. The steps below are ordered the way a move runs, and each one pairs the action with the specific mistake it prevents. Done in order, they keep a migration in the 10 to 30 percent band and on the recover-by-quarter curve.
-
Map every old URL to a 301 redirect
Build a complete one-to-one redirect map from every indexed old URL to its new equivalent. This closes causes 1 and 7, the redirect gaps and the broken backlinks, which together drive the bulk of avoidable loss. The full method is in Building the 301 mapping sheet.
The mistake: redirecting everything to the homepage instead of the matching page. A blanket homepage redirect throws away the page-level signals you are trying to preserve, and Google treats it as a soft 404.
-
Test the entire move on staging first
Run the redirects, the new structure, and the crawl on a staging environment before launch. iO Digital recommends a minimum of two weeks in staging. This is where you catch the noindex and robots leak, cause 4, before it reaches the live site. The gate is detailed in Testing migrations on staging.
The mistake: launching the noindex tag or robots.txt block from staging onto the live site. This single error takes traffic to zero, and it is the catastrophic mistake teams hit again and again.
-
Choose and verify a clean target domain
If the move is onto a new or acquired domain, verify its history before you commit equity to it. Check the registration record, the backlink profile, and the archive for prior spam or penalties, so the domain starts as an asset. Screened aged and expired domains with a clean history are listed on the SEO Domains marketplace, where the history is read before the domain is priced.
The mistake: migrating onto an unvetted domain bought for its metric. A toxic or penalised history is inherited the moment you move onto it, and no redirect can clean it off afterward.
-
Submit the Change of Address tool
For a domain change, submit a Change of Address in Google Search Console so Google is told the move is intentional and permanent. The mechanics are covered in Using GSC’s Change of Address tool. Note that Google does not require this step for an HTTP-to-HTTPS move.
The mistake: skipping the signal and leaving Google to infer the move from redirects alone. The inference works eventually, but the explicit signal speeds the reindex and reduces the depth of the dip.
-
Hold content and structure constant at cutover
Change the address and nothing else at the moment of the move. Keep the content, the internal structure, and the on-page metadata identical, so the only variable Google reprocesses is the URL. This closes causes 3 and 5, the content and metadata losses.
The mistake: bundling a redesign or a content rewrite into the migration. Two changes at once compound the drop and make the cause impossible to isolate when traffic falls.
-
Monitor against the recovery curve
Track the move against the expected curve: trough by week two, recovery signal by weeks five to six, baseline inside a quarter. Watch indexing, redirects, and traffic by segment. The full cadence is in Post-migration monitoring for 6 months.
The mistake: reacting to the week-one trough with panic edits. Changing things while Google is mid-reprocess adds noise and slows the recovery you are watching for.
The migration loss checklist: cause, why it costs, and the fix
The mistakes that turn a 15 percent dip into an 80 percent collapse are a short, repeatable list. Each one maps to a cause of loss and a documented fix, and the fixes converge on the same discipline: redirect everything, change one thing at a time, and start from a clean target domain. Use this as the scannable reference before and after a move.
The table consolidates the seven causes and the six steps into one place. The left column is the mistake, the centre is why it costs traffic, and the right is the fix. Read down the fix column and it describes a clean move onto a vetted domain with no compounded changes.
| The mistake | Why it costs traffic | The fix |
|---|---|---|
| Incomplete 301 map | Old URLs return 404 and lose rankings plus inbound link equity | A complete one-to-one redirect map for every indexed URL |
| Blanket redirect to the homepage | Page-level signals are discarded and Google reads a soft 404 | Redirect each old URL to its matching new page |
| Noindex or robots leak from staging | Google is told to stay out and traffic falls to zero | A staging test that verifies indexing rules before launch |
| Redesign bundled with the move | URL and content changes compound into a deeper, longer drop | Hold content and structure constant at cutover |
| Metadata not carried across | Titles, descriptions, and canonicals change how pages rank and get clicked | Migrate on-page metadata one-to-one with the URLs |
| Change of Address not submitted | Google reprocesses slower without the explicit move signal | Submit the Change of Address tool for a domain change |
| Migrating onto an unvetted domain | A toxic or penalised history is inherited and cannot be redirected away | Verify the target domain’s history before committing equity |
| Panic edits during the week-one trough | Changes mid-reprocess add noise and slow recovery | Hold steady and monitor against the recovery curve |
Migration traffic loss frequently asked questions
The five questions buyers and site owners raise when they search for migration traffic loss, answered against Google’s guidance and the documented agency and case-study figures this guide cites.
Q1How much traffic will I lose in a domain migration?
A clean, well-mapped move typically loses 10 to 30 percent of organic traffic in the first month, per agency case data from Fountain Partnership and Numen Technology. A botched move, or one onto a domain with toxic history, has been documented losing up to 80 to 90 percent. The figure you land on is set by redirect completeness and the health of the target domain.
Q2How long does it take to recover traffic after a migration?
Google states that a small to medium site takes around two to four weeks for the bulk of its pages to move, and larger sites take longer. A clean move troughs in the first week or two, shows a recovery signal by weeks five to six, and returns to baseline within one to three months. A botched move can stretch across 12 to 18 months, and a fraction never fully recover.
Q3Is a traffic drop after migration normal or a penalty?
A temporary drop is normal. Google describes search visibility as something that can fluctuate temporarily during the move, and states that “this is normal and a site’s rankings will settle down over time.” It is a processing artefact, not a penalty. The exception is a fall to near zero, which points to a noindex or robots block leaked from staging and warrants an immediate fix.
Q4Do 301 redirects prevent the traffic loss?
They prevent the avoidable part of it. Google states that “301 and other permanent redirects don’t cause a loss in PageRank,” so a complete map preserves the equity. They do not remove the baseline dip from the crawl-and-reindex lag, which is unavoidable on any move. Redirects keep you in the clean band; they do not eliminate the dip entirely.
Q5Does the domain I migrate onto affect the recovery?
Yes, and this is the variable nearly every guide skips. Moving onto a domain with a clean history recovers on the normal curve. Moving onto a domain that carries prior spam, a penalty, or toxic backlinks inherits that history the moment equity transfers, and no redirect undoes it. Verifying the target domain’s history before the move is as decisive as the redirect map.
The variable under every recovery: the domain you move onto
The target domain decides whether a migration recovers. A move onto a clean, screened domain returns to baseline on the normal curve. A move onto a domain carrying toxic history inherits that liability and stalls, whatever the redirects do. Sourcing a target domain whose history has been read before purchase is the single highest-leverage protection in the whole move. SEO Domains operates that curated marketplace.
Why the target domain is the deciding variable
Every competitor guide treats the destination domain as a given and obsesses over the redirects. The redirects matter, but they move equity onto whatever foundation you chose. If that foundation is a domain with a clean record, the equity lands and recovers. If it is a domain with a buried penalty or a toxic backlink profile, the move pours your hard-won equity onto a liability, and the recovery curve never closes.
How to verify a target domain is clean
A target domain that holds up survives a history check before the move commits to it. The signals that matter are the same ones used to screen any aged or expired acquisition:
- Registration history through the ICANN record, now served by RDAP, the Registration Data Access Protocol that replaced WHOIS as the standard lookup on 28 January 2025.
- The backlink profile, read for editorially earned links rather than a spam-inflated count.
- The archived page history, checked for prior unrelated or spammy use that would carry a reputation across.
- A clean penalty and spam screen, so the domain enters the move as an asset rather than a hidden liability.
A domain that fails these is a liability the moment equity moves onto it. A domain that passes them is a foundation that recovers. The metrics behind the screen are documented across the When to migrate from an old domain guidance and the wider migration hub.
Source a clean target domain, not a buried liability
The legitimate demand behind every migration traffic-loss search is a move that recovers. That outcome rests on a target domain whose history is known before equity transfers. That is the product: a screened domain, not a migration service and not done-for-you SEO. SEO Domains operates the curated marketplace where aged and expired domains are screened across their registration history, backlink profile, and prior use before they are listed and priced.
