How do I know a Google update caused my drop?

Compare the date of the decline against Google's published core update dates. A core update rolls out over one to three weeks, so the drop is usually gradual. An overnight drop, or one that began before the update, points at something on your own site instead.

Is a core update the same as a penalty?

No. A penalty, properly a manual action, is a human decision at Google and always appears as a message in Search Console. A core update is an index-wide change in how signals are weighed, and targets nobody. If Search Console shows no message, there is no manual action.

Can rankings lost to a core update be recovered?

Sometimes, and nobody can guarantee it. Recovery depends on closing the gap against the pages that replaced you, and positions often do not return until a later core update reassesses the page. Treat any promise of guaranteed recovery by a fixed date as a warning sign.

Should I disavow backlinks after a core update?

Usually not. Disavow exists for manual actions and known toxic link campaigns. After a core update, Google has re-scored pages rather than acted against your links, and disavowing in bulk on suspicion can remove links that were helping you.

How long does recovery take?

Often until the next core update runs, which can be months rather than weeks, because the same scoring that demoted the page has to reassess it. Work done in the interim is what that reassessment reads.

2026-09-24 · 6 min read

My rankings dropped after a Google update. What now?

Short answer

A drop after a core update usually means Google re-scored your pages against competitors, not that you were penalised. Do not rebuild the site in week one. Confirm the dates line up with a known update, identify exactly which pages lost, and work on the signals behind those pages.

First, confirm the update is what hit you

Rankings move for many reasons, and an update is only one of them. Before changing anything, establish that the timing actually matches.

Open Search Console and compare the drop against the dates Google published for its last core update. A core update rolls out over one to three weeks, so the decline is usually a slope rather than a cliff. A drop that happened overnight, or that started weeks before the update, is a different problem — a server outage, a botched deploy, a robots.txt change, an expired certificate, a migration.

Did impressions fall, or only clicks? Only clicks means the layout of the results page changed, not your position
Did every page lose, or a specific group of them? A group points at a content or intent problem, not a site-wide one
Did the drop coincide with anything you shipped that week?
Is the page still indexed at all? A deindexed page is not a ranking problem

A core update is not a penalty

These get confused constantly, and the confusion leads people to fix the wrong thing.

A manual action is a human decision at Google to demote or remove a site, and it appears as a message in Search Console. If there is no message there, no manual action was taken against the site. Nothing was done to you.

A core update is a change to how Google weighs signals across the whole index. Nobody is targeted. Your pages were re-scored relative to every competing page, and some of those competitors now score better than they did. The result feels identical from the outside, but the response required is completely different.

Why core updates keep coming

Google ships core updates several times a year, plus continuous changes that are never announced. This is not an occasional disruption to normal conditions; it is the normal condition of the channel.

Anyone promising positions that never move is describing a search engine that does not exist. Ranking is a relative position in a set that is rescored constantly, and a competitor investing more than you is enough to move you down without anything on your site changing at all.

The practical consequence is that recovery work is not a one-off repair. Sites that hold position across updates are the ones with continuous investment behind them, not the ones that got everything right once.

What not to do in the first two weeks

The instinct after a drop is to change everything at once. That instinct destroys your ability to learn anything, because once ten things change together, no recovery or further decline can be attributed to any of them.

Specifically, avoid these while a rollout is still in progress:

Rewriting pages that were performing well — you may lose what was still working
Mass-disavowing backlinks on suspicion. Disavow is for manual actions and known toxic campaigns, not for core update volatility
Redirecting affected URLs somewhere else, which discards their history
Buying a large batch of links in a hurry, which adds a second variable on top of the first
Changing the domain

What recovery actually involves

Recovery starts with a comparison, not with edits. Take the queries where you lost the most, look at who now occupies those positions, and establish what they have that you do not.

In practice the gap is usually one of a small number of things: their page answers the query more completely, their page covers an intent yours only half serves, they have stronger or more relevant links pointing at that specific page, or their page is indexed and refreshed while yours is stale.

From there the work is ordinary and unglamorous. Strengthen the pages that lost, make sure the links pointing at them are indexed and actually passing value, and close the gap against whoever replaced you. None of this is a trick, which is exactly why it survives the next update.

How long recovery takes, honestly

Positions lost to a core update frequently do not return until another core update runs, because the scoring that demoted the page is the scoring that has to reassess it. That can mean months, not days.

Improvements made in the meantime are not wasted — they are what the next assessment reads. But anyone quoting you a fixed recovery date for a core update drop is guessing, and a specific number is a signal to be careful, not a reassurance.

We will not promise that lost positions come back. What can be promised is a diagnosis that tells you which pages lost, why, and what closing the gap would take.

When to bring in help

If the drop is small, limited to a few pages, and you can see what changed, handling it in-house is reasonable.

Bring in someone when revenue is affected and the cause is not obvious, when the same pages keep sliding across successive updates, or when the gap against the sites that replaced you is a link gap rather than a content gap — that one rarely closes on its own.

Frequently asked questions

How do I know a Google update caused my drop?: Compare the date of the decline against Google's published core update dates. A core update rolls out over one to three weeks, so the drop is usually gradual. An overnight drop, or one that began before the update, points at something on your own site instead.
Is a core update the same as a penalty?: No. A penalty, properly a manual action, is a human decision at Google and always appears as a message in Search Console. A core update is an index-wide change in how signals are weighed, and targets nobody. If Search Console shows no message, there is no manual action.
Can rankings lost to a core update be recovered?: Sometimes, and nobody can guarantee it. Recovery depends on closing the gap against the pages that replaced you, and positions often do not return until a later core update reassesses the page. Treat any promise of guaranteed recovery by a fixed date as a warning sign.
Should I disavow backlinks after a core update?: Usually not. Disavow exists for manual actions and known toxic link campaigns. After a core update, Google has re-scored pages rather than acted against your links, and disavowing in bulk on suspicion can remove links that were helping you.
How long does recovery take?: Often until the next core update runs, which can be months rather than weeks, because the same scoring that demoted the page has to reassess it. Work done in the interim is what that reassessment reads.