Guides

Ride the update radar

The radar watches Google's official search channels, puts confirmed ranking updates on a public timeline, and maps the actionable ones to executable checks — with webhook, MCP and digest delivery.

Updated 2026-11-11

On this page

Guide · radar

Google updates on a public timeline, mapped to the checks we run — and three channels that tell you when something moved.

  1. What the radar watches

    Every day we read the Google Search Status Dashboard and the Search Central blog. Confirmed core, spam and ranking updates go onto the public timeline, and the ones we can map to an executable check also get a detail page. Triage levels stay internal; public badge copy uses plain language such as Act now or Watchlist.

  2. Browse the public timeline

    /radar is the complete official timeline — updates with no checks stay listed. A /radar/<slug> page covers one update, not a rule: only updates with checks have a detail page. Public checker explainers live at /checkers, and the full rule library is in the Checks tab after you sign in.

    Text
    https://<your-app-url>/radar            ← official timeline (all confirmed updates)
https://<your-app-url>/radar/<slug>     ← one update, its checks and verdicts
https://<your-app-url>/checkers         ← the public checker library

  3. Get updates: webhook, MCP, digest

    Priority update pushes ride the same webhook infrastructure as audit events, the MCP tool answers “what changed?” inside any coding agent, and the digest summarizes the day for people who prefer email. Pick one channel or all three; nothing here consumes API quota.

    Text
    # webhook event (monitoring:write key, see the webhooks guide)
"events": ["audit.finished", "update.p0"]

# MCP tool (radar:read scope)
get_radar_updates  →  active-rule counts, latest update entries

  4. From radar check to audit finding

    Rules with check items become audit checks. When a check fires on your site, the next audit reports it as a finding linked to the check it maps to; when the condition clears, the next audit resolves the finding automatically — findings are never closed by hand.