Only What Changed Alerts
Threshold-filtered alerts that fire only when one of five overnight signals crosses a team-set bar.
Only What Changed Alerts notify the team when one of five overnight signals crosses a threshold the team sets, pushing to Slack, email, or webhook with a one-click ticket attached.
How it works
Five specific signals are tracked every night rather than vague anomaly detection across many metrics. The team sets a numeric threshold per signal that filters out noise, so an alert fires only when a change crosses that bar. When a signal fires, the alert pushes to the destinations the team configured, each carrying the affected page, the change detected, the threshold crossed, and a one-click button that creates a ticket in the team's project tracker. The morning report holds the full daily summary; live alerts are the urgent subset that warranted an immediate push.
Key capabilities
- Five overnight change signals: new errors, score drops, new orphan pages, broken page data tags, and position drops (the latter from the Google Search Console connection).
- A configurable numeric threshold per signal that the team controls independently and can tighten or loosen by season; error and orphan-page signals fire on the binary healthy-to-broken transition.
- Push delivery to Slack channels, email inboxes, and webhook endpoints, singly or in combination.
- A one-click ticket button that pushes work into Asana, ClickUp, Trello, or Linear with the page, signal, suggested fix, and priority.
- Grouped alerting for bulk changes, so a site-wide regression produces one alert rather than one per page.
- Time-bound muting per signal for planned migrations or editorial sprints, logged for an audit trail.
Tips
Set thresholds per signal to match your operation. A high-stakes ecommerce site might keep tight thresholds on position drops but looser ones on score drops, while an evergreen content site might do the reverse. See Site Inspector for the full nightly report these alerts draw from.