Did a Google core update hit your site? How to tell, what to check and what not to do

Published November 5, 2026 · 8 min read

A Google core update probably hit your site if three things line up: your organic traffic from Google started falling during the rollout window listed on the Google Search Status Dashboard, the drop shows up as lower average positions in Search Console (not as missing pages or broken tracking), and it is spread across many queries and pages rather than one URL. If any of those is missing, look for another cause first.

This guide walks through how to confirm it, how to read the pattern, and what Google itself recommends doing (and not doing) afterwards.

What a core update actually is

Several times a year Google makes broad changes to its ranking systems and announces them as core updates. Google's own guidance on core updates stresses two points that shape everything below:

Core updates don't target specific sites or pages. They re-evaluate how well content answers searches compared with everything else that competes for the same queries.
Pages that lose positions aren't necessarily "bad". Other pages may simply be judged more helpful for those searches now.

So there is no penalty to lift and no single setting to fix. That is different from a manual action (a human reviewer flagging spam), a spam update, or a technical problem such as pages dropping out of the index. Telling these apart is the first job.

Step 1: Line up your drop with the update dates

Open the Google Search Status Dashboard and look at the ranking updates listed for the last few months. Each entry shows when the rollout started and when it finished. Rollouts usually take one to three weeks, and rankings can move up and down throughout that window.

Then check when your traffic changed:

In Search Console → Performance → Search results, set the date range to the last 3 months and look at the daily Clicks and Impressions lines.
In GA4 → Reports → Acquisition → Traffic acquisition, look at sessions for Organic Search by day.

Ask yourself:

Did the decline start after the rollout began and settle by the time it finished?
Was there another update (a spam update, for example) in the same window? Note it too.
Did you change anything in the same period: a redesign, migration, new CMS, URL changes, a consent banner? If so, the timing alone proves nothing.

A drop that begins weeks before an update, or long after it finished, is very unlikely to be caused by it.

Step 2: Rule out the causes that look similar

Before you blame the algorithm, spend ten minutes excluding the usual suspects. Each has a recognisable fingerprint:

What you see	Likely cause	Where to check
GA4 organic falls, Search Console clicks are flat	Tracking or consent problem, not rankings	GA4 Realtime, Tag Assistant; see why GA4 and Search Console disagree
Clicks drop to near zero overnight on many pages	Pages blocked or removed from the index (`noindex`, robots.txt, server errors)	Search Console → Indexing → Pages; URL Inspection
A message about spam or unnatural links	Manual action	Search Console → Security & Manual Actions → Manual actions
Same dip as last year in the same weeks	Seasonality	Compare with the same period a year earlier
Impressions steady, positions steady, clicks fall	Fewer clicks per impression (SERP features, AI Overviews, a competitor ad)	Performance report: CTR line
Gradual loss of positions over 1–3 weeks across many queries, during a rollout	Core update	Steps 3–4 below

If you want a quick, structured first pass, our free GA4 traffic drop checker works through the tracking, seasonality and channel questions in a few minutes. Our broader traffic drop checklist covers the non-Google causes in more depth.

Step 3: Wait, then compare the right weeks

Google recommends waiting at least a full week after the update has finished before analysing it. During the rollout, positions fluctuate and early numbers mislead.

Then, in Search Console's Performance report:

Click Date → Compare and choose Custom.
Compare one week after the rollout ended with the same weekdays in the week before it started. Using whole weeks avoids weekday effects.
Turn on Clicks, Impressions, CTR and Average position at the top.

Now read the four numbers together:

Positions down, impressions down, clicks down: classic ranking loss. Consistent with a core update.
Positions roughly the same, clicks down: probably not a ranking issue. Look at CTR, seasonality and search demand instead.
Impressions down but positions stable: fewer people searched for your topics (demand), or a set of queries stopped showing you at all. Check which queries disappeared.

Also check the Search type filter (Web, Image, Video, News) separately. A drop in Google Images traffic, for example, can hide inside an otherwise stable Web number.

