What this does
Every day it pulls your Search Console data, compares each page and query against its own recent baseline — not against a global average, which is how anomaly detection usually fails — and alerts only when something genuinely deviates.
The alert names the page and the query. You are not told “traffic is down.” You are told
“/pricing lost 62% of impressions on crm for agencies starting Tuesday.”
Why baselines are per-page
A site-wide threshold drowns in normal noise. A page that reliably gets four impressions a day dropping to zero is a real signal. A page that gets four thousand a day swinging by 15% is Tuesday. Per-page, per-query baselines are the only way to tell those apart, and it is the part most off-the-shelf alerts skip.
What you get
- The workflow file and the cron schedule
- The baseline configuration: window length, sensitivity, and the exclusion list for pages that are genuinely seasonal
- A setup document for the API credentials and the alert channel
- A short note on tuning: start less sensitive than you think you want, because an alerting system that cries wolf gets muted and then it is worth nothing
This one is free
No email required. Search Console anomalies are the most common cause of a “why is my traffic down” call I get, and the answer is almost always that the drop was visible for weeks before anyone looked.