Was It a Google Update? Diagnose the Traffic Drop
The problem
A traffic cliff near tracker volatility is not yet an update diagnosis.
Search evidence, official timing, and competing events must agree before a team starts update-recovery work.
The tracker spiked, so Google caused the loss
This skips Search Console scope, the official record, deployments, reporting, demand, and other controls.
Prove the loss, then test the attribution
Use official timing and first-match controls to choose the narrowest claim and first response.
The insight
Timing can support a contributor claim; it cannot prove cause.
A specific event matching both date and affected scope outranks a loose update overlap. Missing checks produce an honest evidence-first route.
The method
Five steps from traffic alarm to diagnosis memo
Prove the Search loss, verify the official window, test competing explanations, commit attribution and response, and preserve a usable handoff.
Loss
Use Search Console to prove the change and affected scope.
Timing
Use Google’s official record, not tracker chatter.
Alternatives
Check site, policy, reporting, and demand events.
Response
Choose the narrowest attribution and one verifiable first action.
The deliverable
A Traffic Drop Diagnosis Memo
The memo gives an SEO or technical owner one bounded attribution, first response, evidence limit, and review condition.
FAQ
Frequently asked questions
Is a volatility tracker enough to confirm an update?
No. Use Google’s official status record for confirmed rollout dates.
Does timing prove cause?
No. It may support a likely-contributor call only after stronger explanations are checked.
What if controls are missing?
Choose The evidence is not enough yet and make the missing check the first response.
Get started