Step 4: Find out which pages and queries lost the most

A core update rarely hits a whole site evenly. In the comparison view:

Open the Pages tab and sort by Clicks difference. Note the 10–20 pages that lost the most.
Open the Queries tab and do the same. Note which topics the losing queries belong to.
For your top losers, click the row and compare average position before and after.

Google's guidance draws a useful line here:

A small drop, like moving from position 2 to 4, does not call for drastic action. Google explicitly recommends not making changes to content that is already performing well just because it slipped a little.
A large drop, like falling from position 4 to 29, deserves a deeper look at those pages and at the site as a whole.

In GA4, cross-check with Reports → Engagement → Landing page, filtered to Session default channel group = Organic Search. This shows whether the pages that lost Google traffic were also the ones that brought in key events, so you can prioritise the losses that matter to the business, not just the biggest raw numbers.

Step 5: Assess the affected content honestly

For a sustained, large drop, Google points to its self-assessment on creating helpful, reliable, people-first content. Read it, then look at your losing pages next to the pages that now rank above them for the same queries.

Useful questions:

Does your page answer the search better than the pages above it, or does it mostly repeat what they say?
Does it show first-hand experience or expertise, such as original photos, real testing, specific numbers from your own work?
Is the main answer easy to find, or buried under long introductions, ads and pop-ups?
Was the page written mainly to rank (thin variations, keyword-stuffed headings, mass-produced articles) rather than for a reader?
Is it up to date? Outdated steps, prices or screenshots are a common reason a once-good page slips.

Google suggests trying to be objective, and even asking someone not involved with the site to review the pages. Look at patterns across the site, not just individual URLs: core updates assess content broadly.

What not to do

The most common damage after a core update is self-inflicted. Avoid:

Quick fixes. Removing a page element "because someone said it hurts SEO", changing titles everywhere, or adding keyword blocks. Google specifically warns against superficial changes.
Mass deletion. Google calls deleting content a last resort, for pages you believe can't be improved. Bulk-deleting sections can remove pages that still bring in traffic.
Touching pages that only dipped slightly. If a page went from position 2 to 4, rewriting it can lose more than it gains.
Disavowing links in a panic. A core update is not a link penalty. The disavow tool is meant for cases like a manual action for unnatural links.
Reacting before the rollout ends. Rankings often bounce during the rollout. Decide on data from at least a week after completion.
Buying "recovery" services that promise rankings. Nobody can guarantee positions in Google.

How long recovery takes

There is no fixed timeline. According to Google, some improvements can take effect within days, but it can take several months for its systems to recognise that a site is consistently producing helpful content. Google also runs smaller, unannounced core updates, so recovery doesn't always have to wait for the next big one. If nothing has changed after a few months, the next broad core update is often when you see the effect.

And sometimes there is no "recovery" in the old sense: if competitors now genuinely answer the query better, the realistic goal is to make your page the best answer again, not to restore an old position.

Summary: a 15-minute check

Find the update dates on the Search Status Dashboard and line them up with your daily clicks and organic sessions.
Exclude tracking problems, indexing problems, manual actions and seasonality.
Wait a week after the rollout ends, then compare whole weeks before and after in Search Console.
List the pages and queries with the largest position losses, and check which ones mattered for key events in GA4.
Improve the pages with large drops meaningfully; leave small dips and well-performing pages alone.

FAQ

Does Google tell you if a core update affected your site?

No. There is no notification in Search Console for core updates. Manual actions do get a message, which is one way to tell them apart.

My traffic went up after a core update. Should I do anything?

Not urgently. Check that the gain is in pages and queries that matter to you, and keep improving the same way. Positions can shift again at the next update.

Can a core update affect only part of my site?

Yes. It is common for one section, content type or topic to lose while the rest is stable. That is why the page and query breakdown in Step 4 matters more than the sitewide total.

Is a drop in clicks with stable positions a core update?

Usually not. If your average position didn't change, rankings aren't the main cause. Look at click-through rate, search demand and changes in what the results page shows.