Every few months a client sends me a screenshot of a traffic graph with a cliff somewhere in the middle. The first question is always the same: was it an update? The answer is almost never obvious, and most of the advice circulating online makes it worse — either panicking too early or shrugging and doing nothing at all.

I have been watching core updates since 2012 and dealing with the fallout professionally for most of that time. Here is what I actually know to be true, as opposed to what sounds authoritative on an SEO blog.

What a Core Update Actually Is

Google runs a core update roughly three to four times a year. A core update is a change to the main ranking algorithm — how Google weights signals like E-E-A-T, relevance, and quality across its entire index. It is not targeted at a specific tactic. It is Google recalibrating which pages it thinks deserve to rank for broad categories of intent.

Spam updates are different. They target specific patterns Google has identified as manipulative: thin affiliate content, scaled content abuse, site reputation abuse (parasite SEO), cloaking, and similar. If you got hit by a spam update and you have clean content and a clean link profile, you are probably caught in collateral filtering — which does happen and which does resolve, usually within a few weeks.

Product reviews updates existed as a separate cadence and are now folded into core. Helpful content updates are now also part of the core cycle. Tracking which named update dropped is less important than understanding what category of signal changed.

How to Tell If an Update Actually Hit You

Step one: check the date. Google publishes confirmed update rollout windows on its Search Status Dashboard. If your traffic drop started more than two weeks before or after a confirmed update, you are probably looking at something else — a technical issue, a lost backlink, a competitor surge, or a manual action.

Step two: look at which pages dropped. If it is sitewide, that points toward a quality or spam signal on the domain level. If it is category-specific, look at what those pages have in common — thin content, over-optimized anchor text in internal links, affiliate density, or pages that match a spam update target pattern.

Step three: compare against competitors in the same vertical. Go into Google Search Console, filter by the impacted queries, and look at whether your impressions dropped without position changes, or whether positions fell too. Then check whether pages that outranked you gained or if a different set of competitors entirely moved in. That tells you whether Google elevated a specific type of content or just reshuffled the deck.

Step four: check for manual actions in Search Console under Security and Manual Actions. An algorithmic update and a manual penalty are entirely different situations and require different responses.

What Not to Do in the Days After an Update

The worst thing you can do is make large-scale changes immediately after an update drops. Google explicitly says that core update recoveries, if they happen, take months — typically until the next core update. Rearchitecting your site in a panic before the rollout is even finished (most updates take one to three weeks to fully deploy) will make it nearly impossible to tell what is helping.

Do not add content in a panic. Thin content added quickly to shore up page counts signals desperation more than quality, and Google can tell. This is also where the line between content marketing and SEO matters most — reactive publishing rarely serves either goal. Do not go on a link-building sprint. If spam signals contributed to your drop, acquiring more links at volume is the wrong direction.

Do not implement changes based on correlation posts from third-party rank trackers. Those tools aggregate data across millions of sites and can tell you a wave happened — they cannot tell you why your specific site was impacted or what to fix.

What Actually Helps Recovery

Honest assessment first. Print out your twenty lowest-performing pages from the past 90 days and read them as if you were a user, not an SEO. Are they genuinely useful? Do they say something a visitor could not find in three better places in two minutes? If the answer is no, that is where you start.

For core update recoveries, Google has published a list of self-assessment questions, and they are worth taking seriously: Does the content demonstrate first-hand expertise? Is it written for people, not for ranking? Does it leave visitors satisfied or hunting for more? These are harder questions than they look. Most content fails them in subtle ways — it technically covers the topic but adds no perspective, no judgment, no insight a human with real experience would offer.

For spam update hits, the path is usually to consolidate and remove rather than add. Thin pages that were created to capture keyword variants but that deliver no real value should either be merged into stronger pages or removed and redirected. This is slow work and it is uncomfortable because it means acknowledging that some of what was built probably should not have been built.

The Realistic Recovery Timeline

Most sites that recover from a core update do so within two core update cycles — six to nine months. Layering in a seasonal SEO strategy during the recovery period helps you plan content timing around demand rather than scrambling through volatility. That is a hard number to give clients who are watching revenue drop, but it is accurate. Sites that make genuine improvements often see partial recovery before that, but full recovery rarely happens in weeks.

Spam update recoveries are faster if the offending patterns are genuinely removed. In my experience, two to four months is realistic once the underlying issue is corrected and Google has re-crawled the affected pages.

Some sites do not recover, and I think it is worth saying that plainly. If a site was built primarily around ranking rather than around being useful to a specific audience, and if the competitive landscape has genuinely improved, recovery may require rebuilding the content strategy from scratch rather than patching the current one.

What I Actually Do With Clients After an Update

When I work through an update impact with a client, the first two weeks are pure diagnosis — no changes, just documentation. I want to see the full shape of the drop: which pages, which queries, which devices, which countries. That map tells me what signal probably shifted.

After that, I build a prioritized list. High-traffic pages that dropped get reviewed for content quality first. Pages with clear spam patterns (over-optimized anchor distributions, near-duplicate content clusters) get addressed second. Technical issues — crawl budget problems, canonicalization errors that might have confused Google during the update — get handled alongside content work, not sequentially.

I am not going to tell you there is a formula that works every time. If the update fallout has you evaluating outside help, the guide on how to read an SEO proposal will help you assess what you are actually being offered. Updates are Google making judgment calls at scale, and those judgment calls are not always consistent. What I can tell you is that sites with genuinely useful content and clean technical foundations recover more reliably than sites that were built primarily around ranking signals.

If you are dealing with a drop and want a straight read on what you are looking at, my SEO consulting work starts with exactly this kind of diagnosis. I would also suggest reading through SEO red flags if you are evaluating whether your current approach is the problem, and how to measure SEO success for building a cleaner baseline before the next update cycle hits.

  • SEO ConsultingThe main engagement page — start here if you want a direct assessment of your situation.
  • SEO Red FlagsSigns that your strategy or provider has structural problems worth addressing before the next update.
  • How to Measure SEO SuccessBuild a measurement framework that holds up through algorithm volatility.