SERP volatility · Last updated July 2026
SERP volatility checker and tracker: the volatility index for your own keywords
The short answer
SERP volatility is how much Google's search results reshuffle from one day to the next. The public volatility checkers, Semrush Sensor, MozCast and Algoroo, each score it by re-running a fixed sample of roughly ten thousand keywords every day and publishing one aggregate number. That number tells you whether the wider index is moving. It cannot tell you whether your site moved, because your keywords are almost certainly not in the sample. To answer that, you need daily position history for the terms you actually rank for, which is what a rank tracker stores.
Serpstracker does not publish a market-wide volatility index, and the dashboard does not print a single volatility score. What it keeps is the whole Google top 10 for every keyword, every day, so you can see exactly which results churned and when. For the industry-wide reading, use one of the free sensors compared below.
Check a keyword now
Google rank checker
Live · checked today
Querying Google results…
Type any keyword and see today's top Google results (up to 10). Add your domain and we highlight where you rank. This is a live check of the positions the full product tracks for you daily.
- You
Track daily and get an alert the day it drops.
Live Google positions, no signup. One check is a snapshot. Volatility only becomes visible once you have the same keyword checked on consecutive days.
What counts as normal SERP volatility, and what counts as an event.
Google's results are never still. Personalization, freshness, index churn and ordinary re-crawling move positions every single day, so a keyword drifting between position 6 and position 8 across a week is not a signal of anything. The public sensors mostly normalize their readings onto a 0 to 10 scale, and the widely used rule of thumb is that anything above 7 means something broad is happening across the index. The bands below are how practitioners read those numbers in practice.
| Index score | What it usually means | What to do |
|---|---|---|
| 0 to 4 | Baseline churn. Ordinary daily reshuffling with no broad pattern behind it. | Nothing. Do not read a two place drift as a trend. |
| 4 to 6 | Elevated. Often a niche-specific reshuffle, or the quiet leading edge of a rollout. | Note the date. Keep working, but stop shipping risky changes. |
| 6 to 8 | High. Something broad is moving, confirmed or otherwise. | Log the start date so you can compare the week before against the week after. |
| 8 and above | Extreme, and usually an announced core or spam update mid-rollout. | Freeze non-essential changes and wait for the rollout to finish before judging anything. |
One caution about the scale. A high reading is evidence that the index is moving, not evidence that you were affected. During the May 2026 core update plenty of sites sat perfectly still while the sensors ran hot, and plenty of sites moved several places during a week when every public sensor reported a calm baseline. The score is weather for the whole country. Your rankings are the weather in your yard.
Every free SERP volatility checker, and what each one actually measures.
These are the tools people mean when they search for a SERP volatility index or ask what the volatility is today. All of them are free to read, and we do not compete with any of them, because none of them tracks your keywords. They are worth bookmarking. Check two rather than one, because their samples differ enough that they regularly disagree by a full point.
| Checker | How it reports | Strength | Limitation |
|---|---|---|---|
| Semrush Sensor | 0 to 10 score, updated daily, split by industry category and by desktop against mobile | The category split is the most useful feature in the whole field. Finance moving while health sits still is a real signal. | Aggregate of Semrush's own keyword sample, so a niche outside its categories is invisible. |
| MozCast | A weather metaphor reported as a temperature, from a daily sample of about 10,000 keywords | The longest running dataset, so historical context going back years is easy to read. | One number for the whole index, US-centric, with no way to filter to your niche. |
| Algoroo | A "roo" score with an interactive chart you drag to change the date range | Best for retrospectively pinning down the exact day something started moving. | Fixed keyword sample again, and the score is not directly comparable to the others. |
| Advanced Web Ranking | A free volatility tracker published alongside its paid rank tracking product | Useful cross-reference when two other sensors disagree. | Same structural sampling limit, and it is a marketing surface for the paid tool. |
| SE Ranking update tracker | Volatility by category plus a maintained timeline of confirmed Google updates | The timeline is the fastest way to check whether a date lines up with an announced update. | Confirms what already happened rather than telling you it is happening to you. |
| Serpstracker | No index. Daily position history and the full stored top 10 for the keywords you track | Answers the only question that pays: did my rankings move, on which terms, and who replaced me. | Covers your keywords only, so it will never tell you the state of the wider index. |
We sell a rank tracker, so read that last row with the appropriate suspicion. The honest summary is that these are two different instruments and you want both. Open a sensor to learn whether the index is moving. Open your own daily keyword position history to learn whether you are.
The blind spot every aggregate volatility score shares.
Each public checker re-runs a fixed sample of mostly high-volume, mostly US keywords once a day and compresses the result into a single figure. That design has three consequences worth understanding before you make a decision based on a reading.
01
Your keywords are not in the sample
Ten thousand keywords sounds like a lot until you remember Google handles billions of distinct queries. The odds that a commercial long-tail term you care about is in any sensor's panel round to zero. The sensor is measuring a different set of SERPs than the ones that pay you.
02
An average hides the interesting part
A quiet aggregate can contain a violent reshuffle in one niche, cancelled out by stillness everywhere else. This is exactly the reported pattern through mid 2026: several stretches where site owners saw large movement while the headline sensors stayed near baseline, because the movement was concentrated rather than broad.
03
A daily aggregate has no per-URL detail
Even when the index says the SERP moved, it will not tell you that you fell from 4 to 9, that two competitors entered the top 10, or that the result which replaced you was a forum thread. Those are the three facts that determine what you do next, and none of them survive being averaged into one number.
None of this makes the sensors bad. They answer the question they were built for, which is whether Google is in the middle of something. The mistake is treating that answer as a diagnosis of your site, and the cost of the mistake is real: teams rewrite pages that were never affected, and teams sit still through drops that had nothing to do with an update.
How to build a volatility reading for the SERPs you care about.
You need two things the public sensors cannot give you: the same keywords checked on a fixed daily cadence, and a stored record of the whole top 10 rather than just your own position. The second part matters more than people expect, because who replaced you is usually the explanation.
Step 1
Track daily, not weekly
A weekly check cannot distinguish a one day spike from a permanent loss, and it cannot date the start of a rollout to better than seven days. Every plan here checks every keyword every 24 hours for that reason. Weekly tracking is the single most common reason a team cannot say when their drop began.
Step 2
Keep the whole top 10, not just your rank
Every check stores the full ten results. Three months later you can still answer who was above you the day before a drop, which is impossible if the tool only kept your own number.
Step 3
Watch churn, not just position
The useful per-keyword measure of volatility is how many of the ten results changed since yesterday. A SERP where your position held but six of ten URLs turned over is far less stable than the number 7 next to your name suggests.
Step 4
Date the event, then wait
Log the first day movement appeared and compare the week before it against a week after the rollout finishes. Judging mid-rollout is how teams end up reverting changes that were working.
Two related pages go deeper on the mechanics: daily SERP tracking of the full top 10 covers what gets stored on every check, and rank drop alerts covers getting told the same day rather than finding out in a monthly report.
The Google updates behind 2026's volatility spikes so far.
When a sensor runs hot, the first useful question is whether the date lines up with something Google announced. These are the confirmed rollouts of 2026 to date, with the dates Google gave. Core updates have been landing roughly every three to four months, which puts the next broad one in the third quarter of 2026.
| Update | Rollout window | Duration |
|---|---|---|
| March 2026 core update | March 27 to April 8, 2026 | 12 days |
| May 2026 core update | May 21 to June 2, 2026 | 12 days |
Google's own advice on reading the aftermath is unusually specific, and most people ignore it. The guidance is to wait "at least a full week after a core update completes before analyzing your site in Search Console", then to compare "this week with a week before the core update started rolling out". Google also warns against overreacting to a small drop, saying there is "no need to take drastic action" and specifically recommending "avoiding making changes to content that's already performing well". None of that comparison is possible without daily position history covering the weeks on either side, which is the practical argument for tracking continuously rather than starting after something goes wrong.
The questions people ask about SERP volatility.
What is SERP volatility?
SERP volatility is the degree to which Google's search results change position from one day to the next. It is measured by re-running the same set of keywords daily and scoring how much the top results moved. A high reading means the index is reshuffling broadly, usually during an algorithm update. A low reading means results are close to where they were yesterday.
What is SERP volatility today?
For an index-wide reading, check a free sensor such as Semrush Sensor, MozCast or Algoroo, which all publish a fresh score every day. Read two rather than one, because their keyword samples differ and they often disagree by a point. For whether your own rankings moved today, none of those will help, since your keywords are not in their samples.
What is a normal SERP volatility score?
On the common 0 to 10 scale, anything from 0 to 4 is ordinary daily churn and means nothing. Between 4 and 6 is elevated and often niche-specific. Above 7 is generally read as a broad event across the index, and above 8 usually coincides with an announced core or spam update in the middle of its rollout.
How do I check if a Google update affected my site?
Find the date the sensors spiked, then compare your own daily rankings for the week before that date against the week after the rollout finished. Google recommends waiting a full week after completion before analyzing. If your positions held through the window, the update did not touch you, regardless of how high the public score went.
Is SERP volatility always caused by an algorithm update?
No, and assuming so is a common error. Seasonal query patterns, news cycles pulling fresh results into the top 10, index refreshes, testing of new SERP features and competitors publishing or updating pages all move positions. Announced core updates account for a small share of the days when something visibly moves.
How long do Google core updates take to roll out?
Google says a core update rollout can take up to two weeks. In practice the recent ones have run close to that: the March 2026 core update took 12 days, from March 27 to April 8, and the May 2026 core update took 12 days, from May 21 to June 2. Rankings can move in both directions during the window before settling.
Should I make changes during high SERP volatility?
Avoid anything risky until the rollout finishes. Positions genuinely move in both directions mid-rollout, so a change made on day three gets judged against a moving baseline and you will never know whether it helped. Routine publishing is fine. Reverting pages, rewriting titles or rolling back a migration is not, until you can measure the result.
Do I need a rank tracker if I use a free volatility checker?
They answer different questions, so most teams end up with both. The free checker tells you the state of the wider index and costs nothing. A rank tracker tells you which of your keywords moved, by how much, and who took your place, which is the part the aggregate score structurally cannot provide.
More on the diagnosis side: why Google rankings drop works through the causes in order of likelihood, and how often Google updates rankings covers the cadence behind the baseline churn.
The pages that turn a volatility reading into a decision.
SERP tracking
The full Google top 10 stored on every daily check.
Rank drop alerts
Told the same day a position falls, not next month.
Daily rank tracker
Why the daily cadence is what makes dating an event possible.
Competitor rank tracking
Who entered the top 10 the day you left it.
Keyword position tracking
Daily position history for every term you track.
Google SERP tracker
How the daily checks are run and stored.
Ranking reports
Explaining a volatile month to a client who reads one page.
Rank tracker cost comparison
What daily tracking costs across 11 tools.
Best rank tracker
The full roundup of the field.
Start today
Know whether the volatility was yours.
Every keyword checked every 24 hours, the whole top 10 stored on every check, and an alert the day a position moves. From $39 a month for 250 keywords.