How long does a Google core update take to roll out?

The two week figure is the one Google publishes, and it causes a specific and expensive problem. Two weeks is long enough that people stop waiting. Somewhere around day four, traffic is down, someone senior asks what is being done about it, and a team starts rewriting pages against a baseline that is still moving. By the time the rollout finishes, nobody can separate what the update did from what the panic did.

So it is worth being precise about what the clock actually looks like, and what each part of it means for the decision in front of you.

How long do Google core updates last?

Between one and two weeks, with two weeks as the stated ceiling. The pattern in 2026 has been remarkably consistent: both confirmed core updates this year took 12 days from announcement to completion. That is slightly faster than some of the longer rollouts of previous years, which occasionally stretched past three weeks, but it is close enough to the ceiling that planning for two weeks is the right assumption.

Google announces both the start and the completion on its Search Status Dashboard and its Search Central social accounts. The completion notice is the one that matters, because it is the only reliable marker that the numbers you are looking at have stopped being provisional.

Why do rankings move up and down during a rollout?

Because a core update is not flipped on everywhere at once. It propagates across data centers and across the index over days, so different queries and different locations get the new ranking behavior at different times. A keyword can genuinely sit at position 4 on Monday, 11 on Wednesday and 6 on Friday, and none of those three numbers is the answer.

Recent rollouts have also shown distinct waves rather than a smooth ramp. Practitioners tracking the May 2026 update reported several separate spikes of movement across the 12 days rather than one continuous slide. If you happened to measure on a quiet day between spikes, you would have concluded you were unaffected, and been wrong.

This is the argument for daily measurement over weekly. A daily rank tracker gives you 12 data points across a 12 day rollout, so the shape of the movement is visible. A weekly check gives you one or two, which is not enough to distinguish a spike from a trend or to date the start of anything.

Should I make changes during a Google core update?

Avoid anything you would need to measure. Google is direct about the small-drop case, saying there is "no need to take drastic action" and specifically recommending "avoiding making changes to content that's already performing well". The practical reason is measurement, not superstition: a change made on day three gets evaluated against a moving baseline, so you will never learn whether it worked.

Routine work is fine. Keep publishing on your normal schedule, keep fixing genuine bugs, keep shipping the things you were going to ship anyway. What to postpone until the rollout completes is the reactive category: rewriting titles across a section, rolling back a recent migration, deindexing pages, consolidating URLs, or gutting a page that dropped. Those are all decisions you want to make against a stable measurement.

When should I check if a core update affected my site?

Google's guidance is to wait "at least a full week after a core update completes before analyzing your site in Search Console", and then to compare "this week with a week before the core update started rolling out". For the May 2026 update, which completed June 2, that meant the first honest read was around June 9, comparing against the week ending May 20.

Notice what that comparison requires: clean ranking data from the week before the update started. You cannot create that retroactively. Teams that begin tracking after they notice a problem have no before, and end up arguing from Search Console's averaged position, which blends locations and devices and is a different measurement from a daily rank check rather than a more convenient version of one.

How long does it take to recover from a core update?

Months, not weeks, and often not until the next core update. Google says "some changes can take effect in a few days, but it could take several months for our systems to learn and confirm that the site as a whole is now producing helpful, reliable, people-first content". It adds that if "it's been a few months and you still haven't seen any effect, that could mean waiting until the next core update".

Since core updates arrive roughly every three to four months, that is the realistic planning horizon. Sites hit in May 2026 that made substantive improvements through June and July are mostly waiting on the next broad update, expected in the third quarter, for the reassessment to land. The work in between is content, not tracking: the pages that come back are the ones that got materially better, and teams tend to get further by improving what already has ranking history than by putting fresh articles on a consistent schedule and hoping volume covers the gap. Both help. Only one of them compounds on the pages that already dropped.

How often does Google release core updates?

Several times a year, in practice every three to four months. In 2026 the confirmed core updates were March and May, alongside a spam update in March and a Discover-specific update in February. Following that cadence, the next broad core update is expected in the third quarter of 2026.

It is worth separating this from ordinary ranking churn, which happens constantly and has nothing to do with announced updates. Google refreshes its index continuously, and positions shift daily for reasons that never get a name or a dashboard entry. There is a fuller treatment of that cadence in how often Google updates rankings.

How do I know it was a core update and not something else?

Line up three things: the date your rankings moved, the date any announced update started, and what the volatility sensors were reading that week. If your drop began four days before a rollout was announced, the update is not your explanation and you should keep looking. Most drops are not core updates. They are a lost link, a technical regression, a competitor who published something better, or a SERP layout change that pushed the organic results down the page.

The free volatility checkers tell you whether the index at large was moving, but not whether you were, because your keywords are not in their samples. There is a full comparison of what each one measures on our SERP volatility tracker page, including where the aggregate score structurally cannot help. For working through the non-update causes in order of likelihood, start with why Google rankings drop.

The short version

Plan for two weeks of rollout, then one more week of waiting before you look. Both 2026 core updates took 12 days. During the window, keep working normally and postpone anything reactive, because a moving baseline makes every change unmeasurable. After the completion notice plus a week, compare that week against the week before the update began. If you are down, expect the recovery timeline to run in months and to depend on real content improvement rather than on waiting.

The one thing you cannot do at the end is manufacture the before. Continuous daily tracking is what makes the comparison Google recommends possible at all, and it is a lot cheaper to have running than to wish you had. Our plans start at $39 a month for 250 keywords checked every day, with drop alerts the day a position moves rather than at the end of the month.