Google Search Console change history, next to the change that caused it.
Search Console records what happens to your site — manual actions, coverage drops, sitemap errors — but each lives in its own report, never next to the deploy or content change behind it. CoNote will put those events on one shared timeline, beside the change from the same day.
Google Search Consolepublished a changeCoverage dropped — 1,240 pages no longer indexed
Search Console· 16:40
Migrated blog to a new URL structure (main → 9c1d4e2)
GitHub· 09:20
Finding your history
Your Search Console history: today, and once CoNote is live
The manual way · inside Search Console
Where to find it today
It’s spread across reports — if you go digging:
- 1
Open Search Console
Go to search.google.com/search-console and pick the property you need — each domain or prefix is tracked separately.
- 2
Check Manual Actions
Open Security & Manual Actions → Manual actions to see any penalty Google has applied, and whether it’s still active.
- 3
Review Page Indexing
Under Indexing, open Pages to see indexed vs. not-indexed counts over time, with the reason each page dropped out — this is where a coverage drop shows up.
- 4
Open the Sitemaps report
Under Indexing, open Sitemaps for each submission, its processing status, and any errors Google hit reading it.
- 5
Stitch the dates together by hand
Each report stands alone, the data ages out after about 16 months, and nothing lines an event up against the deploy or redirect that caused it — so you reconstruct that yourself.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect Search Console once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Manual actions, sharp coverage changes, and sitemap errors will be waiting — no report-hopping inside Search Console.
- 2
Jump to the day traffic moved
Scan the day organic traffic dipped; the coverage drop or manual action will be stamped right there.
- 3
See it beside everything else
The event will sit next to that day’s deploy, redirect, or content change — the likely cause is right there.
Sound familiar?
Search Console tells you what happened — not why.
Sara09:05
Tom09:09
Sara09:13
Tom09:18
The deploy and the coverage drop sit in two different tools.
It records the event — a manual action, a coverage drop, a sitemap error — but never lines it up against the deploy, redirect, or content change that caused it.
- Each report stands alone — coverage here, manual actions there, sitemaps elsewhere
- Locked inside Search Console, where engineering and leadership never look
- Never lined up against the deploy or content change from the same day
- Coverage and performance data ages out after about 16 months
Once Search Console is connected, the event will already be on the timeline — “Coverage dropped: 1,240 pages no longer indexed” — on the day it happened, next to the URL migration that caused it.
How it works
Connect once. Then it’ll log itself.
- 01
Authorize with Google
A two-click Google authorization — read-only on your Search Console property. CoNote will read the events Google records, nothing else.
- 02
Key events will log themselves
CoNote will check on a schedule and log the events that matter — manual actions, sharp coverage changes, and sitemap errors — each as a readable entry the day it happens.
- 03
Read it in context
The event sits beside that day’s deploy, redirect, or content change. When traffic moves, you scan one page instead of three separate reports.
What lands on your timeline
- Manual actions reported or lifted by Google
- Sharp coverage and indexing changes
- Sitemap submissions and processing errors
In your week
What teams will use it for.
Traffic dropped — algorithm or our own change?
Organic traffic dips. The coverage drop sits next to the URL migration from the same day, so you can tell a Google-side change from one you shipped.
Pages fell out of the index
A batch of pages de-indexes. The coverage drop is dated right next to the redirect or robots.txt change that likely caused it — no cross-tool archaeology.
A manual action appeared
The penalty lands on the timeline the day Google reports it, beside whatever shipped that week — so you know where to start looking.
Prove the recovery
When the manual action is lifted, it’s logged and lined up with the fixes you shipped — a clean record of what you did and when it worked.
Side by side
Native reports vs. your logbook.
See manual actions, coverage, and sitemaps
Search Console reports
CoNote
One view across every event type
Search Console reports
CoNote
Lined up against deploys, redirects, content
Search Console reports
CoNote
Visible to engineering and leadership
Search Console reports
CoNote
Kept beyond ~16 months
Search Console reports
CoNote
Setup
Search Console reports
CoNote
On the timeline
The event in context.
A coverage drop on its own is a mystery. Next to the URL migration from the same morning, it’s a diagnosis.
Tuesday, June 9
Migrated blog to a new URL structure (main → 9c1d4e2)
GitHub· 09:20
Coverage dropped — 1,240 pages no longer indexed
Search Console· 16:40
Sitemap error — 1,180 URLs returned 404
Search Console· 17:10
Questions
Search Console tracking, answered.
Not an edit history like some tools — instead it records events about your site. Manual actions live under Security & Manual Actions, indexing and coverage changes under Indexing → Pages, and submission history under Indexing → Sitemaps. Each report stands on its own.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch Search Console on automatically the day it ships.
A standard two-click Google authorization with read-only access to your Search Console property. It will never change your site, your settings, or anything in your account.
The events that matter for SEO — manual actions Google reports or lifts, sharp coverage and indexing changes, and sitemap submissions or errors — each as a plain-language entry with the date it happened.
From the moment you connect, every event is logged and kept for as long as your logbook exists — unlike Search Console’s own reports, which age out after about 16 months.
Search Console’s data is split across separate reports, inside Search Console, where only people with access ever look. CoNote will put those events on a shared timeline next to your deploys, redirects, and content changes — so you can line an SEO event up against the change behind it.
Only your team. Every entry is scoped to your team, and connecting Search Console won’t expose your property to anyone outside it.
Keep digging
Track the rest of your stack.
Open the logbook.
Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.
Start your logbook