Technical
How to check if a Google update hit you
update-week-check a saved expert workflow your assistant follows, in Claude, ChatGPT or Cursor
Was your bad week a known search or AI event? Give a date window and this free check maps it against the documented event calendar, confirmed Google core and spam updates, AI-surface rollouts, engine and ecosystem events, data artifacts like the num=100 break, and reports overlaps honestly: correlation, not confirmation.
Try it
did the update hit us
Private beta Part of the quattr-ai-search plugin, rolling out org by org. Request access ↗
Say any of these
was there a Google update last week?did an algorithm update hit us?was my traffic drop an algo update?any core update around June 25?update week checkwas that week volatile for everyone?
You never name the skill or a tool, the assistant routes on what you asked. These are the phrasings it recognises for this one.
And when it stays out of the way
Not when you want cause analysis on THEIR data ("why did our clicks drop") or a gainers/losers table (rank-movement-review).
Use it instead of anomaly-investigator when there is no Quattr account/MCP and the ask is only whether a documented event overlapped a window; use anomaly-investigator instead when you have a Quattr account/MCP connected, cause analysis runs on YOUR data there.
What it reads
This one answers from evidence rather than from your metrics, it fetches and reads what it needs, so it runs no analyses against your data.
The numbers behind it
Metrics it reads, each defined in the reference
Domain moversPage-one footprint retentionSERP volatility index
Reports these numbers feed
What it refuses to do
- Never present algo-unconfirmed tracker chatter as confirmation, it corroborates, it never suffices.
- Prevalence and volatility figures are methodology-dependent across trackers, never compare readings across trackers.
- Beyond-coverage windows get the boundary statement, not a guess; forward-dated calendar entries (e.g., the 2026-09-15 CDN default flip) are announced-not-yet-landed and must be labeled so.
What the answer looks like
Was there a Google update last week?
Analysis plan, every step, resolved for you
- Routed to the governed workflow
update-week-check - Dates bound explicitly
Jul 19 to Jul 25, 2026 - Honesty gates armed
scope echo · freshness
Yes, a documented core update overlapped 5 of your 7 days. That's correlation, not confirmation.
- Events in window
- 1 confirmed Google core update, rolling Jul 21 to Aug 3
- Overlap
- 5 of 7 days the rollout covered most of your window
- Honest read
- correlation, not confirmation ecosystem volatility ≠ your site was hit
Jul 19 to Jul 25, 2026
⚠ Observationalas of Aug 1, 2026 (documented event calendar, no account data read)IllustrativeOpen in Quattr ↗
With a Quattr account this becomes cause analysis on YOUR data, anomaly-investigator.
A simulated conversation on fictional data. Scope, freshness and the ⚠ Observational marker are attached by the same director that renders every demo here, not written by hand.
Want this Skill running on your own accounts? Every Quattr customer works with an AI Search Strategist who sets it up with you.