A traffic drop that lines up with a confirmed Google core update rollout, and affects a broad set of pages rather than one URL, is very likely update-related. Recovery requires identifying which specific pages lost visibility, making those pages genuinely more useful than what currently outranks them, and waiting for a subsequent update to re-evaluate the improvements, which can take several months.
The first question: was it actually the update?
Before diagnosing anything, confirm the timing. Compare the exact date traffic dropped against Google's published core update rollout windows. A drop that lines up closely, affecting a broad set of pages rather than one URL, is very likely update-related. A drop confined to one page, or one that started on a date with no confirmed rollout, is more likely a technical fault, a lost backlink, or a manual action, each of which needs a completely different fix.
What core updates are actually evaluating
Core updates re-run Google's broad assessment of content quality and relevance across the whole index. Nothing was "done to" your site specifically. Pages that were always thin, generic, or less useful than competing pages simply get re-ranked more accurately once the update processes. This is why recovery is rarely about finding a single broken setting and far more often about genuinely improving the content itself.
How to diagnose what happened
Pull the list of your highest-traffic pages before and after the update from Search Console, and sort by the largest percentage losses. Look for a pattern: is it a specific content type, a specific topic, or pages competing against a specific kind of competitor? A SEO audit at this stage should focus entirely on the affected pages rather than the whole site, since spreading the diagnosis too wide slows down finding the actual pattern.
What recovery usually requires
Once the pattern is clear, the fix is almost always making the affected pages genuinely more useful than what currently outranks them: more complete answers, clearer structure, real expertise visible on the page, not just more words. This is content strategy work, not a technical patch, and it does not show results immediately. Google has said recovery typically requires waiting for a subsequent update to re-evaluate the improved pages, which can take several months.
Spam updates vs core updates: a different problem
Not every drop is a core update. Google also ships separate spam updates targeting specific manipulative patterns, scaled content abuse, expired domain abuse, site reputation abuse, and a helpful content system that specifically evaluates whether content was written primarily for people or primarily to attract search traffic. A drop tied to a spam update usually means a specific, identifiable violation rather than a broad quality re-evaluation, and it often requires a reconsideration request after the fix rather than simply waiting for the next core update.
Check Search Console's Manual Actions report first. A drop with an associated manual action is a spam issue with a specific documented cause. A drop with no manual action, timed to a confirmed core update rollout, is a quality re-evaluation, and the two require entirely different responses.
The mistakes that make it worse
- Rewriting the entire site instead of the specific pages the data shows were actually affected.
- Chasing a rumoured "fix" from a forum thread instead of your own Search Console data.
- Making large structural changes and technical changes at the same time, which makes it impossible to tell which change caused which result.
- Giving up after one update cycle. Genuine improvements sometimes take two or three cycles to be fully reflected.
The honest summary
A core update recovery is a diagnosis exercise followed by patient, targeted content improvement, not a single technical toggle. Sites that treat it that way, and that can point to documented case studies of doing it before, tend to recover fully. Sites chasing a quick fix usually spend months solving the wrong problem.