ClarifySEO · 27 May 2026
How to check if a Google core update affected your site
Traffic dropped after a Google core update? Here's how to tell whether it actually hit you — and what to do if it did.
Google rolled out its May 2026 core update on May 21st. If your traffic dropped around that date, the instinct is to assume you were hit. Sometimes that's right. Often it isn't — and treating an AI Overviews problem like a content quality problem, or a seasonal dip like an algorithm penalty, will send you in the wrong direction.
There's a straightforward way to tell what actually happened. It takes about fifteen minutes in Google Search Console.
Wait for the rollout to finish first
Core updates take up to two weeks to fully settle. Rankings move around during the rollout period before stabilising — a page that looks hit on day three might recover by day twelve, and a page that looks fine early might drop later.
Google's own guidance is to wait at least one full week after the rollout completes before drawing conclusions. The May 2026 update is expected to finish around June 4th. Mark that date. Any analysis you run before then is based on incomplete data.
That doesn't mean ignoring your Search Console — it means not making major content decisions based on what you see while the update is still in motion.
Source: Google, Core Updates guidance
The check that matters: impressions, not traffic
Most people look at traffic first. Traffic is the wrong starting point because it conflates several different problems into one number.
Open Google Search Console and go to Performance. Set the date range to compare the 28 days before May 21st against the 28 days after. Look at impressions before you look at clicks.
Two patterns tell you very different things:
Impressions and clicks both fell together. Your pages are appearing less often in search results. Google has reassessed your content and is showing it to fewer people. This is what a core update hit looks like — a ranking change, not a CTR change.
Clicks fell but impressions held. Your rankings haven't moved. People are seeing your pages in results at roughly the same rate, but fewer of them are clicking. This is a CTR problem — and in 2026, AI Overviews absorbing traffic above your organic result is the most likely cause. The fix is improving titles and meta descriptions, not rewriting content.
The distinction matters because the responses are completely different. Treating an AI Overviews problem like a content quality problem wastes time and changes things that weren't broken.
Source: Launchcodex, Google May 2026 Core Update
Rule out a manual action first
Before anything else, check whether Google has issued a manual penalty against your site. A manual action is a direct intervention by Google's spam review team — it requires a different response entirely and is not resolved by improving content quality.
In Search Console, go to Security and Manual Actions. If it shows "No issues detected," your site doesn't have a manual penalty and any drop you've seen is algorithmic, not a penalty.
This check takes under a minute and should always be the first step when a sharp, sudden drop occurs.
Check which pages were affected
Site-wide drops and page-level drops point to different causes.
In the Performance report, switch to the Pages tab and sort by the change in clicks over the comparison period. If most of your pages lost impressions at the same time, you're looking at a site-wide re-assessment — Google's view of your overall content quality has shifted. If only specific pages or sections dropped, the issue is more localised.
A few pages dropping around a core update usually means those specific pages lost to competitors whose content better matches what users are looking for. A site-wide drop is a signal that something more systemic is being evaluated — depth of content, topical authority, trust signals.
What a core update is actually doing
Core updates are not penalties. Google has been consistent on this: a ranking drop during a core update doesn't mean your content is wrong, it means another page now better satisfies the same search intent in Google's assessment.
The May 2026 update, like the March 2026 update before it, continues Google's long-running direction: rewarding content with genuine depth and original insight, and reducing visibility for content that exists primarily to rank. That's not new — it's been the direction since the helpful content system became part of core ranking in 2024. This update is further along that same path.
The practical implication: if your content was written to rank rather than to genuinely answer a question, this update will continue to be a problem. The recovery isn't a technical fix — it's improving the substance of what you're publishing.
The AI content question
This update follows a clear pattern in Google's direction, and it's worth stating plainly: the window for AI-generated content to perform well in search is closing. It hasn't slammed shut, but the trajectory is clear.
The helpful content system was the first signal. Core updates in 2024 and 2025 reinforced it. The May 2026 update continues it. Google is building systems to surface content that reflects genuine experience and knowledge — because in an environment saturated with AI-generated text, that's the only way to maintain search quality.
For site owners who've been using AI to produce content at scale, this is a real risk. For site owners writing from actual experience about things they genuinely know, this is an advantage — because that content is harder to replicate than anything generated at scale.
That's not an argument against using AI tools at all. It's an argument that the content has to reflect real knowledge, not substitute for it.
Source: Google, Creating helpful content
If you were hit: what to do
Google's position on recovery is consistent: there are no specific technical actions that reverse a core update impact. The system evaluates sustained content improvement over time — which means the work starts now but the recognition comes later, often at the next named update.
The most honest question to ask for each affected page is whether it genuinely answers the query better than the pages that have moved above it. Not whether it's longer, better formatted, or more keyword-optimised — whether it's actually more useful to someone who searched that term. If the answer is no, that's the work.
One thing worth knowing: Google has confirmed that smaller unannounced algorithm changes run continuously between named updates. Improvements made now can be recognised before June, not only when the next core update rolls out. There's no reason to wait.
The number worth watching going forward
Average position gives you a snapshot. Impressions give you a trend. The most useful habit after any core update is setting up a comparison in Search Console that you can revisit monthly — the same date range, the same pages, so you can see whether impressions are recovering or continuing to decline.
Month-on-month tracking is what tells you whether the work you're doing is having any effect. Without it, you're making content decisions without feedback — which is exactly the situation this kind of update is designed to create pressure around.
See exactly which of your pages lost impressions in the May 2026 update.
Run a free audit and see exactly where you stand.