Search Visibility

Traffic Dropped After A Google Core Update

A core update drop feels like a penalty and is not one. Google states these updates do not target individual sites, that a page which dropped is not necessarily bad, and that no change you make carries a guarantee of recovery. That last sentence is the one that should decide how much you spend, and it is the one nobody quotes.

Get the drop read before you spend The sentence nobody quotes

Start here

Where You Are In This

Three points people arrive at, and the right move is different at each. Pick the one that matches your week.

  • 01

    It dropped this week

    Do not touch anything yet. Google says to wait until the update finishes rolling out and then a full week beyond that before analysing, because the numbers move while it runs.

    Why waiting is the work
  • 02

    You are sure it was a penalty

    Check Search Console for a manual action first. If there is none, it is not a penalty, and treating a ranking change as an infraction sends you looking for a rule you never broke.

    What a core update is
  • 03

    Months on, nothing has come back

    That is a known outcome rather than a failed fix. Google says it may take until the next core update, and separately that recovery is not guaranteed at all.

    The sentence to plan around

The correction

It Is Not A Penalty, And You Did Not Break A Rule

The first correction is the most useful one, because it changes what you go looking for.

A page can fall without changing, because position is relative Two ranked lists side by side, before and after a core update. In the before list, your page sits third out of six with a fixed quality bar drawn beside it. In the after list, your page has exactly the same quality bar, unchanged, but now sits fifth, because two other pages were reassessed upward and moved above it. An arrow between the lists is labelled nothing changed on this page. A caption records Google's statement that core updates are broad in nature and do not target specific sites or individual web pages, and that pages which drop do not have anything wrong to fix. BEFORE THE UPDATE 1 2 3 Your page 4 5 6 NOTHING CHANGED ON THIS PAGE AFTER THE UPDATE 1 2 reassessed up 3 4 reassessed up 5 Your page 6 The bar beside your page is identical in both columns. Only its neighbours moved. Google: core updates are broad in nature and do not target specific sites or individual web pages, and pages that drop after a core update do not have anything wrong to fix.
The same page, the same quality, two positions. Only the neighbours moved.

Google

Core updates are broad in nature, and don't target specific sites or individual web pages.

Nothing was done to you. A core update changes how Google assesses relevance across the board, and your position is relative: pages that did not move can lose ground because others gained it. That is why audits that hunt for a fault often find nothing, and why the ones that find something usually found it because they were determined to.

Google is blunter still about what a drop implies about your page.

Google

Pages that drop after a core update don't have anything wrong to fix.

Read that before commissioning anything. It does not say there is nothing you could improve. It says the drop itself is not evidence of a defect, so a project justified purely by the drop is a project justified by nothing.

The order

The First Instruction Is To Do Nothing

Google publishes an order of operations, and it starts with not acting. This is the part most often skipped, and skipping it is what produces the wrong diagnosis.

When a reading is worth taking, and when it is a reading of a moving target A timeline running left to right. A shaded band marks the rollout, from the update start date to the update end date, with a jagged line through it showing rankings still moving. Immediately after the end date a second shaded band marks one further week, labelled still settling. Only the region after that is marked as the point at which Google recommends analysing in Search Console. Two comparison markers are drawn: a valid comparison between the week before the rollout began and the week after the settling period, and an invalid one taken inside the rollout, marked as measuring a moving target. A caption states that most wrong diagnoses come from a reading taken in the shaded regions. THE ROLLOUT rankings still moving ONE WEEK still settling READ IT HERE Analyse now against the week before The week before THE ONLY COMPARISON WORTH MAKING START END PLUS 7 DAYS Google: wait at least a full week after a core update completes before analysing your site in Search Console. Most wrong diagnoses are readings taken inside the shaded regions, then acted on for months.
A reading taken in either shaded band is a reading of something still moving.

Google

We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console.

  1. 01

    Find the actual dates

    Check the Search Status Dashboard and note the start and end date of the update. A drop that began before the rollout started was not caused by it, and that alone settles a surprising number of cases.

  2. 02

    Wait for it to finish, then wait a week

    Google recommends waiting at least a full week after a core update completes before analysing your site in Search Console. Rankings move throughout a rollout, so a reading taken mid update is a reading of a moving target.

  3. 03

    Compare like with like

    The comparison is this week against a week before the rollout began. Not month on month, which mixes the update with seasonality, and not against last year, which mixes it with everything.

  4. 04

    Size it before you scope it

    A small drop and a large one are different problems. Assess how pages were ranking before and after, and let the size decide whether a deeper assessment is justified at all.

  5. 05

    Only then, assess the content

    For a large drop, Google points at its own questions on helpful, reliable, people first content. That is a content review, not a technical audit, and the two get confused constantly.

