Google updates: diagnose before you fix
Google changes its ranking thousands of times a year, but only the major updates produce a visible swing. What costs money is not the drop, it is the rushed fix: rebuilding pages that were still working. The first step is to confirm an update is really the cause before you touch anything.
- Most drops blamed on an algorithm come from a technical problem or a competitor that moved ahead.
- A major update rolls out over several weeks. Judging on the third day leads to wrong decisions.
- Core updates do not penalize specific techniques, they reassess relative quality.
- The risky practices have stayed the same for fifteen years, and they always get detected in the end.
- A drop in sessions is not a drop in leads. Check both before you commit a single dollar to a fix.
On this page
Core update
A core update is a significant change to Google's ranking systems, rolled out several times a year and announced publicly. It does not target particular sites and does not penalize specific techniques. It reassesses the relative quality of content, which can push a site down without it having changed anything, and without any fix spending being justified.
Not all updates are equal
The question a management team asks is never what Google changed. It is how much this is costing us, and whether we have to spend to fix it. Both answers depend on the type of update involved, and most fix budgets are committed before that point is settled.
If your first reflex facing a drop has ever been to edit pages, the outcome is probably familiar: the decline continued, and you lost what was still working. A traffic drop is diagnosed like a fall in output on a production line. You first look at what changed in the input, you do not take the machine apart.
The word algorithm covers very different things, and confusing the categories leads to bad spending decisions. A penalty gets fixed, a reassessment gets waited out, a continuous adjustment gets ignored. The budget to commit is not the same in the three cases, and it is zero in the third.
| Type | What it does | Appropriate response |
|---|---|---|
| Core update | Reassesses the relative quality of all content | Wait for the rollout to finish, then analyze |
| Spam update | Targets specific manipulative practices | Identify and remove the practice at fault |
| System update | Changes one component, reviews, helpful content, experience | Check whether the component applies to you |
| Continuous adjustment | Thousands a year, unannounced | None, they are invisible individually |
| Manual action | Human penalty, notified in Search Console | Fix it, then request a review |
A manual action always appears in Search Console. If no notification is there, the drop is not a penalty. It is the first thing to check, and it takes thirty seconds.
What to check before approving a fix
A core update rolls out over one to three weeks. Judging on the third day means deciding on a third of the information, and it is the moment when most fix budgets get committed. Three causes must be ruled out before concluding an algorithm effect, and two of them can be checked in under an hour.
- Does Search Console show a manual action, and on what date was it checked?
- Does the drop hit every page or a single family, and which one?
- What changed on the site in the six weeks before the drop, on the technical side as well as the editorial side?
- Did our competitors move up on the same queries, or did the whole market slip?
- How many leads did we actually lose, and on which pages?
A good answer separates the drop in sessions from the drop in leads, gives a rollout date, and names what was ruled out. An evasive answer announces a Google update and offers to re-optimize the content.
Deciding whether to act now or wait for a rollout to finish is a trade-off worth a few weeks and a few thousand dollars. A 90-minute consultation settles it, with a written summary you can circulate through your organization.
Diagnosing a drop before concluding
The usual sequence is expensive: traffic drops, someone searches for a Google update and is bound to find one, management approves a fix budget, and the team edits pages. A few weeks later, the situation is worse and the money is spent.
Three causes must be ruled out before invoking an algorithm. The first two can be checked without spending a dollar.
A technical problem
A noindex tag that appeared after a release, a robots file rule that is too broad, server errors, a drop in indexing. The Search Console indexing report settles the question in a few minutes.
A change in measurement
A tracking tag removed during a redesign, a domain change, a filter modified in the analytics tool, seasonality. A drop in measured traffic is not always a drop in real traffic.
A competitor that moved ahead
You did not decline, a competitor moved past you. It is the most frequent cause and the least often considered, because it does not show up in your own data. It is also the only one of the three that calls for an investment decision rather than a fix.
Once these three causes are ruled out, the question becomes precise: does the drop coincide with a rollout window confirmed by Google, and does it hit the whole site or only one family of pages? A drop concentrated on one content type points to a targeted reassessment, not a global problem, and the difference between the two is measured in weeks of billed work.
One thing has to stay in-house and is never delegated: the change log. Who changed what, on which page, on what date, on the content side as well as the technical side, including work done by a hosting provider or a developer. Without this log, an honest diagnosis is impossible and you end up blaming Google for what an internal change caused. The rest can be delegated: the competitive comparison, the reading of crawl reports and the correlation with rollout dates call for tools and daily practice.
How to respond to a core update
The first decision is to decide nothing right away. Reacting within the week almost always costs more than waiting for the diagnosis.
Google's official answer has been consistent for years: there is nothing to fix, because nothing is broken. A core update reassesses relative quality, which means a site can drop without having done anything wrong.
It is frustrating, but useful for deciding: it rules out the pointless fix spending and focuses the budget on the right questions.
The reach of this answer is financial before anything else. The four reflexes in the table below each cost billable production time, and three of them destroy value already earned. Committing nothing during a rollout is often the most profitable decision of the quarter, and it is the hardest to defend to a management team watching its sales fall.
| Reflex | Likely result | What to do instead |
|---|---|---|
| Editing pages during the rollout | Impossible to know what caused what | Wait for the confirmation that it has ended |
| Deleting the pages that dropped | Permanent loss of authority and links | Understand why they dropped |
| Adding content everywhere | Dilution, no targeted improvement | Strengthen the pages that matter |
| Changing title tags in bulk | No effect on a core update | Compare against the pages that moved ahead |
The only analysis that pays off is to take ten lost queries and examine the pages that replaced you. In almost every case, they answer more completely, more directly, or with proof you do not have. It is editorial work, not technical.
It is also the only defensible spending during this period. It produces an asset that stays useful even if the drop had an entirely different cause, unlike a technical overhaul launched in a rush, which is never recovered.
A recovery after a core update usually does not happen before the next update, because the reassessment takes place at those moments. Promising a return in two weeks is dishonest, and a budget committed on that promise is a budget lost.
The risky practices, which have not changed
Manipulative techniques evolve on the surface and stay identical in principle. Google groups them under its spam policies, and they always get detected in the end, because they leave recognizable statistical patterns.
The risk is not a fine. It is the disappearance of an entire acquisition channel, overnight, with no warning and no replacement budget planned. A company that gets half its leads from organic search has to treat this risk the way it would treat losing its main supplier.
| Practice | Why it gets detected |
|---|---|
| Hidden or off-screen text | Gap between the rendered page and the source code |
| Mass-generated pages with no value | Volume, similarity and lack of engagement |
| Buying links in bulk | A profile that appeared too fast from unrelated sources |
| Content copied from elsewhere | Duplication detection across the web |
| Redirects that differ by visitor | Comparison between the crawl and the browser |
| Parasite pages hosted on a third-party domain | Topical mismatch with the host domain |
The question to ask is not whether you will get caught. It is whether this page would exist if search engines did not exist. If the answer is no, it is at risk, whatever its form, and that risk sits on the balance sheet of a company whose acquisition depends on this channel.
A core update penalizes no one. It simply changes the order of those who answer best.
Falia analysis gridThe six checks that follow take half a day and cost less than the first hour of a fix launched by mistake.
What to do when traffic drops
The technical checks are detailed in what blocks a site in search. The general framework of search is laid out in the four layers of search, and the execution on the SEO agency page.
Already running a marketing team? See how we plug in as reinforcement on organic search.
Frequently asked questions about Google's algorithms
What is a Google core update?
It is a significant change to the ranking systems, rolled out two to four times a year and announced publicly. It does not target particular sites and does not penalize specific techniques. It reassesses the relative quality of content, which can push a site down without it having changed anything, and without any fix spending being justified.
My traffic dropped, is it the algorithm?
Not necessarily. Three more frequent causes must be ruled out first: a technical problem such as a noindex tag or a drop in indexing, a change in the measurement itself, and a competitor that simply moved past you.
What should you do during an update rollout?
Change nothing. A rollout lasts one to three weeks and positions fluctuate throughout that period. Any change made during this window makes it impossible to later attribute an effect to a cause.
How long does it take to recover after a drop?
Recovery usually does not happen before the next update, since that is when the reassessment takes place. It can therefore take several months. No provider can honestly promise a quick return, and a proposal that does should be dismissed for that reason alone.
How do I know if I received a penalty?
A manual action always appears in Search Console, in the section set aside for it. If no notification is there, the drop is not a human penalty but a consequence of automated ranking.
Does black hat SEO still work?
Temporarily, sometimes. Manipulative practices leave recognizable statistical patterns and end up detected. The right test is to ask whether the page would exist if search engines did not exist.
- Google Search Central, Ranking systems updates, accessed July 2026.
- Google Search Status Dashboard, update history, accessed July 2026.
- Google Search Central, Spam policies for Google web search, accessed July 2026.
- Google Search Central, Manual Actions report, accessed July 2026.
Geneviève puts the strategy for your engagement into action. She leads all our web development projects: Shopify, WordPress and the new ways of building a site with AI. She manages our team of developers and translates your business needs into technical language. She runs your organic search (SEO), your visibility in AI answers (GEO) and your site's conversion rate optimization (CRO). Her work is at the heart of three goals: Attract customers with SEO and AI, Improve your site's conversion, and Strengthen your visibility in AI answers. With Gabriel, she also builds the landing pages for your advertising campaigns. She writes mainly about SEO, AI visibility and web design.
About Falia →
SEO
Paid advertising
Conversion
AI visibility
Web design