You open Analytics on a Monday and the line has fallen off a cliff. Sessions down 40 percent, maybe more. Somewhere in the last two weeks a Google core update finished rolling out, and your site got caught in it. The panic response is to start rewriting pages, swapping title tags, and installing three new plugins by Wednesday. That is exactly how a bad week turns into a bad quarter.
We get these calls constantly. The owner has already made six changes before we talk, and now nobody can tell which change helped, which hurt, and what the update actually touched. So the first rule is blunt: do not change anything until you know what caused the traffic drop.
Confirm it was actually a Google core update
Not every traffic drop is a core update. Seasonality, a tracking tag that broke, a noindex someone left on after a redesign, a server that was down for a night: all of these look like an algorithm hit if you only glance at the top-line number. Before you blame Google, rule out the boring causes.
Open the Google Search Status Dashboard and note the exact start and end dates of the most recent Google core update. Google confirms these publicly. Then line those dates up against your traffic graph. If your decline started the day the rollout began and kept sliding as it progressed, that is a strong signal. If your drop started a week before the rollout, the update is not your problem and you would be fixing the wrong thing.
One more thing people skip: wait for the rollout to finish. Core updates take one to three weeks to fully deploy, and rankings bounce around while they run. If you react on day three you are chasing a moving target. Give it a full week after the announced end date before you draw conclusions.
Go to Search Console before you touch a page
The Performance report in Google Search Console is where the real diagnosis happens, not Analytics. Set the date range to compare the period after the update finished against an equal stretch before it started. Filter to Search results and web only, so Discover and news noise does not muddy the picture.
Now change the view from clicks to impressions. This matters. Search rankings usually slip before clicks do, so impressions show you where you lost position first. A page that lost impressions has lost visibility in the results; a page that kept impressions but lost clicks has a different problem, which we will get to.
Sort your pages by the biggest impression loss over the window. Do the same for queries. Within twenty minutes you should have two short lists: the exact URLs that dropped and the exact keywords they dropped for. That is your map. Everything else is guessing.
Read the pattern, not just the pages
Look at what the dropped pages have in common. Are they all thin comparison posts? All older articles you never updated? All targeting the same cluster of commercial keywords? A Google core update rarely hits a site at random. They tend to reassess a type of content or a topic where your site no longer looks like the best answer. The pattern tells you what Google reweighted, and that is far more useful than looking at any single page in isolation.
This kind of before-and-after comparison across hundreds of URLs is tedious to do by hand, which is why most owners stop halfway. Our RankRescue diagnostic tool pulls the Search Console and GA4 data together and flags the pages and queries that moved, so the pattern surfaces in minutes instead of an afternoon of spreadsheets.
Cross-check behavior in GA4
Search Console tells you what happened in the results. GA4 tells you what happens once people land. Pull up the affected landing pages in GA4 and look at engagement rate, average engagement time, and conversions for those same URLs over the same window.
If a page lost search rankings and it also had a weak engagement rate before the update, Google likely decided competitors satisfy the query better. That is a content quality signal you can act on. If a page still gets its remaining visitors to stick and convert, the content is fine and the drop is about competitive position, which is a different fix. Separating those two cases stops you from gutting a page that was actually working.
Factor in what AI results are doing to clicks
Here is the part that catches people off guard in 2026. Some of your lost clicks are not a ranking problem at all. They are AI Overviews and AI Mode eating the click before it ever reaches you.
The numbers are not small. Ahrefs measured that when an AI Overview appears, the top organic result sees roughly 58 percent lower click-through. Pew Research, studying almost 69,000 real searches, found people clicked a traditional result 8 percent of the time when an AI Overview was present versus 15 percent when it was not. And in the first four months of 2026, about 68 percent of Google searches ended with no click at all. In AI Mode, that figure runs near 93 percent.
So check your Search Console data for the tell: if a page held its average position but lost clicks, you probably did not get demoted. An AI answer is now sitting above you and satisfying the searcher directly. The response to that is not to rewrite the page in a panic. It is to target queries where AI answers are weaker, earn citations inside those AI responses, and lean into content that needs a human to actually visit, like tools, calculators, original data, and bottom-of-funnel pages.
Now, and only now, decide what to fix
With the diagnosis done you can act with intent instead of flailing. In practice the fixes fall into a few buckets:
- Genuine quality gaps. Pages that dropped and had weak engagement need real depth: first-hand experience, original numbers, and an answer that actually matches what the searcher wanted. Rephrasing the same points more smoothly will not move them.
- Intent mismatch. A page ranking for a query it does not truly serve will keep slipping. Either reshape it to match intent or point that keyword at a page that fits.
- Competitive position. Pages that are fine but lost search rankings to competitors need better internal links, more supporting content around them, and stronger signals that you are an authority on the topic.
- AI-driven click loss. Different game entirely. Shift effort toward content and formats that a summary cannot replace.
Change a small batch, document the date, and wait. Google does not reprocess your site overnight, and recovery from a Google core update often does not land until the next one rolls out. Give each change room to be measured before you stack more on top of it.
What not to do
Do not delete pages in bulk hoping to "prune" your way back. Do not disavow links out of superstition. Do not swap your CMS. Do not buy an SEO tool subscription and act on every red flag it shows, because most of those flags have nothing to do with why you dropped. Panic changes are how sites that lost 30 percent end up losing 60.
The discipline is simple to say and hard to hold: diagnose first, change second, measure third. A Google core update is a signal about a specific slice of your content. The data to hear the message is already sitting in your Search Console account.
If you would rather not do it alone
Reading a Google core update correctly takes pattern recognition across a lot of data, and it is easy to talk yourself into the wrong story. We build tools for exactly this kind of diagnosis, and we build them for teams who want answers without becoming full-time analysts. If you want that work done properly, our AI tools development services cover custom diagnostics tuned to your site and your goals.
Frequently Asked Questions
How long after a Google core update should I wait before making changes?
Wait until the rollout is officially finished, then give it a full week on top of that. Core updates take one to three weeks to deploy, and rankings swing wildly while they run. If you react on day three, you are measuring noise. Let positions settle, confirm the drop held, then change one small batch and wait again.
My rankings look the same but clicks fell. Was I actually demoted?
Probably not. Check Search Console: if a page held its average position but lost clicks, an AI Overview or featured answer is likely satisfying the searcher above you. That is a click-loss problem, not a ranking one. Rewriting the page in a panic will not bring those clicks back. Target queries where AI answers are weaker instead.
Can a Google core update fully reverse, or is the drop permanent?
It can reverse, but rarely fast. Google reprocesses quality signals slowly, and recovery often does not land until the next core update rolls out, sometimes months later. That is why stacking daily changes is pointless. Fix the genuine quality and intent gaps, document what you changed, and expect the meaningful bounce to arrive on Google's schedule, not yours.
Should I use Analytics or Search Console to diagnose the drop?
Both, in order. Start in Search Console with the Performance report, switch to impressions, and find the exact URLs and queries that lost visibility. Then cross-check those same pages in GA4 for engagement and conversions. Search Console tells you what happened in the results; GA4 tells you what happens after the click. One without the other is half a diagnosis.
How do I know if it was the update or something I broke myself?
Rule out the boring causes first. A stray noindex after a redesign, a broken tracking tag, a server outage, or plain seasonality all mimic an algorithm hit. Line your traffic graph up against the confirmed rollout dates on the Google Search Status Dashboard. If your decline started before the rollout began, the update is not your culprit.
Is deleting or pruning low-traffic pages a safe way to recover?
Not as a reflex. Bulk-deleting pages hoping to prune your way back usually removes URLs that were doing no harm and sometimes some quiet wins. Only remove a page if it genuinely serves no one and cannot be merged into something stronger. Diagnose which pages actually dropped and why before you touch the delete button.
If your traffic drop just happened and you want a second set of eyes before you start changing things, tell us what you are seeing on our contact page and we will help you find the real cause first.