
Key takeaways
- A Search Engine Journal study of 892 domain migrations found an average recovery time of 523 days, about 17 months, for the new domain to match the old domain's organic traffic.
- 17% of the migrations in the sample never returned to their pre-migration traffic level even after 1,000 days of tracking.
- The fastest recoveries took 19, 22, 23, and 33 days, but the study gives no cause for them; the author's launch-ahead advice comes from experience.
- The study grew from 171 migrations in the author's 2023 dataset to 892 in 2024, and average recovery time still rose year over year rather than falling.
- The author found some correlation between referring-domain count and recovery time, with many outliers likely due to how each migration was carried out.
Domain migrations, moving a site’s content to a new domain and redirecting the old one, carry a known SEO risk, but how long the risk actually lasts has mostly circulated as folklore. Search Engine Journal contributor Dan Taylor ran a real, large-scale study of it: 892 tracked domain migrations, each measured for how many days the new domain took to reach the same estimated organic traffic the old domain had. We read the study directly. Here is what it found.
The headline number
The average across the 892 migrations was 523 days, about 17 months, for the new domain to match the old domain’s organic traffic. That average sits on top of real spread, not a tight cluster. The shortest recovery times recorded were 19, 22, 23, and 33 days. At the other end, 17% of the migrations in the sample had not returned to their pre-migration traffic level even after 1,000 days of tracking. A smaller group, 25 migrations (2.8%), were marked inconclusive: traffic reached the old domain’s level but never stabilized there.
That range matters more than the average by itself. A site planning a migration around “expect roughly a year and a half” is planning around the middle of a distribution that also contains a three-week recovery and a one-in-six chance of never getting there.
The same author ran an earlier version of the study in 2023, on 171 migrations, and reported an average of 229 days with 42% not returning to their old traffic level. The 2024 run expanded the dataset to 892 migrations and the average rose to 523 days. The two samples are not like for like, so the rise shows a larger and more varied dataset, not that migrations got slower.
What the study says about speed
The study does not report what the fastest migrations, at 19, 22, 23, and 33 days, did differently. Taylor’s own advice, drawn from experience rather than from the dataset, is to launch the new domain and URL structure 24 to 48 hours before implementing the redirects: Google rebuilds its index page by page, so it has already begun crawling the new paths in most cases. Using Google Search Console’s change of address tool, he adds, can smooth a lot of early migration lag.
On the slow side, a community member, Natalia Witczyk, proposed that recovery lag tracks backlink profiles: the profile has to be recrawled and the redirects reflected, which takes longer when it is extensive. Taylor then checked each domain’s referring-domain count and found some correlation, but with “a large number of outliers,” likely due to how the migration was carried out.
Why we care
The number worth planning around here is not 523, it is the range around it: weeks at the fast end, over 1,000 days and still not recovered for 17% of sites at the slow end, from the same set of migrations. The study does not explain what separated the two groups, so treat its timeline as a range to plan for, not a promise, and read Taylor’s launch-ahead and change of address advice as experience, not a measured result.
The evidence
- Subject
- How long domain migrations take to recover lost organic traffic
- Timeframe
- Data collated October 22, 2024
- Verified
- Yes, against first-party data
| Metric | Before | After |
|---|---|---|
| Average days to recover pre-migration organic traffic | n/adays | 523days |
| Migrations that never recovered within 1,000 days | n/a% | 17% |
Sources
- 1.How Long Should an SEO Migration Take? [Study] - Dan Taylor, Search Engine JournalPrimary
Common questions
How long does it take to recover organic traffic after a domain migration?
Per a Search Engine Journal study of 892 domain migrations, the average was 523 days, about 17 months, for the new domain to match the old domain's organic traffic. The fastest cases recovered in 19 to 23 days; 17% of the sample had not recovered even after 1,000 days.
What made the fastest recoveries different?
The study does not say. It lists the fastest times as 19, 22, 23, and 33 days. Separately, the author says from experience that launching the new domain and URLs 24 to 48 hours before implementing redirects, plus Search Console's change of address tool, can smooth early lag.
Does a bigger backlink profile mean a slower migration?
The author found some correlation between referring-domain count and recovery time, following a reader's suggestion that more links mean more recrawling. He flags a large number of outliers, likely due to how each migration was carried out.
Is 523 days the number every site should expect?
No. It is a sample average across migrations of very different quality. The same dataset contains recoveries in under a month and migrations that never recovered, so execution quality, not elapsed time alone, is what the data associates with the outcome.
About the author

Founder, UpgradIQ FZC LLC
Adam Hafez works on technical SEO and search measurement: how pages get crawled, indexed, ranked and now quoted by answer engines. He founded UpgradIQ, which reads Google Search Console and GA4 to tie ranking movement back to the changes that caused it. He publishes what the data supports and states the limits of it.
- Technical SEO
- Search Console and GA4
- Answer engine optimization
- Structured data
The briefing
Only what actually changed in search, delivered in full by RSS, Atom or JSON feed.
FollowRelated reading
Merchant Center feed fixes and three click gains, per Uproer
Uproer's published case study reports feed-level Google Merchant Center changes lifted clicks 130%, 116% and 3,500 for three unnamed ecommerce brands.
Log analysis cut a jewelry site from 16M to 730K crawlable pages
A JetOctopus case study: log files showed Googlebot spending crawl on filter, sort and pagination URLs, and closing them shrank the site to 730K pages.
Nuvemshop lifted good LCP from 57% to 96% by fixing image loading
Nuvemshop's web.dev case study: removing lazy loading on top images and adding fetchpriority took good LCP from 57% to 96% across its stores.
CoinStats: Good URLs and impressions up 3x
DebugBear's case study: CoinStats updated about 15,000 pages and moved off Base64 images; it reports Good URLs and their impressions up 3x.



