Find out first, and make it somebody’s job.
Know about the drop before anyone has to ask — rules and anomaly detection watch each day's numbers as they land, and whatever fires joins a queue with an owner, a status and a due date.
Two ways something reaches the queue.
One you write. One you do not have to.
- Rules you write
- Hear about it the day a number crosses your line — a metric, a condition and a threshold, checked against the previous period as each day's data lands. Rules pause rather than delete.
- Anomaly detection
- One freak day can't hide the next real drop — anomalies are scored against a typical day, not an average one.
- The task queue
- What fires becomes an owned task with a status and a due date, and the work lands in whichever tracker your team already uses.
Log what you shipped. Let the chart judge it.
An annotation takes ten seconds on the day you ship, and turns the note into a claim the data either supports or does not.
- Ten seconds to log
Name the release, pick the day. The annotation sits on every performance timeline from then on.
- A verdict, not a memory
Each one carries a before-and-after click comparison over its own measurement window.
- On the report too
The scheduled report's chart carries your annotations, so a spike arrives with its explanation attached.
Alerts fire on numbers Google has finalised.
Alerting runs on your Search Console metrics — the figures Google settles every day. Everything else Prism watches is monitored and reported on its own page.
- Search Console metrics
- The alerting source. Clicks, impressions, CTR and average position, site-wide: your rules plus automatic anomaly detection, evaluated on every daily sync.
- Site Health findings
- Found on every crawl, classified by effect on traffic in Site Health, and surfaced in the triage queue where they become owned tasks.
- AI answer visibility
- Measured on every scheduled run and reported across the AI Visibility suite, with every answer stored word for word.
- GA4 conversions
- Reported in Traffic on the same dates as your search data, and used to price how much a task is worth doing.
Frequently asked questions
What can an alert rule watch?
Clicks, impressions, click-through rate and average position, site-wide, from Search Console. A rule is a metric, a condition (drops by a percentage, rises by a percentage, or crosses a threshold) and a number. Rules are evaluated against the current period and the one before it on every Search Console sync.
What is anomaly detection doing that my rules are not?
It catches the drops nobody wrote a rule for. Prism keeps a rolling snapshot of each metric, takes the median of the last 28 days and the typical spread around it, and raises an incident when today sits far outside that range.
How does an alert reach me?
A fired alert lands as an in-app notification for the rule owner. What fires can become a task with an owner and a due date, and task creation fires a signed HTTPS webhook, so the work can land in whichever tracker your team already uses. The scheduled report goes out by email and in-app on the cadence you set.
How often do alerts run?
Daily, on every Search Console sync, aligned to when Google finalises its numbers. Every alert fires on a finalised figure you can act on.
Elsewhere in Prism
A fired alert does not stop at the queue
- Smart Campaigns Track a launch as one group of pages and queries over its own window, and compare it with the last one.
- Data warehousing Alerts are evaluated on the Search Console sync.
- Site Health Crawl findings live here, classified by effect on traffic.
- Reports The scheduled summary carries what fired during the period alongside the numbers.
More of the platform
- AI Visibility See exactly what ChatGPT says about your market: your prompts put to ChatGPT, Claude, Gemini and Perplexity on a schedule, every answer kept word for word, and the brands named on the days you were not. 18 reports.
- Search Performance Which queries have been sliding for six months, which of your pages are splitting a query between them, the dated moments Google changed the page it ranks for one. 16 reports over a Search Console warehouse that outlives Google's 16-month window.
- Site Health Severity says how alarming a crawl finding looks. Fix First classifies the same findings by what each one is doing to your traffic: broken while earning, recoverable losses, upside, housekeeping. 13 reports over one crawl.
- Traffic 4 reports off your GA4 property: Overview, Acquisition, Engagement, and Conversions & Revenue. Same property picker, same date range and same comparison period as Search Console, so clicks and revenue sit on one timeline.
- Brand Brands, products, competitors, sectors, audiences, topics and markets, edited once and used by every prompt, query and report. Standardize merges the name variants an answer engine throws at you so NIKE, Nike and Nike Inc count once.
- Reports One executive summary of the period, what moved it and the pages and queries behind the change, emailed to up to 20 recipients on a cadence you set. Every other report saves, shares by link and exports as CSV.
Set one rule. It runs every day.
Connect Search Console, arm a rule on clicks, and Prism checks it against the previous period on every sync from then on.