Google core updates: how to read a traffic drop and respond
A core update hit and your traffic fell. Here is how to confirm the cause, find where the loss sits, and decide what to fix without making it worse.
A core update rolls out, your traffic drops, and the first instinct is to change everything. Resist it. Most of the damage from a bad week comes from rushed edits made before anyone understood what moved. This guide covers how to read a drop, what to check first, and what recovery realistically looks like.
What a core update is (and isn't)
A core update is a broad change to how Google's ranking systems assess content. Google announces them on its Search Status Dashboard and says they usually take a couple of weeks to finish rolling out. They are not penalties. No one at Google flagged your site.
That matters because there is no reconsideration request for a core update. A manual action shows up in Search Console under Manual actions. A core update does not. If that report is empty, you are looking at a reassessment, not a punishment.
Confirm the drop is real before you react
Many drops are not core updates. Rule out the boring causes first.
- Check the Search Status Dashboard for the update's start and end dates. A drop that began days before the start date has another cause.
- Look for a technical change on your side: a deploy, a robots.txt edit, a migration, or a noindex tag that slipped into a template.
- Compare the same weekdays week over week or year over year, so seasonality does not fool you.
- Check the Crawl stats and Pages reports in Search Console for sudden errors or de-indexing.
Wait until the rollout is finished before you draw conclusions. Rankings often swing mid-rollout and settle afterward. Comparing the two weeks after completion with the two weeks before the start gives a cleaner picture.
Find where the loss is concentrated
Open the Performance report in Search Console and compare the two date ranges. Then slice the loss three ways.
- By page: sort by clicks lost. A handful of pages usually account for most of the drop.
- By query: separate branded from non-branded. If branded clicks held, your brand is fine and the loss is in discovery.
- By page type: group by template, such as guides, product pages, or category pages. A loss in one group points to a pattern, not a sitewide verdict.
Patterns tell you more than any single page. If your thin comparison pages fell and your detailed guides held, that is a clear signal about what the update rewarded.
Audit the pages that fell
Open the top losing page next to the page that now ranks above it. Be honest about the comparison. Google has said there is no single fix for a core update, so you are looking for gaps in usefulness, not a checklist item.
- Does the page answer the query completely, or does it skim?
- Does it show real experience, such as original photos, data, or first-hand detail?
- Is it clear who wrote it and why they are qualified?
- Is it mostly rewritten from other pages that already rank?
- Is it cluttered with ads or popups that get in the way?
- Does the format match what searchers want now? Check the intent of the current top results.
Search intent shifts are a common and quiet cause. If the results moved from long guides to short tools or product pages, a better article will not win that slot back.
What to change, and what to leave alone
Fix real quality gaps on the pages that fell. Merge near-duplicates. Add the missing detail. Remove content that exists only to catch a keyword. Do not delete half your site in a panic, and do not touch pages that held steady.
Be wary of quick tricks. Changing dates without changing content does not help. Mass-rewriting pages with AI to hit a word count tends to make the problem worse.
What recovery looks like
Google has said improvements can take months to show, and that some recovery may only come with a later core update. That is Google's own guidance, and it fits what many practitioners report. Some sites never fully return, because the results changed rather than the site getting worse.
AI answer engines complicate this. Citations in AI Overviews and ChatGPT do not follow core updates in any documented way, so a ranking drop does not tell you whether you are still being quoted. Track both separately.
Your next step
Today, export the Performance report for the before and after windows. Sort by clicks lost, group the top 20 pages by template, and write one sentence on what the winning pages do better. That note is your plan. Then wait for the rollout to end before you edit anything.