Monitoring & reporting
Alerts
What it's for
Automatic notifications when something important changes — e.g. the health score drops sharply, new critical issues appear, or rankings fall — so you react in hours, not at the next manual check.
When to use it
- On any production site you can't check daily.
- After a big launch, to catch regressions immediately.
How to use it
- Project → «Alerts»; review the configured rules.
- Adjust thresholds to your tolerance.
- When an alert fires, open the linked crawl/Compare.
Reading your results
For each output: is it good, does it need improvement, or is it bad — and exactly what to do next.
Alert severity
Good
No alerts / only Low: things are stable.
Needs improvement
Medium: a noticeable change — review when convenient.
Bad
High (e.g. a 25+ health-score drop): act now.
What to do next
Open the crawl named in the alert, use Compare to find the cause, fix, and re-crawl to clear it.
Next steps
- Tune noisy rules so High always means «drop everything».
- Route alerts to email/webhooks for your team's workflow.