Features
Alerts and observations
The “Alerts & observations” view brings two threads together: the alerts monitoring opened from your measured data, and the runs of your AI prompt groups. Everything in it is recorded; nothing is estimated.
What the view shows
A timeline, newest first, of the site's latest 30 alerts and latest 10 AI runs that completed, partly completed or failed. Each row carries its date, its severity and the measurement behind it (“Measured: …”) or “Impact: not measured”. “See details and resolution” opens the alert's panel.
| KPI | Reading |
|---|---|
| Open alerts | Unresolved alerts for this site, whatever their date. |
| Critical / Warnings | Severity of the listed observations; a failed AI run counts as a warning. |
| Runs observed | Runs of your prompt groups among the latest 10. |
| Resolved alerts | Alerts closed among the latest 30: the condition stopped or the alert expired. |
| Monitoring | “On” when a scheduled analysis runs for the site or a connected Search Console or GA4 connector is checked daily. |
Monitoring
Two mechanisms feed the alerts:
- Daily checks, for every site whose workspace has a Search Console or GA4 connector in the connected state: Search Console clicks and average position, GA4 sessions. They read only the figures synced from Google.
- Scheduled analysis: plans that include continuous analysis get a weekly analysis of the site after the first completed analysis. Each analysis is compared with the previous one.
The “Latest checks” block gives, for each daily check, its latest pass and the day of data it stood on: “Quiet as of …”, “Change detected, alert open”, “Not enough history to judge yet”, or “Change detected, not recorded: open-alert ceiling reached”. With no check yet: “the first one runs on the next daily pass”.
Alerts and their thresholds
| Alert | Source and rhythm | Trigger |
|---|---|---|
| Search Console clicks anomaly | The site's daily clicks, every day | The latest day departs strongly from its own history (at least 14 days of history) and by at least 20 % of the median, down or up |
| Search Console position drop | Average position, every day | The last 7 days rank at least 2 places and 25 % worse than the 28 days before, with at least 200 impressions on each side and 14 days of baseline |
| GA4 sessions drop | GA4 sessions, every day | The latest complete week is at least 30 % below the weekly mean of the previous weeks (at least two complete weeks, at least 200 sessions per week); the latest day, still being processed by Google, is left out |
| New technical anomalies | Comparison of two analyses | Audit findings absent from the previous crawl; the panel lists the codes that appeared and opens each in the audit |
| Measured traffic decline | Comparison of two analyses | Sessions measured by the connectors fell by at least 20 % since the previous analysis |
The “Critical” or “Warning” severity depends on the size of the change. To understand the data itself, see Search Console history and Traffic and market; for technical findings, the technical audit.
The alert email
- A new alert gives rise to one email, once: an alert that persists sends no reminder. An email with no measured figure to show is not sent.
- It goes to the organisation's first active member (the longest-standing), in French or English according to their language.
- For clicks, positions and sessions, the email carries the alert's figures (baseline, recent value, day of data); for alerts raised by an analysis, the comparison of the last two crawls.
- The email contains an unsubscribe link.
How an alert closes
- Positions and sessions: the alert closes when the measurement is clearly back, under half the threshold; a series hovering around the threshold does not reopen an alert every day.
- Clicks, positions, sessions: an alert no longer observed for 14 days expires.
- New technical anomalies and traffic decline: they stay open; they do not close by themselves when the problem goes away.
- There is no button to close an alert by hand.
AI observations
Each run of a prompt group appears as “AI observation completed”, “AI observation partly completed” or “AI observation failed”, with the group's name and the number of answers recorded. Runs are started from AI prompt groups or AI visibility, and with every analysis; their states are described in Run states.
When the view is empty
- “No continuous monitoring is active for this site”: connect Search Console or GA4 (integrations) or move to a plan that includes continuous analysis (plans).
- “Monitoring is active and has not detected anything for this site yet”: nothing crossed a threshold.
- Daily checks need history: a recent connection shows “Not enough history to judge yet” for the first weeks.