中文导读
Ranking Drop Diagnosis 是一套面向一人公司的通用 playbook，帮助你用更少的人力完成更稳的增长、交付与决策。
概览
Ranking Drop Diagnosis is the skill of finding the real cause of a traffic decline before you rewrite the page, blame an algorithm update, or publish replacement content. For a one-person company, this matters because the wrong fix wastes the week. The right diagnosis tells you whether the problem is technical, intent mismatch, freshness decay, cannibalization, or a broader authority issue.
适用场景
Use this when a page loses clicks or impressions for two or more weeks, when a previously stable page slips from page one to page two, when the query mix changes sharply, or when traffic drops right after a site release or content update.
这个技能能做什么
This skill helps you separate page-level problems from sitewide problems. It gives you a fast diagnostic order so you can decide whether to fix redirects, restore content coverage, refresh examples, merge overlapping pages, or wait because the shift is seasonal rather than structural.
如何使用
Step 1: Compare the last 7, 28, and 90 days in Search Console. Look at clicks, impressions, CTR, and average position for the affected page.
Step 2: Check whether the drop is page-specific or sitewide. If several pages in the same cluster fell together, suspect technical or authority issues before rewriting the page.
Step 3: Review the query set. If the page now ranks for a different intent family, the problem may be mismatched content rather than pure rank loss.
Step 4: Check technical integrity. Confirm the canonical URL, redirect behavior, indexability, internal links, and any recent template or layout change.
Step 5: Compare the current page against the current SERP. Are competitors fresher, more specific, more comparison-oriented, or better structured for answer extraction?
Step 6: Choose one diagnosis and one next move. Do not mix five fixes at once. Pick the most likely cause, ship the correction, and measure the delta.
输出结果
The output should include:
- The likely cause of the drop
- Evidence supporting that diagnosis
- The specific fix to test first
- The metric window to watch after the fix
常见错误
Do not assume every ranking drop means a Google update penalty. Do not rewrite the whole page before checking redirects, canonicals, and query drift. Do not compare against your old page only; compare against what is ranking now. Do not change title, structure, CTA, and intent all at once if you want to learn what actually worked.
SKILL.md 原文件
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# ranking-drop-diagnosis
Ranking Drop Diagnosis
Overview
Ranking Drop Diagnosis is the skill of finding the real cause of a traffic decline before you rewrite the page, blame an algorithm update, or publish replacement content. For a one-person company, this matters because the wrong fix wastes the week. The right diagnosis tells you whether the problem is technical, intent mismatch, freshness decay, cannibalization, or a broader authority issue.
When to Use This Skill
Use this when a page loses clicks or impressions for two or more weeks, when a previously stable page slips from page one to page two, when the query mix changes sharply, or when traffic drops right after a site release or content update.
What This Skill Does
This skill helps you separate page-level problems from sitewide problems. It gives you a fast diagnostic order so you can decide whether to fix redirects, restore content coverage, refresh examples, merge overlapping pages, or wait because the shift is seasonal rather than structural.
How to Use
Step 1: Compare the last 7, 28, and 90 days in Search Console. Look at clicks, impressions, CTR, and average position for the affected page.
Step 2: Check whether the drop is page-specific or sitewide. If several pages in the same cluster fell together, suspect technical or authority issues before rewriting the page.
Step 3: Review the query set. If the page now ranks for a different intent family, the problem may be mismatched content rather than pure rank loss.
Step 4: Check technical integrity. Confirm the canonical URL, redirect behavior, indexability, internal links, and any recent template or layout change.
Step 5: Compare the current page against the current SERP. Are competitors fresher, more specific, more comparison-oriented, or better structured for answer extraction?
Step 6: Choose one diagnosis and one next move. Do not mix five fixes at once. Pick the most likely cause, ship the correction, and measure the delta.
Output
The output should include:
The likely cause of the drop
Evidence supporting that diagnosis
The specific fix to test first
The metric window to watch after the fix
Common Mistakes
Do not assume every ranking drop means a Google update penalty.
Do not rewrite the whole page before checking redirects, canonicals, and query drift.
Do not compare against your old page only; compare against what is ranking now.
Do not change title, structure, CTA, and intent all at once if you want to learn what actually worked.
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# ranking-drop-diagnosis
Ranking Drop Diagnosis
Overview
Ranking Drop Diagnosis is the skill of finding the real cause of a traffic decline before you rewrite the page, blame an algorithm update, or publish replacement content. For a one-person company, this matters because the wrong fix wastes the week. The right diagnosis tells you whether the problem is technical, intent mismatch, freshness decay, cannibalization, or a broader authority issue.
When to Use This Skill
Use this when a page loses clicks or impressions for two or more weeks, when a previously stable page slips from page one to page two, when the query mix changes sharply, or when traffic drops right after a site release or content update.
What This Skill Does
This skill helps you separate page-level problems from sitewide problems. It gives you a fast diagnostic order so you can decide whether to fix redirects, restore content coverage, refresh examples, merge overlapping pages, or wait because the shift is seasonal rather than structural.
How to Use
Step 1: Compare the last 7, 28, and 90 days in Search Console. Look at clicks, impressions, CTR, and average position for the affected page.
Step 2: Check whether the drop is page-specific or sitewide. If several pages in the same cluster fell together, suspect technical or authority issues before rewriting the page.
Step 3: Review the query set. If the page now ranks for a different intent family, the problem may be mismatched content rather than pure rank loss.
Step 4: Check technical integrity. Confirm the canonical URL, redirect behavior, indexability, internal links, and any recent template or layout change.
Step 5: Compare the current page against the current SERP. Are competitors fresher, more specific, more comparison-oriented, or better structured for answer extraction?
Step 6: Choose one diagnosis and one next move. Do not mix five fixes at once. Pick the most likely cause, ship the correction, and measure the delta.
Output
The output should include:
The likely cause of the drop
Evidence supporting that diagnosis
The specific fix to test first
The metric window to watch after the fix
Common Mistakes
Do not assume every ranking drop means a Google update penalty.
Do not rewrite the whole page before checking redirects, canonicals, and query drift.
Do not compare against your old page only; compare against what is ranking now.
Do not change title, structure, CTA, and intent all at once if you want to learn what actually worked.
评论与讨论
添加评论