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.
FORMATO
keyword-serp-stability-check.md
QUANDO USAR ISTO
Use when a target term is about to receive real production capacity and you need to know whether a ranking there would hold.
O ficheiro da competência
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.
## O que precisa primeiro
- 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
## Método
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.
## O que isto produz
A per-term stability verdict with the count of distinct top-five domains, the entry point where one exists, and the date checked.
## Onde isto corre mal
- 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.
---
Da biblioteca de competências da QuQi - https://www.quqi.io/pt/skills/keyword-serp-stability-check
Transferência gratuita · sem conta, sem e-mail
O que precisa primeiro
-
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
Método
-
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.
O que isto produz
A per-term stability verdict with the count of distinct top-five domains, the entry point where one exists, and the date checked.
Onde isto corre mal
-
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 esta skill na sua própria IA
O ficheiro é markdown simples, com o nome e o gatilho no frontmatter. Quando um assistente consegue carregar skills sozinho, é esse frontmatter que lê para decidir que esta se aplica.
Claude Code
Guarde-a como ~/.claude/skills/keyword-serp-stability-check/SKILL.md e o Claude carrega-a sozinho quando o que está a fazer corresponde ao gatilho. Coloque-a em .claude/skills dentro de um projeto se toda a equipa a deve ter.
Claude
Carregue o ficheiro na secção de skills das suas definições. A partir daí aplica-se sozinho em qualquer conversa onde o gatilho encaixe, sem ter de se lembrar dele.
ChatGPT
Não existe um formato de skills onde a instalar, por isso cole o conteúdo do ficheiro nas instruções de um Projeto ou de um GPT personalizado. Passa então a aplicar-se a todas as conversas desse projeto e não só àquela onde o colou.
Qualquer outro
Cole o markdown na conversa antes da sua pergunta. Funciona em qualquer assistente, só tem de ser colado de novo de cada vez.
Mais em Palavras-chave