Google does not schedule core updates, but it does have a pattern. Over the last eight intervals the gap between core updates has averaged 82 days, with a range from 7 to 147. The counter below shows how long it has been since the last one completed and where that sits against the historical range. Use it to plan a reassessment window, not to expect a date.
Progress against the 82 day average gap between recent core updates.
These are averages of past behaviour, not a forecast. Google announces core updates when it announces them, and the gap has been as short as 7 days and as long as 147. Use it to plan a reassessment window, not to expect a date.
Recent gaps between core updates
Why the next core update date matters
For most sites it does not. For a site in recovery it is the single most important date on the calendar, because core ranking systems do not re-score your site continuously. They re-score it during a core update.
That means a site demoted in one core update sits at its demoted position no matter how good the fixes are, until the next core update runs and re-evaluates it. The work is under your control. The reassessment is not. Understanding that distinction is what separates a client who stays the course from one who panics into changes that make things worse, and it is covered in full in how long recovery takes.
How to use the window
- Work backwards from the earliest plausible date, not the average. Why: Gaps as short as 7 days have happened. If your highest-impact changes are not live when a rollout starts, they miss that cycle entirely and you wait for the next one.
- Ship in order of impact rather than in order of ease. Why: If an update arrives early, you want the important work already indexed rather than half of everything done.
- Freeze the site once the fixes are in. Why: Google reassesses the version it finds. Continuous editing means you can never attribute a result to a specific change.
- Confirm the changed pages have been crawled. Why: An improvement Google has not recrawled cannot be reassessed, so it does not matter that it shipped in time.
- Do not judge anything until the rollout completes. Why: Recent core updates have taken 12 to 24 days, and rankings move in both directions inside that window.
What the gap data does and does not tell you
The averages describe past behaviour. They are useful for planning and useless as a forecast, and it is worth being precise about why.
| What it tells you | What it does not | Measurement (the evidence) |
|---|---|---|
| Roughly how long a reassessment wait usually lasts | When the next update will actually run | 82 day average across the last eight intervals |
| That a very short gap is possible | That short gaps are likely | November and December 2024 core updates ran 7 days apart |
| That a long wait is not unusual | That a long wait means anything is wrong | 147 days between the June and December 2025 core updates |
| When to start watching for a rollout | Which sites the update will affect | Rollouts are announced on the Search Status Dashboard |
Google has never published a schedule and has said repeatedly that core updates ship when they are ready. Treat any specific predicted date, including the one on this page, as an average rather than an expectation.
How to know a rollout has started
Two signals, in order of reliability. The live update tracker syncs with the Google Search Status Dashboard twice a day, so a confirmed update appears there within hours of the announcement. The volatility sensor often moves first, because ranking turbulence usually shows up before Google confirms anything, and sometimes without any confirmation at all.
Watch both. High volatility with no confirmation means an unconfirmed adjustment, which behaves differently from a core update and is covered in the seven causes of a drop with no update.
Frequently asked questions
When is the next Google core update?
Google does not announce core updates in advance and has no published schedule. Based on the last eight intervals, the gap has averaged 82 days with a range of 7 to 147, so the counter above shows where the current wait sits against that history.
How often does Google run core updates?
Historically three or four times a year, though the spacing varies widely. Two ran seven days apart in late 2024, and a single gap in 2025 lasted 147 days.
How long does a core update take to roll out?
Recent ones have taken 12 to 24 days. Google marks the completion on the Search Status Dashboard, and rankings move in both directions during the rollout, so measuring before it finishes gives unreliable results.
Will my site recover at the next core update?
Only if the underlying cause has been fixed and the changed pages have been recrawled. Core updates reassess the site as it currently exists, so an unchanged site gets the same verdict repeatedly.
Should I make changes while a core update is rolling out?
Changes shipped during a rollout are sometimes picked up in the same rollout, so it costs nothing to have work already live. What you should not do is react to mid-rollout ranking movement, because it is not a final result.
Waiting for the next core update to fix a drop?
Waiting only helps if the cause has actually been addressed. Send your Search Console access and within 48 hours I will tell you whether your site is ready for the next reassessment or whether it will get the same verdict again. Free, no obligation.
Get free recovery audit