Drift: when a score falls below its own normal range
We compare each pillar against its own history, so an alert means genuinely unusual movement, not a number crossing an arbitrary threshold.
What it is
After every analysis we compare each measured pillar against its own trailing history for your site. When a score falls outside its normal range and the drop is materially large, it is recorded as a measured finding.
When to use it
It runs automatically. Read drift findings first when reviewing an analysis — they flag what changed, as opposed to what has always been low.
Step by step
- 1Run Analyze a few times so there is a baseline to compare against.
- 2Open Analyze and read the findings list. A drift finding names the pillar, the size of the drop, and the normal range it fell out of.
- 3Cross-check What Changed on the same page — where we can attribute the movement to a measured cause, it says so.
What you will see
A finding such as “Technical Health dropped 12 points below its normal range”, with the trailing average, the range, and how many prior runs informed it.
Measured, never manufactured
Your first run raises nothing. A first observation is a baseline, never a regression — the same rule the AI Overviews tracker follows. Drift also only ever compares runs measured under the same scoring methodology: if we change how a pillar is computed, that is our change, and reporting it to you as your regression would be dishonest.
Related guides
Next
What Changed, and whyA measured diff between your last two runs, with the cause named whenever we measured it on both sides.