Short answer
The May 2026 core update completed on 2 June. As of late October, Google has confirmed no core update since. That is the longest core update gap in over three years. If you were demoted in May, you have been waiting roughly five months for a reassessment that has not arrived.
This is the most consequential fact in SEO right now and almost nobody is writing about it, because an absence is harder to notice than an event.
The gap, in context
From my own update tracker, measured as the end of one core update to the start of the next.
| Period | Gap |
|---|---|
| May 2020 to December 2020 | 199 days |
| November 2021 to May 2022 | 176 days |
| September 2022 to March 2023 | 170 days |
| June 2025 to December 2025 | 147 days |
| May 2026 to now | 148 days as of 28 October 2026, still open |
| November 2024 to December 2024 | 7 days |
The current wait has already passed the 2025 record. Longer gaps exist, but all three are from 2020 to 2023, before the recent pattern of two or three core updates a year.
Two core updates in 2026 so far. There were four in 2023.
Why the silence matters
Core ranking systems re-score sites during core updates, not continuously.
So if a core update demoted you in May, every improvement you have made since has been sitting unassessed. Not ignored, not rejected. Simply not yet looked at.
That is the part clients find hardest to accept, and it is why five months of good work can produce a completely flat graph.
Google itself put a number on this
On 2 October 2026, Google published timing guidance stating that recovery after a core update typically takes three to six months.
That figure is worth quoting to anyone asking why nothing has moved. It comes from Google, not from an agency managing expectations.
It also matches what I see. Full recovery reaches roughly three engagements in ten, and the ones that get there rarely do it inside a quarter.
What has been running instead
Plenty. None of it reassesses a core demotion.
- Three spam updates since May: June, August and September. Different systems, different standards.
- Guidance changes on 1 October covering AI content and author profiles. Documentation, not a ranking release, but worth acting on: Google now calls fake author profiles deception.
- Unconfirmed volatility, which my sensor records whether or not Google announces anything.
Watching a spam update hoping to recover from a core demotion is the most common wasted effort I see. It happened through the August 2025 rollout and it is happening again now.
What to do with the wait
- Get the work shipped and crawled now. Only what exists when the rollout starts gets assessed.
- Then freeze the structure. Ordinary publishing is fine. Templates, URLs and indexing settings are not.
- Record your baseline in writing before the next update, not after it.
- Do not rebuild twice. Two rebuilds in one gap means you will never know which version was judged.
The full discipline is in how long should I wait before doing anything, and the live gap is on the core update countdown.
A caution about predictions
Several commentators expect a core update imminently. That is speculation, not an announcement.
The intervals in the table above run from 7 days to 199 days. Any plan built on an expected date is built on an average that the actual data does not respect.
Plan around readiness instead of timing. Readiness is the only part of this you control.
What followed the previous long gaps
Long gaps have ended in ordinary updates, not unusually severe ones. From the tracker:
- June to December 2025, a 147 day gap. It ended with the December 2025 core update, which ran for 18 days.
- September 2022 to March 2023, a 170 day gap. It ended with the March 2023 core update, 13 days long, and a second core update followed only five months later.
- November 2021 to May 2022, a 176 day gap. It ended with the May 2022 core update, which took 15 days.
Nothing in the record suggests a long wait produces a bigger update. The rollouts that ended each gap sat close to the core update median of 14 days.
What does change is how much unassessed work has built up. Sites that kept improving through a long gap often move further when the next update arrives, simply because more has changed since they were last judged. That cuts both ways: sites that kept publishing weak pages through the gap have more to answer for too.
The practical point is unchanged. Be finished before the rollout starts, then measure 28 days after it ends.
The number in this title keeps growing. Every day without a confirmed core update adds to it, and the live count is on the core update countdown.
Down since May and nothing has moved?
That may mean no reassessment has happened yet rather than that your work failed. The two look identical in a flat graph. Send your Search Console access and within 48 hours I will tell you whether your site is ready for the next window.
Get free recovery auditThe rollout lengths behind these gaps are measured in how long Google updates actually take.