How Long Does Google Take to Process a Site Migration?
Nobody can tell you. The organisation actually doing the processing says so in its own documentation. What we can give you instead is what determines it, what a normal pattern looks like and what would genuinely warrant investigating rather than waiting.
There Is No Number
We will not give you a period. It is worth being clear that this is a refusal rather than an evasion. No published source supports a figure, while the organisation doing the work says there are no fixed frequencies.
What the documentation states. Checked August 2026.
The vendor's own site move guidance says that for a move to be considered complete, every address on the old and new site has to be visited at least once. It states plainly that there are no fixed crawl frequencies, with speed depending on the size of the site and the crawling speed possible.
Why that settles it. They would know.
If anybody could state a processing period, it would be the organisation doing the processing. It declines to. That is stronger evidence against every figure in circulation than any argument we could make.
What to do with a quoted figure. Ask where it came from.
Plenty of pages will tell you a number of weeks. If the source is somebody's experience of their own sites, that is a description of those sites rather than of yours.
What follows instead. Something more useful.
What moves the timescale, what the process actually looks like and what would warrant acting.
What Actually Determines It
The useful version of the answer is what the timescale depends on. Four things do. Two are within your control, which is where attention is worth spending.
How many addresses there are. The dominant factor.
Every address on both the old and the new site has to be visited. A site with tens of thousands of them has more to get through than one with fifty. No amount of anything changes that arithmetic.
How often the site is normally visited. Not within your control.
A site that is crawled frequently gets through its addresses faster than one that is visited rarely. That reflects the site's existing standing rather than anything about the migration.
How clean the redirects are. Within your control.
Every old address arriving at its destination in one step is the fastest version of this. Chains, errors and missing entries all add work.
Whether anything else is changing. Also within your control.
A site being altered while it settles is a moving target. That is block six. It is the one people get wrong while waiting.
What Happens Gradually
A migration is not one event with a completion date. The same documentation states that a move takes place on a per-address basis, which changes the question entirely.
What that actually means. Thousands of separate events.
Each address moves when it is visited and its redirect received. Your most important page might be processed on day one. An old page nothing links to might wait considerably longer. Neither is waiting for the other.
Why no single figure could exist. There is no single moment.
Asking when a migration completes is asking when the last of thousands of independent events happens. That is not one number. Treating it as one is why the question feels unanswerable.
What this predicts. Uneven recovery.
Sections returning at different times, some pages behaving normally while others have not moved. That is the expected shape rather than a symptom of anything.
Why it is reassuring. Partial progress is progress.
Some things working and others not is what the middle of this looks like, rather than evidence that something has gone wrong.
What A Normal Pattern Looks Like
Described as a shape rather than a schedule, because the shape is the part that generalises. A decline, then a period of movement, then a gradual return.
The initial drop. Expected.
Performance falls shortly after launch. That is the normal consequence of a site changing. Its presence tells you nothing about whether anything is wrong.
The unstable period. Also expected.
Movement in both directions, pages appearing and disappearing, sections behaving inconsistently. This is what per-address processing looks like from outside. It is the phase people find hardest.
The gradual return. The part that matters.
Direction is the signal worth watching. Something recovering slowly is behaving normally regardless of where it currently sits.
What to watch rather than levels. Which way it is going.
A single reading on a single day tells you almost nothing. The trend across a fortnight tells you nearly everything, per monitoring after migration.
When To Start Worrying
Telling somebody to be patient without telling them what would warrant concern is unhelpful. Three things are worth acting on rather than waiting out. None is defined by a period.
A decline that keeps deepening. The direction is wrong.
Settling looks like decline then stabilisation then return. Something still falling well after launch is not following that shape. The shape is the diagnostic rather than the timing.
Complete flatness. No movement in either direction.
Instability is a sign of processing. A perfectly flat line at a lower level, with nothing moving, can mean nothing is being processed at all.
Old addresses returning errors. Not a waiting problem.
This is a mapping gap and it will not improve with time. It is the one thing on this page that should be checked immediately rather than watched.
What to do first. Verify rather than wait.
Check what the site is telling crawlers and whether redirects behave. Both take minutes and both are more useful than another week of watching.
Do Not Keep Changing Things
Every change made while waiting restarts the reading. The instinct to act is understandable and it is the most reliable way to turn a recoverable situation into an unreadable one.
Why the instinct is strong. Waiting feels passive.
Performance has dropped, somebody is asking about it and doing nothing feels like negligence. Changing something feels like responding, particularly when there is nothing else to report.
What each change costs. The comparison.
The settling period is the one time when movement has a single known cause. Introduce a second and neither can be separated from the other afterwards.
What it compounds into. A site nobody can diagnose.
Several well-meant changes across a few weeks produces a site where nothing can be attributed to anything. At that point even a competent diagnosis has nothing to work with.
What to do with the impulse. Write it down.
Keep a list of everything you want to change and do it once the site has settled. Nothing on that list is urgent, while having a list is itself a form of acting.
What Speeds It Up
Four things genuinely help. None transforms the timescale and all are worth doing, which is the correct expectation to set rather than an underwhelming one.
Clean redirects. The largest of the four.
Every old address arriving in one step, with no chains and no gaps. This is also the thing most likely to be imperfect.
Submitting the new address list. A direct route.
It brings forward the discovery of new addresses rather than waiting for them to be found by following links.
Keeping the old list available briefly. The counterintuitive one.
It helps old addresses get revisited so their redirects are received, which is how each individual move completes.
Updating important external links. Slow but real.
A direct link reaches the destination without a redirect at all. The notification steps are in notifying Google of a migration, recovery timescales are in how long rankings take to recover. The full series is on the website migration guide.
Nobody knows.
Including
them.
No period quoted because none can be supported, the shape watched rather than a single day's reading, the three things that genuinely warrant acting separated from the ones that only warrant waiting, every impulse to change something written down instead of acted on, with the redirects checked rather than the calendar.
What a migration engagement covers:
A migration is a one-off project rather than a monthly service, so it is scoped and quoted against the size of the site and how much is changing at once.
Every guide.
One practice.
What a migration is, the types, when to do it, planning, the checklist, auditing, mapping, redirects, internal links, tags, downtime, crawling, structured data, performance, notifying, monitoring, recovery and the mistakes.
