What actually changes in a core update
Google's ranking systems are a stack of signals — relevance, quality, expertise, trust, usefulness, page experience, links — and a core update adjusts how those signals are weighed and how quality is assessed, across every query at once. Nothing about your site is flagged; your pages are simply re-scored against a recalibrated standard, alongside every competitor's. That's why the same update lifts some sites and drops others in the same industry: the ones that were over-rewarded under the old weighting lose ground, and the ones that were under-rewarded gain it. Google search, in its own description, is trying to reward content that would have deserved to rank all along.
How to read the drop, or the gain
Open Search Console's performance report and compare the two or three weeks after the update's rollout began with the same period before, filtered by page and then by query. A sitewide decline across most pages and queries points at a quality reassessment; a drop concentrated on a few pages or a few queries points at those pages' relevance or at a competitor improving. Cross-check the Search Status Dashboard for the exact rollout window, since core updates take days to two weeks to complete and traffic keeps moving until they do. And annotate your own changes — a redesign, a migration, a lost link, a seasonal dip — because these mimic updates constantly and get blamed on them.
What to do if you dropped
First, nothing dramatic. Rankings during a rollout are unstable, and the reflexive week-one edits — rewriting titles, deleting pages, stuffing keywords — remove the very things Google may have been about to re-credit. When the rollout completes, assess the affected pages honestly against the quality questions Google itself publishes: is the content original and substantive, does it demonstrate real expertise, does it fully answer the search, would a reader trust the author, is the page cluttered or thin, is it obviously written for search engines rather than people. Then improve — consolidate thin pages, add real depth and proof, fix technical friction — and understand that recovery from a core update typically shows at the next core update, when the site is re-scored again. There is no fix that reverses a core update in a week, and anyone selling one is selling a story.
What to do if you gained
Gains are a signal too: the update credited something you were doing. Identify which pages and queries rose, and do more of exactly that — the same depth, structure, expertise and proof, applied to the pages that didn't move. Protect the technical foundation so nothing undermines it, and keep building; the sites that ride updates upward over years are the ones treating each one as feedback rather than weather.
Spam updates are a different conversation
If the timeline points at a spam update instead, the diagnosis is narrower and the answer more direct. Spam updates improve Google's detection of manipulation: bought or networked links, scaled machine-generated pages with no value, expired-domain abuse, hacked content, cloaking. A site hit by one has something specific to remove — the links, the pages, the vendor who supplied them — and often a manual action notice in Search Console spelling it out. Recovery here is faster than from a core update, because the cause is concrete. It's also the clearest argument for doing search engine optimization the slow, honest way in the first place.
The long view
Over ten years of updates, one pattern holds: sites built on genuine pages, demonstrated expertise, real reviews and earned links drift upward across updates, with the occasional dip; sites built on shortcuts drift downward with the occasional bounce. A core update is Google moving its grading closer to what a careful human would judge, and the practical strategy is to build for that judge continuously rather than to react to each announcement. If your traffic moved and you want to know why, the free audit reads your Search Console data against the update timeline and gives you the honest diagnosis and the prioritized fix list, in writing, the same business day.
