How Often Does Google Update Its Algorithm?
Many times a day, almost none of it announced and almost none of it anything to do with your site. This guide covers what actually changes, what a core update reassesses and what to do while one is in progress, which is usually nothing at all.
Constantly And Mostly You Will Never Know
Google changes how Search works many times a day. The overwhelming majority of those changes are never announced, never noticed and never discussed by anybody. This is normal operation rather than a sequence of events. Understanding that before anything else changes how you read every fluctuation you will ever see in your reporting.
How many changes there are. Thousands a year.
Google has published figures on this repeatedly, describing more than five thousand improvements to Search across 2021 alone. Testing, evaluation and small refinements run continuously. There is no version number and no release night.
Why the gap is that wide. Most changes are too small to see.
Google's own documentation on core updates states that smaller core updates happen continually and are not announced because they are not widely noticeable. So the quiet ones are not being hidden from you. They are simply not events.
Why this guide opens here. It reframes the question.
Most people arrive at this subject after something moved, wanting to know which update did it. Frequently no update did. Working out whether an update caused a drop is a separate exercise with a proper method. It starts by ruling out the ordinary explanations first.
What A Broad Core Update Actually Is
A broad core update is a periodic reassessment of how quality is judged across everything Google ranks. It is not aimed at a behaviour, an industry or a site. It is a recalibration of the whole judgement, applied to billions of pages at once.
Why so many sites move at once. The standard moved, not your site.
Your pages are the same pages they were the previous week. What changed is the assessment being applied to them, plus the strength of everything competing for the same searches. Both of those sit outside your control.
Why a site that did nothing can still fall. The judgement is comparative.
If competitors have published materially better answers since the last reassessment, a page that stood still can lose ground without anybody having done anything wrong to it. This is the part businesses find hardest to accept and it is the part that explains most of what they see.
What Google says site owners should do. Nothing special.
The standing guidance published with these rollouts is that there is nothing new or particular that creators need to do, provided they have been making satisfying content meant for people. That has not changed across years of these announcements.
Nothing Was Done To You
A core update is not a penalty. Nothing was applied to your site, no notice was issued and there is nobody to appeal to. We state this early because it decides everything that follows, including whether a business spends the next year removing things that were never the problem.
What a penalty actually is. Something applied to one site.
A manual action is a person or a system acting against a specific site for a specific breach of published policy. It arrives with a notice in Search Console and it has a process for resolving it. Our material on risky practices covers that route properly.
Why the distinction is not word play. The two demand opposite responses.
A penalty means identifying something and undoing it. A core update means becoming a better answer than you were. One is a removal job and the other is an improvement job. Choosing wrongly wastes months.
Where the fuller argument sits. On the recovery page.
The consequences of this position take a page of their own to work through. How to recover from a Google algorithm update sets out what improvement actually involves and why it is slower than a fix.
Core Updates Against Targeted Updates
Not everything called an update is the same kind of thing. Some address one specific behaviour. Others reassess quality broadly. Working out which sort you are looking at changes what you should do, so it is worth ten minutes rather than a guess.
What a targeted update does. Addresses one behaviour.
Spam rollouts are the clearest example. They enforce published policy against particular tactics, they are usually described in terms of what they detect and they are recurring rather than one-off events.
Why it changes your response. One of them has a fault to find.
If a rollout addressed a behaviour and your site engaged in that behaviour, there is something identifiable to deal with. If a broad reassessment moved you, there is nothing to find and the work is comparative instead.
Where this gets genuinely difficult. Overlapping rollouts.
In March 2026 the Search Status Dashboard recorded a spam rollout beginning on 24 March and a core rollout beginning on 27 March. Anybody who moved in that window had two candidate causes and no clean way to separate them, which is a good reason to be cautious about confident diagnoses.
What Is Confirmed And What Is Not
A small number of changes are announced as they begin. A few more get acknowledged after the fact. The vast majority are never mentioned by anybody at Google. A great deal of what circulates as an update is therefore inference rather than confirmation. The difference is worth holding onto.
Where confirmation appears. Two published places.
Named ranking rollouts are posted to the Search Status Dashboard as they start and marked when they finish. Google also maintains a ranking release history page listing them. If a rollout is not in either, it has not been confirmed.
What most update chatter is built from. Third-party volatility measures.
Various companies track how much search results are moving across large sets of keywords. When those measures spike, the industry reports an unconfirmed update. That is a reasonable signal that something changed broadly. It is not a statement from Google and we never present it as one.
Why an unconfirmed change is still real. Confirmation is a courtesy.
Google does not owe anybody an announcement and does not make one for most changes. So the absence of confirmation tells you nothing about whether something happened. It only tells you nobody official has said so.
What to do with an unconfirmed report. Treat it as a prompt.
Check whether the movement is industry wide or specific to you. That single question is the most useful thing these third-party measures can help with. The diagnosis guide works through it properly.
Where The Official Information Comes From
There is an official channel for this information and everything else is interpretation of it. Knowing which is which saves you from acting on somebody's reading of somebody else's guess. This block carries a date because the arrangement has changed recently.
What Search Liaison was. A public role.
Google created the Search Liaison position in 2017 and Danny Sullivan held it, explaining how Search worked and answering site owners directly on a public account.
What changed and when. The account closed on 1 August 2025.
Sullivan moved to another role inside Google's Search team and the public Search Liaison account was retired, with a closing message directing site owners to Search Central instead. Anybody still telling you to follow that account is working from old information.
Where the authoritative material sits now. Search Central and the dashboard.
The Search Central blog and documentation carry the guidance. The Search Status Dashboard carries named rollouts and their state. The ranking release history page carries the record. Those are the sources we check first and the ones worth checking yourself.
A Rollout Is Not A Moment
An update does not land at once. It is applied progressively. Positions move in both directions throughout that period. Almost every wrong conclusion drawn about an update comes from somebody reading their reporting while the rollout was still in progress.
What Google publishes about timing. An estimate.
Each named rollout usually arrives with an expected period attached, described as an estimate rather than a commitment. Some complete earlier than stated and some run beyond it. We do not quote a duration as fact anywhere on this site, because it varies by rollout.
What happens while it runs. Movement in both directions.
A page can drop sharply in the first days, recover most of it later and finish roughly where it started. Another can rise early and settle lower. Mid-rollout position data describes a state that no longer exists by the end.
How to tell it has finished. The dashboard says so.
Google marks a rollout complete on the status dashboard and updates the ranking release history. That is the point at which your numbers start describing a settled outcome rather than a moving one.
Do Not Act During A Rollout
If an update is in progress, the correct response is to record where you stand and wait. Changing the site while the ground is moving destroys your ability to read what happened. Reactive editing of pages that were performing well is the commonest self-inflicted damage in this whole subject.
Why waiting is not passivity. It protects the evidence.
Two things are changing at once if you edit mid-rollout: the assessment and your site. Afterwards you cannot tell which produced the outcome, so you have lost the one chance to learn something from an event you did not choose.
Why small drops deserve no drastic action. Proportion matters.
Google's published guidance makes this point directly, that a modest slip does not warrant a dramatic response. A page moving from second to fourth has not been condemned. It has been reassessed alongside everything else.
What to do instead. Document the position.
Export your Search Console data before it ages out of the comparison window. Note the rollout dates. Record which pages and which query groups moved. That record is what makes diagnosis possible later and almost nobody keeps it.
When to start looking properly. After completion.
Once the rollout is marked finished and a settled period has passed, the diagnosis method becomes worth applying. Before that, it is guesswork with better presentation.
Most Updates Will Not Affect You
A business doing careful work for real customers passes through the overwhelming majority of these changes without noticing that anything happened. That is not comfort offered to close a page. It is what the record of the last decade shows.
Which sites actually move. The ones near a line.
Sites built on volume without substance, on tactics that were always borderline or on being the least bad option in a weak set of results. When the assessment tightens, those are the positions that were never secure.
Why the direction is predictable even though the specifics are not. It has not varied.
Every significant update over more than a decade has moved the same way, towards judging whether a page genuinely serves the person who searched. The history of these updates reads as one continuous argument once you look at it that way.
What that gives you to aim at. Something better than preparation.
You cannot prepare for a specific update and anybody selling that is selling a guess. You can be the sort of site that updates do not trouble, which is a different and achievable objective. Preparing your website for future updates sets out what that involves.
Where to go next. Depends what brought you here.
If something moved, start with the diagnosis guide. If you already know it was a rollout, the recovery guide is next. The full series sits on the Google algorithm updates guide.
Nothing was
applied to your site,
so there is nothing
to undo.
That single distinction decides whether the next six months are spent stripping a site back or making it worth ranking. We have never had to undo anything on a site we built, because we build the same way whether or not a rollout is expected.
How we work through one of these:
If your positions have moved and nobody has explained why, start with the diagnosis guide rather than a rebuild.
Every guide.
One position.
How updates work, the history of what each one changed, whether a drop came from an update at all, what recovery genuinely involves, what helpful content means now and how to build a site that rollouts leave alone.
Written to talk you down rather than agree with the panic.
