Organic

The alert

The message that ends the argument

The two weeks a team loses to an organic decline are not spent fixing pages. They are spent establishing which of three things happened. This arrives with that already settled, on the day it happened.

O
OrganicAPP#eng-alerts
🔴 Organic sessions dropped −32.9%cluster=product-comparisons
Baseline
9342.53
Now
6272.56
Confidence
99.9%
Started
Aug 10
Property
www (4 clusters tracked)
Cluster
product-comparisons
URLs
412
Break
Aug 9
Likely cause · Position, impressions, and click-through all break on the same day for the product-comparison cluster and for no other cluster. The order rules out a tracking bug: a broken tag drops sessions without moving impressions or position, and this moved position first. It also rules out seasonality, since the other three clusters run through the same date unchanged. Total site sessions moved less than 3%, which is why the weekly report looked fine.
  1. 1.Pull the 412 comparison URLs and diff serving position by query before and after Aug 9.
  2. 2.Split impressions by surface to see whether the loss is classic search, the answer-engine panel, or both.
  3. 3.Check whether the lost queries are now answered inline without a click, which is a different problem from a ranking loss.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
O
OrganicAPP#eng-alerts
🔴 Average position jumped +69.3%cluster=product-comparisons
Baseline
6.341
Now
10.737
Confidence
99.9%
Started
Aug 9
Property
www (4 clusters tracked)
Cluster
product-comparisons
URLs
412
Break
Aug 9
Likely cause · Position, impressions, and click-through all break on the same day for the product-comparison cluster and for no other cluster. The order rules out a tracking bug: a broken tag drops sessions without moving impressions or position, and this moved position first. It also rules out seasonality, since the other three clusters run through the same date unchanged. Total site sessions moved less than 3%, which is why the weekly report looked fine.
  1. 1.Pull the 412 comparison URLs and diff serving position by query before and after Aug 9.
  2. 2.Split impressions by surface to see whether the loss is classic search, the answer-engine panel, or both.
  3. 3.Check whether the lost queries are now answered inline without a click, which is a different problem from a ranking loss.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
Reading average position

Position 4 beats position 9, so average position is the one metric here where a rise is the bad direction. It carries an inverted flag through the engine, which is why the alert calls a 69% increase a regression rather than an improvement. Getting that sign wrong is how ranking dashboards end up cheerful during a collapse.