Position change alerts

A single position is a snapshot; a position change is a signal. Knowing that a keyword fell from 4 to 19 overnight is what turns rank tracking from a vanity dashboard into an early-warning system. This article explains exactly how the change number is derived, how to monitor for meaningful drops, and how VisibilityIQ stores ranking history so old data stays useful without growing without bound.

What you’ll need

A configured rankings connector with at least two completed syncs — a change requires a previous and a current position to compare (see Setting up rank tracking).
A sync cadence that matches how closely you need to watch — daily for volatile commercial terms, weekly for most sites.

How position change is computed

For every keyword on every sync, VisibilityIQ stores position_change = current_position − previous_position. The direction follows the SEO convention, which is the opposite of ordinary arithmetic intuition:

Negative = improved. Moving from 10 to 5 yields −5. Smaller rank numbers are closer to position 1.
Positive = dropped. Moving from 5 to 10 yields +5. You moved away from the top.

Sort your change column ascending to surface your biggest wins, descending to surface your biggest losses. A keyword with no previous position (newly tracked, or freshly re-entered the top 100) has no change value until the next sync establishes a baseline.

Monitoring drops

Not every change deserves attention. Daily checks naturally wobble ±1–3 positions because Google personalises results and tests orderings. Filter for the signal:

Single-day drops of 10+ positions are worth investigating immediately. The usual culprits are a page going noindex, a canonical change, a site migration, or an algorithm update affecting your niche.
Sustained drift — a keyword sliding a few positions every sync for a week — often signals a competitor strengthening their page or your content going stale.
Drops on transactional or commercial keywords outrank drops on informational ones in priority, because they map directly to revenue. Cross-reference the intent label when triaging.

A keyword that vanishes from the list entirely has most likely fallen past position 100, which is the point beyond which positions are not synced.

Recommended review cadence

Match your review rhythm to your sync cadence. For a weekly sync, a weekly review of the largest positive changes catches problems while they’re still cheap to fix. For daily syncs on a fast-moving commercial site, scan the top drops each morning. Don’t react to single-day noise — confirm a drop persists across two consecutive syncs before treating it as real, unless the magnitude is large enough (10+) to act on immediately.

History compression

Ranking history would grow unbounded if every daily row were kept forever, so VisibilityIQ compresses it. Full daily rows are retained for 90 days. Beyond that horizon, only the weekly Monday snapshot is kept, which preserves the long-term trend line while shedding day-to-day noise you’d never query. This keeps year-over-year comparisons meaningful without bloating the database. Compression runs on a schedule, so no action is required on your part; just be aware that change calculations more than 90 days back are computed against weekly, not daily, baselines.