📊
Ranking movement
Positions across organic links, AI Overview sources and answer-engine citations — checked on your schedule, per keyword, location and device. Every gain, drop and disappearance is flagged with the exact before/after.
Recurring pulls · snapshot diffs · alerts
Know the moment a SERP changes — before your report does.
Rankings drift, AI Overviews rewrite themselves overnight, and the sources an engine cites turn over without warning. cloro schedules repeat pulls, snapshots every result, and fires an alert the instant a position, citation or answer shifts on the queries you watch.
● Google & 7 AI engines
● Webhook & email alerts
● Diff on every capture
🔔 Change feed
WATCHING · 142 queries
- ▼ RANK "best crm for startups"google · us-desktop 2m ago
- ✦ CITED "how to reduce churn"perplexity 14m ago
- ▲ RANK "headless cms comparison"ai overview 31m ago
- ✎ ANSWER "is postgres good for analytics"chatgpt 1h ago
- ▼ DROPPED "cheapest object storage"google · uk-mobile 2h ago
ChatGPT
Gemini
Perplexity
Copilot
Grok
AI Overview
AI Mode
Google Search
What gets watched
Three kinds of change, one alert stream
A SERP isn't one number anymore. cloro tracks the whole result surface and tells you exactly which layer moved.
🔗
Citation turnover
The domains an answer engine cites shift constantly. Get told when a source is added, dropped or reordered in the answer.
✎
Answer rewrites
The synthesized text itself changes. cloro diffs the answer body so you catch new claims, framing and recommendations.
How monitoring runs
Set a cadence, cloro does the rest
Register a watch
Point a monitor at a query, engine, location and device, and choose how often to re-pull — hourly, daily or on a custom cron.
Snapshot & diff
Each run captures a full structured snapshot and compares it against the last one, computing exactly what changed and by how much.
Alert on change
When a threshold is crossed, cloro posts a webhook and emails your team — with the diff, both snapshots and a link into the timeline.
snapshot.diff · "best crm for startups"
engine: "ai_overview" region: "us" device: "desktop" captured: 2026-08-13T09:00Z vs 2026-08-12T09:00Z sources_cited: - 1. techradar.com + 1. cloro.cloud/blog 2. g2.com + 3. capterra.com (new) - 4. old-review-site.net (dropped) answer_text: - "...tools like Tool A lead the market..." + "...tools like Tool A and Tool B now lead..." change_score: 0.41 triggered: rank, citation, answer
Snapshot diffs
Every run is a versioned, comparable record
cloro doesn't just tell you something changed — it shows you the line-level difference between the current capture and the one before it, so an alert arrives with proof attached.
- Full structured snapshot stored on every scheduled pull
- Line-level diff of citations, ranks and answer text
- A single
change_scoreto gate noisy alerts - Point-in-time replay — pull any past snapshot back by timestamp
One request
Schedule a monitor in a single call
Describe the query, the cadence and where to send alerts. cloro handles the recurring fetch, the snapshotting, the diffing and the delivery — you just receive the events.
- Cron or interval scheduling, down to hourly
- Per-monitor alert thresholds and channels
- Signed webhook payloads plus optional email
- Pause, edit or replay any monitor by id
POST /v1/monitors
# watch a query and alert when the SERP shifts curl https://api.cloro.cloud/v1/monitors \ -H "Authorization: Bearer $CLORO_KEY" \ -d '{ "query": "best crm for startups", "engines": ["google", "ai_overview", "perplexity"], "location": "us", "device": "desktop", "schedule": "0 */6 * * *", "alert_on": ["rank", "citation", "answer"], "threshold": 0.2, "notify": { "webhook": "https://hooks.example.com/serp", "email": "[email protected]" } }' # → created { "monitor_id": "mon_7Qa3kZ", "status": "active", "next_run": "2026-08-13T12:00:00Z", "snapshots_kept": 90, "billing": "per successful run" }
Change timeline
Every shift, kept in order
Each monitor keeps a running history you can scroll, replay and export — so a ranking drop is never a mystery about when and what else moved.
▲
2026-08-13 · 09:00 UTC
Reclaimed the top AI Overview citation
Your domain moved into the first cited source for "best crm for startups", displacing a review aggregator that had held it for nine days.
✎
2026-08-12 · 21:00 UTC
Answer text rewritten overnight
Perplexity re-synthesized its answer for "how to reduce churn", adding a second recommended approach and a new cited study.
▼
2026-08-12 · 03:00 UTC
Slipped off page one on mobile
"cheapest object storage" dropped from position 4 to 9 on UK mobile Google, while a competitor's comparison page entered the featured snippet.
✦
2026-08-11 · 15:00 UTC
New competitor entered the answer
ChatGPT began naming an additional vendor for "headless cms comparison" that had not appeared in the previous 30 snapshots.
Delivery
Alerts where your team already works
🪝
Signed webhooks
Every change posts a JSON event to your endpoint, signed so you can verify it came from cloro. Pipe it into Slack, a queue or your own workflow.
POST /your-endpoint
✉️
Email digests
Prefer a human-readable heads-up? Get a per-monitor email with the diff inline and a link into the timeline — instant or rolled into a daily digest.
[email protected]
🎚️
Thresholds & quiet
Tune sensitivity per monitor with a change_score threshold, so a reordered footnote stays quiet while a lost first position always rings.
"threshold": 0.2
8engines you can watch
1hminimum pull cadence
90snapshots kept by default
195+locations to monitor from
🛰️
What teams monitor
A handful of high-value queries, watched continuously, catches the moves that a monthly rank report misses entirely.
Money keywords6h
AI answer citationsdaily
Competitor launcheshourly
Who it's for
For teams who can't wait for the next report
- SEO & GEO teams — catch ranking and citation drops the day they happen, not at month-end
- Brand & PR — get pinged when an answer engine changes how it describes you
- Competitive intel — know the hour a rival enters an AI answer or a featured snippet
- Agencies — run always-on monitors across a whole client roster from one key
Questions
SERP monitoring, explained
How often can cloro re-pull a query?
Down to hourly on standard monitors, scheduled with a plain interval or a cron expression. Each run is an independent, structured capture, so you can watch high-stakes queries frequently and lower-priority ones daily.
What exactly counts as a "change"?
Three layers: ranking movement (a position gained, dropped or disappeared), citation turnover (a source added, removed or reordered in an answer), and answer rewrites (the synthesized text itself changing). Each run produces a single change_score so you can decide how sensitive an alert should be.
How do alerts reach my team?
Every triggered change posts a signed JSON webhook to your endpoint and, optionally, sends an email with the diff inline. Payloads include both snapshots, the computed diff and a link into the monitor's timeline.
Can I monitor AI answer engines, not just Google?
Yes. A single monitor can watch Google Search alongside ChatGPT, Gemini, Perplexity, Copilot, Grok, AI Overview and AI Mode — each returned in the same schema so the diffs are directly comparable.
Are past snapshots kept?
By default cloro retains the last 90 snapshots per monitor, and you can pull any of them back by timestamp for point-in-time replay or export. Retention is configurable per monitor.
How is monitoring billed?
Per successful monitored run. A pull that fails or returns nothing isn't billed, and your live usage counter reflects exactly what each monitor has consumed.
Stop refreshing the SERP by hand.
Point a monitor at the queries that matter, pick a cadence, and let cloro tell you the moment anything moves.