The ceiling

Recovery Is Not Guaranteed, And Google Says So

This is the sentence that should govern the budget, and it is almost never in the proposal.

Google

There's no guarantee that changes you make to your website will result in noticeable impact in search results.

Google is not saying effort is wasted. It is saying the relationship between work and recovery is not contractual. Anybody selling a core update recovery with a timeline or an outcome attached is selling something the platform has explicitly declined to promise.

  • Days to months

    Google says some changes can take effect in a few days, but it could take several months.

  • Or the next update

    If it has been a few months with no effect, Google says that could mean waiting until the next core update. Assessments are refreshed when the systems are, not when your work is finished.

  • Or not at all

    The no guarantee sentence is unconditional. It is the honest ceiling on what any adviser, including me, can promise.

Makes it worse

Five Responses That Cost More Than The Drop

What people do in the first fortnight, and what it costs.

  • Rewriting everything at once

    It removes your ability to attribute anything. If forty pages change and traffic moves, you have learned nothing about which change mattered, and you cannot undo the ones that hurt.

  • Deleting or noindexing the losers

    Often done on the theory that thin pages are dragging the site down. A page that dropped is not established as a problem page, and removing it removes whatever it was still earning.

  • Buying links to force it back

    This converts a ranking change, which carries no penalty, into a link spam problem, which can. It is the one response that can make the situation categorically worse.

  • Filing a reconsideration request

    Reconsideration is for manual actions. With no manual action there is nothing to reconsider, and the request confirms the diagnosis was wrong rather than fixing anything.

  • Changing the technical stack

    Migrations undertaken as a response to a core update introduce a second, larger variable on top of the first. Now two things are moving and neither can be read.

What is worth doing

Work That Holds Its Value Either Way

What is actually worth doing, given that recovery cannot be promised.

  1. 01

    Establish what you lost, in money

    Not sessions. Which queries lost position, what those queries were worth in enquiries, and therefore what the drop costs per month. If the answer is small, the correct response may be to accept it.

  2. 02

    Separate the drop from the trend

    Plenty of sites that blame an update were already declining. The dashboard dates make this visible in one comparison, and the answer changes completely if the slope predates the rollout.

  3. 03

    Change one thing that you can read

    A cohort of pages, a single change, and a held back control group. This is slower and it is the only version that teaches you anything about your own site.

  4. 04

    Fix what was already worth fixing

    If a page was thin, unclear or out of date before the update, improve it because it was, not because a rank moved. That work holds its value whichever way the next update goes.

  5. 05

    Reduce the dependency

    The sites that survive updates comfortably are the ones where organic search is one channel among several. That is a business change rather than an SEO one, and it is the only permanent answer to an assessment you do not control.

Questions

The Ones That Keep Coming Up

No. Google says core updates are broad in nature and do not target specific sites or individual web pages. A penalty in the strict sense is a manual action, which appears in Search Console. If there is no manual action listed, there is no penalty to appeal.

Google recommends waiting at least a full week after the update finishes rolling out before analysing your site in Search Console. Rankings move throughout a rollout, so anything measured during it is measuring a moving target.

Google states that pages which drop after a core update do not have anything wrong to fix. Position is relative, so a page can lose ground because other pages gained it rather than because it got worse.

Google says some changes can take effect in a few days but it could take several months, and that if a few months pass with no effect it could mean waiting until the next core update. It also states there is no guarantee of noticeable impact at all.

Not on the evidence of the drop alone. A page that dropped has not been established as a problem, and deleting it removes whatever it still earns. Improve or remove pages on their own merits, decided before the update rather than because of it.

No, and the sentence to hold them to is Google's own: there is no guarantee that changes you make to your website will result in noticeable impact in search results. A guaranteed recovery is a promise the platform has declined to make.

Where this came from

Every Quote On This Page

Google Search Central, checked against the live pages on 10 September 2026. Nothing here is a paraphrase presented as a quotation.

Written by

Zammy Zaif

Global search and business growth strategist. The most expensive core update cases I see are the ones where somebody acted in the first fortnight, changed forty things at once, and can no longer tell which of them helped.

Before you commission a recovery

Send me the dates and the Search Console export. An hour is usually enough to establish whether the update is even a candidate, what the drop is worth per month, and whether the honest answer is to accept it. Sometimes it is, and you will be told that.

Book expert consultation Other problems