Why require positive positions?

Zeros are filtered to avoid divide-by-zero noise—remove trailing blanks in Sheets first.

Different keyword intents mixed?

Volatility compares within each row only; segment informational versus commercial lists separately for cleaner averages.

Can I plug Search Console directly?

Not inside this tool—reshape exports into the CSV pattern first.

Short series of two weeks?

Needs at least three numeric samples—wait for another data point or exclude the row.

SERP & Rankings

Live

SERP Volatility Tracker

Detect ranking turbulence to spot Google update impact.

X / Twitter LinkedIn Facebook

Rank time-series CSV

Header: keyword,p1,p2,p3,... (positions over time)

0.32

Avg CV

stable

moderate

volatile

very-volatile

Per-keyword volatility

volatile-keyword

very-volatile

avg pos 10.0 · σ 6.4 · CV 0.64 · range 21

seasonal-keyword

volatile

avg pos 18.3 · σ 9.1 · CV 0.50 · range 31

trail running shoes

volatile

avg pos 10.8 · σ 3.3 · CV 0.31 · range 17

hiking boots

moderate

avg pos 4.0 · σ 0.4 · CV 0.11 · range 4

sustainable running

stable

avg pos 11.6 · σ 0.5 · CV 0.04 · range 11

Start here · Why measure SERP volatility

Volatile keywords swing positions week to week, suggesting algorithm churn, fierce competition, or unstable intent maps—useful for prioritizing which terms deserve extra monitoring.

Each data row starts with the keyword then at least three positive numeric positions in chronological order. Empty or zero cells drop out before stats run.

Coefficient of variation (σ / mean) drives verdicts: stable below 0.1, moderate below 0.3, volatile below 0.5, and very-volatile above. Sparklines visualize each series; the dashboard also averages CV across rows and buckets counts per verdict.

When to use this tool

Stakeholder expectation setting
Show leadership which head terms bounce so ROI forecasts include wider confidence bands.
Testing cadence planning
Schedule more frequent rank checks for very-volatile keywords.
Partnering with PPC
Align paid support on queries whose organic positions oscillate.
Post-update triage
After core updates, separate structural losers from normal noisy SERPs.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

Flat query

Try this

Positions repeat within a narrow band across weekly columns.

What to look for

Low CV lands in stable with a tight sparkline—safe for slower reporting cadence.

Roller coaster

Try this

Weekly positions swing from single digits to twenties repeatedly.

What to look for

High CV triggers very-volatile and a jagged sparkline needing qualitative SERP review.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

Step 1 — Gather time-ordered positions
Export the same keyword list across equal time spacing where possible.
Step 2 — Format CSV header
Start each line with keyword then p1,p2,... without gaps inside the row.
Step 3 — Paste into the textarea
Include every monitored keyword in one run for comparable averages.
Step 4 — Interpret summary tiles
Average CV plus bucket counts describe portfolio shake versus calm.
Step 5 — Pair with rank deltas
Use rank change alerter for two-point comparisons when volatility explains large swings.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

SERP Volatility Tracker does one job: detect ranking turbulence to spot Google update impact. It lives under SERP & Rankings on SEOToolkits, where the beginner idea is simple: SERP SEO studies the search results page itself: rankings, snippets, features, and what Google is rewarding.

FAQ

Why require positive positions?: Zeros are filtered to avoid divide-by-zero noise—remove trailing blanks in Sheets first.
Different keyword intents mixed?: Volatility compares within each row only; segment informational versus commercial lists separately for cleaner averages.
Can I plug Search Console directly?: Not inside this tool—reshape exports into the CSV pattern first.
Short series of two weeks?: Needs at least three numeric samples—wait for another data point or exclude the row.