Every Google algorithm update, on the same timeline as your changes.
When organic traffic moves, the first question is always “was it Google, or was it us?” CoNote logs every core and spam update rollout — start, completion, and the official announcement — so a ranking shift sits right next to the algorithm update and the changes you shipped that week.
June 2026 core update — rollout started
Google Algorithm Updates· 17:00
Migrated blog to a new URL structure (main → 9c1d4e2)
GitHub· 09:20
What it watches
What it logs.
Google’s official algorithm rollouts — the ones that actually move rankings — straight from the source.
- Core updates and spam updates, as Google announces them
- Both the rollout start and its completion
- Drawn from Google’s official announcements — not rumour or chatter
- Lined up against your deploys, content, and Search Console events
On the timeline
What lands on your timeline.
The rollout, on the page — so a ranking shift has an obvious suspect to rule in or out.
Monday, June 8
June 2026 core update — rollout started
17:00 · Google Algorithm Updates
Official announcement — expect 1–2 weeks to fully roll out
17:05 · Google Algorithm Updates
Sound familiar?
The day you’ll wish it was written down.
Sara10:20
Tom10:24
Sara10:28
Google’s update and your own change blur into one bad week.
With this on your timeline, the core update is already there — “June 2026 core update — rollout started” — on the exact week your rankings moved, next to the migration you shipped.
Setup
On by default.
- 01
Nothing to connect
There’s no account to authorize — CoNote watches Google’s official update announcements for you.
- 02
Rollouts log themselves
When Google starts or completes a core or spam update, it lands on your timeline with the date.
- 03
Read it in context
The update sits next to your deploys, content changes, and Search Console events — so a ranking shift has its suspects on one page.
Questions
Google updates on the timeline, answered.
Google’s confirmed core and spam updates — the rollout start, its completion, and the official announcement — each as a plain-language entry with the date. Unconfirmed “algorithm chatter” isn’t logged; only what Google announces.
From Google’s own official announcements of ranking-system updates — the authoritative source — not from third-party rumour or volatility trackers.
No. It’s a built-in source — there’s no account to connect. Confirmed updates appear on your timeline automatically.
No — it logs that the update happened and when. Whether your site was affected is something you read from your own rankings and Search Console data; having the rollout on the timeline lets you line the two up.
Because when traffic moves, the first question is “Google or us?” With the rollout already on the page next to the deploys and content changes you shipped, you can answer it instead of guessing weeks later.
Keep digging
Track the rest of your stack.
Open the logbook.
Free plan, no card. Connect your first source and the timeline fills itself.
Start your logbook