Anomalies Snapshot
Anomalies Snapshot is Metricstab's statistical alarm for your top-line traffic. It surfaces individual days inside the selected reporting period whose clicks or impressions deviated unusually far from that period's own baseline — so you can stop eyeballing the trend chart and immediately know which dates deserve a closer look. This page documents exactly how the signal is computed, every type of anomaly you can see, how to read each tile, and the playbook for turning each pattern into action.
What it is
The Anomalies Snapshot highlights up to five days inside the currently selected reporting period where one of your two top-line metrics — clicks or impressions — deviated unusually far from the period's own typical day.
It is purely a statistical alarm on your existing trend data: no machine learning, no external benchmarks. The same days that look like spikes on the trend chart will surface here, ranked by how unusual they are rather than by absolute size.
How we compute it
- For the selected date range, we collect the daily clicks and impressions reported by Search Console for your site.
- Across those days we calculate two summary numbers per metric: the average (μ) and the standard deviation (σ) — a measure of how much a typical day varies from the average.
- Each day is then scored by how far it sits from the average, in standard-deviation units:
z = (day's value − average) / standard deviation. This is the z-score. - Days where
|z| ≥ 2.0on either clicks or impressions are flagged — these are days more than two standard deviations away from the mean. - If a day trips on both metrics, we keep the one with the larger absolute z-score so each day appears only once.
- Flagged days are sorted by
|z|(most unusual first) and the top five are shown.
|z| ≥ 2 day is roughly
the most unusual 5 % of days statistically — useful as a "look here first" filter, not a strict
alarm.
How to read each tile
- Spike — a day with an unusually high value on the louder metric.
- Dip — a day with an unusually low value.
- σ chip on the right (e.g.
+2.4σ) — how many standard deviations away from the mean. Bigger absolute value = more unusual. - Date — the calendar day the anomaly was observed.
- Detail line — the actual metric value alongside the period's baseline (e.g.
1,240 clicks vs ~480 baseline).
The header summary line shows the sample size (number of days analysed) and the baseline clicks/day used for the calculation.
What to do with it
Anomalies are the start of an investigation, not the end. A few useful next steps:
- Cross-check the date against your Annotations panel — releases, PR coverage, campaigns.
- Check the Top Movers breakdown to see which queries or pages drove the surge.
- If the spike is sustainable (a new ranking, viral content), think about how to defend the gain.
- Look at Content Decay and Cannibalization for ranking-loss patterns.
- Review the Index Coverage data for crawl/indexing regressions on key pages.
- Compare to Device and Country Breakdown to check whether the dip is concentrated in one segment.
Caveats & limits
- Short ranges are noisy. With fewer than ~10 days, σ becomes very small and almost any movement looks like an anomaly. Prefer ranges of 28 days or longer.
- Trend periods bias the baseline. A range that already contains a permanent step-change (e.g. a new section launched mid-period) will pull μ toward the new normal. Slice the range around the change for a cleaner read.
- Weekly seasonality isn't decomposed. Sites with strong weekday/weekend rhythms may flag every Sunday as a dip; cross-check with the trend chart's weekly view before drawing conclusions.
- "Both metrics" days collapse to one tile on the louder metric — open the trend chart for the full picture.
Related reports
- Traffic Trend — the underlying daily series; flagged days appear as markers.
- Top Movers Breakdown — which queries/pages contributed to the day's swing.
- Content Decay — for diagnosing dips traced to ranking loss.
- Annotations — to capture context that explains future anomalies.