Check SERP Stability Before Committing
Difficulty scores describe how hard a result page is to enter, not how hard it is to stay in. Some result pages churn continuously because Google has not settled what the query means, and a page that reaches position four in month two can be gone by month four with nothing done wrong. Committing your best capacity to an unsettled SERP is how a programme loses a quarter and cannot explain why.
CATEGORY
Keyword research
FORMAT
keyword-serp-stability-check.md
WHEN TO REACH FOR THIS
Use when a target term is about to receive real production capacity and you need to know whether a ranking there would hold.
The skill file
keyword-serp-stability-check.md
---
name: keyword-serp-stability-check
description: Use when a target term is about to receive real production capacity and you need to know whether a ranking there would hold.
---
# Check SERP Stability Before Committing
Difficulty scores describe how hard a result page is to enter, not how hard it is to stay in. Some result pages churn continuously because Google has not settled what the query means, and a page that reaches position four in month two can be gone by month four with nothing done wrong. Committing your best capacity to an unsettled SERP is how a programme loses a quarter and cannot explain why.
## What you need first
- position history for the top ten of each target term across at least 12 weeks, from a rank tracker or a historical index
- the current top ten for each term, checked live and logged out in the target country
- the known algorithm update dates covering that window
## Method
1. Pull twelve weeks of history for the top ten of the term, not for your own site. Your absence from the results tells you nothing about how volatile the page is.
2. Count the distinct domains that have held a top-five slot across the period. Three or four is settled; eight or more means Google is still testing and any ranking you win there is a loan.
3. Check whether the page type mix changed inside the window. A SERP that moved from listicles to product pages has been reclassified, and content built for the old mix is obsolete before it is written.
4. Separate genuine churn from update aftershocks by comparing the volatile weeks against the update dates. Volatility confined to a rollout window is normal and is not a reason to avoid the term.
5. For settled SERPs, name the entry point: the weakest domain in the top ten and what it has that the others do not. If you cannot name it, you have no route in and the term is not as reachable as the stability suggests.
6. For unsettled SERPs, either skip the term or enter deliberately at low cost with one page rather than a cluster, and set a review date instead of treating an early ranking as proof.
7. Record each verdict with its date and evidence, so a term skipped this quarter is reassessed from the record rather than re-argued from scratch.
## What this produces
A per-term stability verdict with the count of distinct top-five domains, the entry point where one exists, and the date checked.
## Where this goes wrong
- Reading volatility from a tracker that samples weekly, which averages away the churn you are trying to detect.
- Mistaking seasonal rotation of results for instability, which is normal and predictable in retail and travel.
- Avoiding every volatile SERP on principle, since unresolved intent is also the cheapest place for a small site to enter if it accepts the risk.
---
From the QuQi skill library - https://www.quqi.io/skills/keyword-serp-stability-check
Free to download · no account, no email
What you need first
-
position history for the top ten of each target term across at least 12 weeks, from a rank tracker or a historical index
-
the current top ten for each term, checked live and logged out in the target country
-
the known algorithm update dates covering that window
Method
-
01
Pull twelve weeks of history for the top ten of the term, not for your own site. Your absence from the results tells you nothing about how volatile the page is.
-
02
Count the distinct domains that have held a top-five slot across the period. Three or four is settled; eight or more means Google is still testing and any ranking you win there is a loan.
-
03
Check whether the page type mix changed inside the window. A SERP that moved from listicles to product pages has been reclassified, and content built for the old mix is obsolete before it is written.
-
04
Separate genuine churn from update aftershocks by comparing the volatile weeks against the update dates. Volatility confined to a rollout window is normal and is not a reason to avoid the term.
-
05
For settled SERPs, name the entry point: the weakest domain in the top ten and what it has that the others do not. If you cannot name it, you have no route in and the term is not as reachable as the stability suggests.
-
06
For unsettled SERPs, either skip the term or enter deliberately at low cost with one page rather than a cluster, and set a review date instead of treating an early ranking as proof.
-
07
Record each verdict with its date and evidence, so a term skipped this quarter is reassessed from the record rather than re-argued from scratch.
What this produces
A per-term stability verdict with the count of distinct top-five domains, the entry point where one exists, and the date checked.
Where this goes wrong
-
Reading volatility from a tracker that samples weekly, which averages away the churn you are trying to detect.
-
Mistaking seasonal rotation of results for instability, which is normal and predictable in retail and travel.
-
Avoiding every volatile SERP on principle, since unresolved intent is also the cheapest place for a small site to enter if it accepts the risk.
Use this skill in your own AI
The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.
Claude Code
Save it as ~/.claude/skills/keyword-serp-stability-check/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude
Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT
There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else
Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.
Questions about this skill
When do I check stability rather than read a difficulty score?
Before committing real production capacity to a term. Difficulty describes how hard a result page is to enter, not how hard it is to stay in. Some pages churn continuously because Google has not settled what the query means, so a page that reaches position four in month two can be gone by month four with nothing done wrong and no explanation available.
What do I need in hand before starting?
At least twelve weeks of position history for the top ten of the term itself, the current results checked live and logged out in the target country, and the algorithm update dates covering that window. History for your own site says nothing about how volatile the page is. Without the update dates you read rollout aftershocks as permanent churn and skip terms that were never unstable.
What do I end up with, and which part gets used?
A settled, unsettled or reclassifying verdict per term, with the count of distinct domains that held a top-five slot, the entry point where one exists, and the date checked. The entry point is the part that gets used: the weakest domain in the top ten and what it has that the others do not. No named entry point means no route in.
What is the mistake that ruins this, and what does it cost?
Reading volatility from a tracker that samples weekly, which averages away the churn you are trying to detect and returns a settled verdict for a page that changes daily. The opposite error costs as much: refusing every volatile SERP on principle. Unresolved intent is also the cheapest entry for a small site, provided you enter with one page and a review date rather than a cluster.
More in Keyword research