A single repeated capture of a search results page that RankGear collects, alongside other captures of the same query, to measure how much the SERP moves on its own — with no change to your target page.
| Term | SERP Volatility Sample |
|---|---|
| Category | Search and SERP Data |
| Also known as | Repeat Search Sample |
| Where it appears | Volatility |
What it means in RankGear
A SERP Volatility Sample appears in RankGear’s Volatility tooling. Each sample is one capture of the search results page for a single keyword at a single moment. On its own that capture tells you almost nothing; its value comes from being one of a series. By retrieving the same query repeatedly under identical settings, RankGear can watch which URLs climb, drop, or reorder between captures even when your own page has not changed at all. The sample is the atomic unit of that measurement — the raw retrieval that feeds the volatility reading.
How to interpret it
A sample is only comparable to another sample when both were pulled the same way. Before you read anything into movement between runs, confirm that provider, country, language, device, location, requested depth, and completeness all match across the set. A rank change that actually comes from switching device or city is not volatility — it is a settings mismatch. Because results also drift with time, personalization, and provider coverage, treat each sample as a comparative indicator of how unstable the query environment is, not a Google score. A churning SERP tells you something about the query, not about whether any single page deserves to rank.
| Setting held constant | Why it must match across samples |
|---|---|
| Provider | Different providers crawl and rank differently, so mixing them fakes movement. |
| Country and language | Localization reorders results; a locale change reads as false volatility. |
| Device | Mobile and desktop SERPs differ in layout and order. |
| Location | Geo-sensitive queries return different local packs and rankings. |
| Requested depth and completeness | A partial or shorter run isn’t comparable to a full Top 20 capture. |
Example
Suppose you track “commercial refrigeration repair” and want to know whether a stubborn ranking is your page’s problem or just a restless results page. RankGear pulls a Top 20 localized run — Google, United States, English, mobile, one set city — as a single SERP Volatility Sample, then repeats that identical run several times across the day. If positions three through twelve reshuffle between samples while your URL holds steady, the volatility lives in the SERP itself. If the order is stable across every sample, a lost position is more likely tied to your page. Each localized Top 20 capture may take several provider calls, but every call in the sample keeps the same localization settings.
Important considerations
- A single sample is meaningless in isolation — volatility is measured across a series of samples, never from one retrieval.
- Every sample in a comparison must share the same provider, country, language, device, location, requested depth, and completeness; otherwise you are measuring your own settings, not the SERP.
- Search results change over time and by location, device, provider, and personalization context, so expect some baseline drift even on stable queries.
- Volatility readings are comparative indicators of how much a results page is moving; they are not Google ranking scores and do not by themselves explain why a page ranks.
- A deep or heavily localized run can span multiple provider calls; exclude incomplete or partial captures before comparing.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.