At Search Central Live in Barcelona on October 2, Google’s Gary Illyes reportedly gave typical timing ranges: 1 to 3 months for a site move, and about 3 to 6 months to recover from a core update. The slowest cases run 6 months to over a year for both. These are reference ranges from a recap, not promises, so use them to set expectations and to stop making panic changes every week.
What Google reportedly said
According to a recap by John Campbell of ROAST, shared in Search Engine Journal’s SEO Pulse, Illyes described two sets of timing. For site moves, the typical case takes 1 to 3 months, while the slowest cases take 6 months to more than a year. For recovery after a core update, the typical case is about 3 to 6 months, with the slowest cases taking 6 months to a year.
The recap does not give a sample size, a time period, or a definition of what counts as typical. That is why these numbers are best read as ranges to plan around, not deadlines Google has committed to.
Why this matters right after the spam update
Google just finished its September 2026 spam update on October 8, after roughly 13 days and 16 hours, much longer than the three earlier spam updates this year. Many site owners are now looking at flat or lower traffic and wondering how fast it will come back. If you are in that group, our guide to the first 7 days after the spam update covers what to read first. Keep in mind that the ranges above were about core updates and site moves, so a spam-policy fix may follow its own timeline.
The real risk is changing too much too soon
When recovery takes months, the common mistake is to keep rewriting, deleting, and migrating every week. That makes it hard to tell what worked, and a site move layered on top of a recovery effort adds a second long timeline. Change one meaningful thing at a time, log the date, and give each change enough time to show up in Search Console before you judge it.
It also helps to separate a ranking problem from a penalty. If Search Console shows a notice, you are dealing with a manual action, covered in our post on what to check when Google issues more manual actions, and the fix has to be proven to Google. If there is no notice, you are waiting on algorithmic reassessment.
Where SEO, AEO, and GEO meet
Slow recovery is also an AI visibility story. Answer engines and AI Overviews lean on pages Google already trusts, so a site that is still recovering is a weaker source for citations too. Building real author credit, verified facts, and clean structure helps your rankings, your answer box chances, and your AI citations at the same time. That is why we treat SEO, AEO, and GEO as one framework.
Your recovery planning checklist
- Write down your start date. Record the day the drop began or the move launched, so you measure against a real baseline.
- Match your situation to the right range. A site move is 1 to 3 months typically. A core update recovery is about 3 to 6. Do not mix the two.
- Fix the cause once, thoroughly. Improve the weak pages or finish the migration cleanly, and avoid small tweaks every few days.
- Check Search Console on a fixed schedule. Review Performance and Indexing every two weeks, not daily, and compare against your baseline.
- Keep a change log. Note each fix with its date so you can link movement to a specific action.
- Plan cash flow for the slow case. If your business cannot wait six months, support it with other channels while organic recovers.
The bottom line
Google’s reported ranges say recovery is a matter of months, not days, and the slowest cases can take a year. Use them to plan, change things deliberately, and measure on a calendar instead of reacting to every ranking tool wobble.
If you want help planning a recovery or a safe site move, our SEO services include a Search Console review and a written timeline. You can also see how we connect SEO, AEO, and GEO at GCL Marketing, or browse more articles by topic.
Frequently Asked Questions
How long does a Google site move take to recover?
Google’s Gary Illyes reportedly said 1 to 3 months is typical, with the slowest cases taking 6 months to more than a year.
How long does core update recovery take?
About 3 to 6 months in the typical case, and 6 months to a year in the slowest cases, based on a recap of the October 2 session.
Are these timelines guaranteed?
No. The recap does not include a sample size or a definition of typical, so treat the numbers as reference ranges, not deadlines.