More accurate performance metrics when keywords drop out of range (OTR)

We’ve fixed a long-standing blind spot in how performance metrics handle keywords that fall out of the tracked range (OTR).

Previously, if a keyword dropped from a high position (e.g. Top 3) to OTR, it could be ignored in calculations. This sometimes resulted in misleading metrics, like showing positive movement when rankings had actually declined.

Now, you can control how OTR keywords are treated across all performance metrics:

New setting: “

Out of range behaviour”

Exclude (default): keeps current behaviour, ignores OTR keywords in comparisons
Count as dropped: treats OTR as “not ranked”, reflecting real declines in metrics

Why this matters

Fixes trust issues in key metrics like Movement since start and Top N changes
Ensures drops out of ranking are properly reflected
Removes the need for manual cross-checking between keyword table and dashboard
Gives you control depending on your workflow (clean reporting vs strict accuracy)

This applies everywhere: dashboard, project overview, reports, emails, and exports.