Google core updates

Core updates recalibrate ranking systems broadly — they don't target specific sites. The WBP differentiator isn't reporting "an update happened" — it's auditing our own detection rules against what Google now rewards, then shipping code changes to the plugin suite within a fixed cycle. Every core update triggers the same 72-hour audit protocol and 7-day cycle.

TL;DR: Response cycle: Hours 0–12 monitor, 12–48 audit rules, 48–72 draft changes. Day 4 beta, Day 6 stable, Day 7 notify users. No update-recovery consulting sold — the fix is public, in the plugins.

1. What a core update actually is

Google's core algorithms are trained against the Quality Rater judgements. Between core updates, the model is stable. A core update ships a re-trained model, usually incorporating months of updated rater guidance and expanded training data.

Nothing about your page changed during a core update. What changed is the model's opinion of what a good page looks like on the query classes you compete on.

2. The 72-hour audit protocol

1
Hours 0–12 — Monitor
Aggregate rank + traffic movement across the WBP user cohort. Distinguish site-level noise from update signal. No public statements yet.
2
Hours 12–48 — Audit rules
Compare winning URLs vs losing URLs on the same query set. Identify what the model now rewards. Score each WBP detection rule against the new signal.
3
Hours 48–72 — Draft changes
Ship code changes to the plugins that need re-weighting. Draft user-facing documentation. Prepare the beta release.

3. The 7-day update cycle

Every announced core update triggers the same 7-day rhythm across the plugin suite:

Days 1–2 — code changes drafted and reviewed.
Day 4 — beta release to opt-in cohort.
Day 6 — stable release.
Day 7 — user notification with plain-language explanation of what changed and why.

Plugin-specific responses: Quality Engine re-weights, EEAT Engine tunes trust signals, Better Rank / Helpful Content adjust detection thresholds, Better Index re-runs indexation audits, Up to Date shifts refresh cadences, SEO Pro updates ranking-factor heuristics.

4. How to detect you were hit

Correlated drop

Traffic falls on or within days of the announced update. Multiple templates decline together — not one URL.

Query-class shift

The queries you lost cluster around one intent or topic. Random distribution is usually a technical issue, not an update.

Rating floor drop

The average position on your primary queries drops one to three positions, not to zero. Total zeroes are more likely index/technical.

SERP re-ordering

Not just you moving down — new competitors moving up. Study the winners to understand the model's new preference.

5. What we don't do

We do not claim to know exactly what Google changed. Nobody outside Google does.
We do not sell 'core update recovery' services. The fixes ship as free plugin updates.
We do not push cosmetic template edits between updates.
We do not overreact to single-URL drops — real update signal is cohort-wide, not per-URL.
We do not stop monitoring between announced updates — ranking drift between updates gets its own watch.