recover-content
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRecover Content
内容恢复
Diagnose and reverse traffic loss on existing pages using the decay triage
framework: refresh, consolidate, redirect, or retire.
使用衰减分类处理框架诊断并挽回现有页面的流量流失:更新、合并、重定向或下线。
Before You Start
开始之前
Gather this context (ask if not provided):
- Which pages are losing traffic? Specific URLs or a general "the whole blog is declining."
- How much traffic was lost? Percentage drop or absolute numbers.
- Over what timeframe? Gradual decline over months vs sudden drop.
- Any recent changes? Site redesign, CMS migration, content edits, algorithm update timing.
If the user doesn't know which pages are declining, suggest checking Google Search
Console → Performance → Pages, sorted by click change over the last 6 months.
收集以下背景信息(如果用户未提供可主动询问):
- 哪些页面正在流失流量? 具体的URL,或者笼统的「整个博客流量都在下滑」。
- 流失了多少流量? 下降百分比或者绝对数值。
- 发生在什么时间范围内? 是数月内逐步下滑还是突然下降。
- 近期有没有做过改动? 网站重构、CMS迁移、内容编辑、算法更新的时间点。
如果用户不知道哪些页面流量在下滑,建议查看Google Search Console → 效果 → 页面,按过去6个月的点击量变化排序。
Identifying Decay
识别内容衰减
Content decay happens when a page gradually loses search traffic over time.
Common signals:
- Clicks declining month-over-month for 3+ months
- Position slipping from page 1 to page 2+
- Impressions stable but CTR dropping (competitors have better titles/snippets)
- Impressions declining (Google no longer considers the page relevant)
内容衰减指页面的搜索流量随时间逐步流失,常见信号包括:
- 连续3个月以上点击量环比下滑
- 排名从第1页下滑到第2页及以后
- 曝光量稳定但CTR下降(竞争对手的标题/摘要更有吸引力)
- 曝光量下滑(Google不再认为该页面具有相关性)
Composite Decay Score
综合衰减评分
Score each page across 5 weighted signals to prioritize action:
| Signal | Weight | How to Score (0-100) |
|---|---|---|
| Traffic decline | 30% | 0 = no decline, 50 = 20-40% drop, 100 = >60% drop |
| Position drops | 25% | 0 = stable, 50 = lost 3-5 positions, 100 = dropped off page 1 |
| CTR decline | 15% | 0 = stable, 50 = 20% decline, 100 = >40% decline |
| Content freshness | 15% | 0 = updated this quarter, 50 = 6-12 months stale, 100 = >2 years stale |
| Competitive displacement | 15% | 0 = no new competitors, 50 = new entrants on page 1, 100 = displaced from top 3 |
Composite Decay Score = (Traffic x 0.30) + (Position x 0.25) + (CTR x 0.15)
+ (Freshness x 0.15) + (Displacement x 0.15)| Score | Stage | Response |
|---|---|---|
| 0-20 | Healthy | Continue monitoring |
| 21-40 | Early decay | Add to refresh queue (next month) |
| 41-60 | Active decay | Schedule refresh this week |
| 61-80 | Significant decay | Immediate refresh or rewrite decision |
| 81-100 | Terminal decay | Rewrite, redirect, or retire |
从5个加权信号维度为每个页面评分,以确定处理优先级:
| 信号 | 权重 | 评分规则(0-100) |
|---|---|---|
| 流量下滑 | 30% | 0 = 无下滑,50 = 下滑20-40%,100 = 下滑超过60% |
| 排名下降 | 25% | 0 = 稳定,50 = 下降3-5个排名位,100 = 掉出第1页 |
| CTR下滑 | 15% | 0 = 稳定,50 = 下滑20%,100 = 下滑超过40% |
| 内容新鲜度 | 15% | 0 = 本季度刚更新,50 = 6-12个月未更新,100 = 超过2年未更新 |
| 竞品取代 | 15% | 0 = 无新竞争对手,50 = 第1页出现新竞品,100 = 掉出前3名 |
Composite Decay Score = (Traffic x 0.30) + (Position x 0.25) + (CTR x 0.15)
+ (Freshness x 0.15) + (Displacement x 0.15)| 评分 | 阶段 | 处理方式 |
|---|---|---|
| 0-20 | 健康 | 持续监控 |
| 21-40 | 早期衰减 | 加入更新队列(下月处理) |
| 41-60 | 活跃衰减 | 本周安排更新 |
| 61-80 | 严重衰减 | 立即决定更新或重写 |
| 81-100 | 终末期衰减 | 重写、重定向或下线 |
Alert Priority Matrix
告警优先级矩阵
When multiple signals fire together, escalate:
| Signal Combination | Priority | Response Time |
|---|---|---|
| Traffic decline + Position drop | P1 Critical | Refresh within 48 hours |
| Traffic decline + CTR decline | P1 Critical | Rewrite title/meta immediately |
| Position drop + Competitor displacement | P2 High | Refresh within 1 week |
| CTR decline only | P3 Medium | Rewrite title and meta this week |
| Freshness indicators only | P3 Medium | Schedule refresh within 2 weeks |
当多个信号同时出现时,提升处理优先级:
| 信号组合 | 优先级 | 响应时间 |
|---|---|---|
| 流量下滑 + 排名下降 | P1 紧急 | 48小时内更新 |
| 流量下滑 + CTR下滑 | P1 紧急 | 立即重写标题/元描述 |
| 排名下降 + 竞品取代 | P2 高 | 1周内更新 |
| 仅CTR下滑 | P3 中 | 本周内重写标题和元描述 |
| 仅新鲜度不足 | P3 中 | 2周内安排更新 |
The Decay Triage Framework
衰减分类处理框架
For each decaying page, apply this decision tree:
对每个衰减页面,按照以下决策树处理:
Decision 1: Is the topic still relevant?
决策1:主题是否仍然有价值?
- Yes → proceed to Decision 2
- No (product discontinued, event passed, technology obsolete) → Retire. 301 redirect to the closest relevant page or parent category.
- 是 → 进入决策2
- 否(产品已下线、活动已结束、技术已过时)→ 下线。301重定向到最相关的页面或父分类页。
Decision 2: Is there another page on the site targeting the same topic?
决策2:站点内是否有其他页面对同一主题做了布局?
- Yes → Consolidate. Merge the best content from both pages into one. 301 redirect the weaker page.
- No → proceed to Decision 3
- 是 → 合并。将两个页面的优质内容合并到一个页面中,将质量较差的页面301重定向到合并后的页面。
- 否 → 进入决策3
Decision 3: Has the search intent shifted?
决策3:搜索意图是否发生了变化?
Check what currently ranks for the target keyword. Has the SERP changed from:
-
Listicles → long-form guides?
-
Blog posts → product pages?
-
Text → video?
-
General → specific?
-
Yes, intent shifted → Rewrite. Rebuild the page to match current intent. Keep the URL.
-
No → proceed to Decision 4
查看目标关键词当前的排名结果,SERP是否发生了以下变化:
-
榜单类内容 → 长文指南?
-
博客文章 → 产品页?
-
文字内容 → 视频内容?
-
泛化内容 → 垂直内容?
-
是,意图已变化 → 重写。重构页面内容以匹配当前搜索意图,保留原有URL。
-
否 → 进入决策4
Decision 4: Is the content simply outdated?
决策4:是否仅仅是内容过时?
Check for: stale statistics, outdated screenshots, deprecated tools/methods,
old dates in the title, broken external links.
- Yes, outdated → Refresh. Update facts, screenshots, examples, and dates. Add new sections covering recent developments.
- No → Investigate deeper. The issue may be technical (lost backlinks, slower page speed, mobile issues) or competitive (stronger pages now outrank).
检查以下内容:过时的统计数据、老旧的截图、已弃用的工具/方法、标题里的旧日期、失效的外链。
- 是,内容过时 → 更新。更新事实信息、截图、案例和日期,新增介绍近期发展的内容模块。
- 否 → 深入排查。问题可能来自技术层面(丢失反向链接、页面速度变慢、移动端适配问题)或者竞争层面(质量更高的竞品页面排名超过了本页面)。
Refresh Playbooks by Content Type
不同内容类型的更新指南
Different content types require different refresh approaches. Use the matching playbook:
不同类型的内容需要不同的更新方法,选择适配的指南:
Blog Post / Article (3-4 hours)
博客文章/普通文章(3-4小时)
- Update title with current year or fresh hook (10 min)
- Rewrite introduction with a new angle (20 min)
- Update all statistics with current sources (30-60 min)
- Add 1-2 new sections covering gaps competitors address (60-90 min)
- Update screenshots and images (30 min)
- Add or refresh FAQ section with current PAA questions (20 min)
- Refresh internal links to recent related content (15 min)
- Update meta description (5 min)
- Add or update schema markup — dateModified at minimum (10 min)
- Republish with updated date and re-submit to Search Console (5 min)
- 更新标题,加入当前年份或新的吸引点(10分钟)
- 用新的角度重写引言(20分钟)
- 用最新来源更新所有统计数据(30-60分钟)
- 新增1-2个模块覆盖竞争对手已经补充的内容缺口(60-90分钟)
- 更新截图和图片(30分钟)
- 新增或更新FAQ模块,加入当前的PAA问题(20分钟)
- 更新内部链接,指向近期发布的相关内容(15分钟)
- 更新元描述(5分钟)
- 新增或更新schema标记——至少更新dateModified字段(10分钟)
- 以更新后的日期重新发布,并重新提交到Search Console(5分钟)
Statistics / Data Roundup (4-5 hours)
统计/数据汇总类内容(4-5小时)
- Verify every statistic — remove any without a current source
- Replace outdated stats with current data (within 2 years)
- Add new statistics from recent studies
- Update all source links — replace broken citations
- Update year references in title and body
- Add a data visualization if none exists
- Update meta description and title
- 核验每个统计数据——移除所有没有最新来源的数据
- 用近两年的最新数据替换过时的统计数据
- 加入近期研究中的新统计数据
- 更新所有来源链接——替换失效的引用链接
- 更新标题和正文中的年份引用
- 如果没有数据可视化内容则新增
- 更新元描述和标题
How-To Guide (3-3.5 hours)
操作指南类内容(3-3.5小时)
- Verify all steps still work as written
- Update screenshots for any changed interfaces
- Add new alternative methods if any have emerged
- Update tool recommendations (remove deprecated, add current)
- Add a troubleshooting section for common failure points
- Update FAQ with recent questions
- Test all external links
- 核验所有步骤仍然可以按描述正常执行
- 对所有发生变化的界面更新截图
- 如果有新的替代方法则新增
- 更新工具推荐(移除已弃用的工具,加入当前常用工具)
- 新增排查模块,介绍常见问题的解决方法
- 用近期的问题更新FAQ
- 测试所有外链是否有效
Refresh Checklist (General)
通用更新检查清单
For any content type, always complete:
- Update all statistics and data points to current year
- Replace outdated examples and screenshots
- Add new sections covering developments since last update
- Remove or update broken external links
- Improve the title and meta description (check competitor titles for CTR ideas)
- Add internal links from recent, related content
- Expand thin sections that competitors cover better
- Add original insights, data, or expert quotes (E-E-A-T signals)
- Update the published/modified date
- Re-submit to Google Search Console for re-indexing
对任何类型的内容,都需要完成以下检查:
- 将所有统计数据和数据点更新到当前年份
- 替换过时的案例和截图
- 新增模块介绍上次更新之后的行业发展
- 移除或更新失效的外链
- 优化标题和元描述(参考竞争对手的标题获取CTR优化思路)
- 新增来自近期相关内容的内部链接
- 扩充竞争对手覆盖更完善的薄弱内容模块
- 新增原创观点、数据或专家引用(E-E-A-T信号)
- 更新发布/修改日期
- 重新提交到Google Search Console请求重新索引
Consolidation Checklist
内容合并检查清单
When merging two pages:
- Identify the stronger URL (more backlinks, better position, older)
- Move the best content from the weaker page into the stronger one
- Set up a 301 redirect from the weaker URL to the stronger one
- Update all internal links that pointed to the weaker URL
- Check for backlinks to the weaker URL — the redirect will pass authority
合并两个页面时:
- 确定权重更高的URL(反向链接更多、排名更好、发布时间更早)
- 将权重较低页面的优质内容迁移到权重更高的页面中
- 将权重较低的URL 301重定向到权重更高的URL
- 更新所有指向权重较低URL的内部链接
- 检查指向权重较低URL的反向链接——重定向会传递权重
Prioritization
优先级排序
Score each page for refresh priority:
| Factor | Weight |
|---|---|
| Current traffic value | 25% |
| Decay severity (composite score) | 20% |
| Competitive opportunity | 20% |
| Refresh difficulty (inverse — easier = higher) | 15% |
| Strategic importance (conversions, brand) | 10% |
| Backlink equity at risk | 10% |
Then rank pages:
| Page | Decay Score | Traffic Lost | Priority Score | Action | Effort |
|---|---|---|---|---|---|
| ... | 72 (significant) | 1,200/mo | 85 | Refresh | 3-4 hrs |
| ... | 45 (active) | 300/mo | 60 | Consolidate | 2 hrs |
Focus on pages that (a) had the most traffic, (b) drive conversions, and (c) are
easiest to fix. A quick refresh on a high-traffic page beats a full rewrite on a
low-traffic one.
为每个页面的更新优先级打分:
| 因素 | 权重 |
|---|---|
| 当前流量价值 | 25% |
| 衰减严重程度(综合评分) | 20% |
| 竞争机会 | 20% |
| 更新难度(反向计分——难度越低分数越高) | 15% |
| 战略重要性(转化、品牌) | 10% |
| 面临流失风险的反向链接权重 | 10% |
然后对页面排序:
| 页面 | 衰减评分 | 流失流量 | 优先级评分 | 处理方式 | 所需工作量 |
|---|---|---|---|---|---|
| ... | 72(严重) | 1,200/月 | 85 | 更新 | 3-4 hrs |
| ... | 45(活跃) | 300/月 | 60 | 合并 | 2 hrs |
优先处理以下页面:(a) 原有流量最高的 (b) 能带来转化的 (c) 修复难度最低的。对高流量页面做快速更新的收益远高于对低流量页面做完全重写。
Content Retirement Options
内容下线选项
When a page can't be saved, choose the right exit:
| Option | When to Use |
|---|---|
| 301 redirect | Content has backlinks or residual traffic — send equity to closest relevant page |
| Consolidate | Multiple weak pages on same topic — merge best content into one URL |
| Noindex | Internal utility page that shouldn't rank but serves users |
| Delete (410) | No value, no links, no traffic — clean removal |
当页面无法修复时,选择合适的下线方式:
| 选项 | 使用场景 |
|---|---|
| 301重定向 | 内容有反向链接或残余流量——将权重传递给最相关的页面 |
| 合并 | 同一主题下有多个低质量页面——将优质内容合并到同一个URL |
| Noindex | 不应该参与排名但对用户有用的内部工具页面 |
| 删除(410) | 无价值、无链接、无流量的页面——彻底清理 |
Output Format
输出格式
Content Recovery Plan: [domain]
内容恢复计划:[domain]
Decay Summary
- Pages analyzed: [count]
- Pages needing action: [count]
- Estimated traffic recoverable: [sum of lost traffic]
Triage Results
| Page | Traffic Lost | Diagnosis | Action | Effort |
|---|---|---|---|---|
| ... | ... | intent shift / outdated / cannibalization / irrelevant | refresh / consolidate / redirect / retire | low / medium / high |
Priority Actions
For each high-priority page:
- What specifically needs to change
- Which sections to update, expand, or remove
- Estimated impact if recovered
Pro Tip: Use the free Keyword Density Analyzer to check whether a declining page is still optimized for its target keyword. SEOJuice MCP users can runto see active content decay alerts with severity ratings — the/seojuice:content-strategytool pulls pages losing traffic automatically.list_content_decay
衰减总结
- 分析页面数:[count]
- 需要处理的页面数:[count]
- 预估可挽回流量:[sum of lost traffic]
分类处理结果
| 页面 | 流失流量 | 诊断结果 | 处理方式 | 所需工作量 |
|---|---|---|---|---|
| ... | ... | 意图变化 / 内容过时 / 内容冲突 / 无价值 | 更新 / 合并 / 重定向 / 下线 | 低 / 中 / 高 |
优先级操作
对每个高优先级页面:
- 需要调整的具体内容
- 需要更新、扩充或移除的模块
- 修复后的预估收益
专业提示: 使用免费的Keyword Density Analyzer检查流量下滑的页面是否仍然针对目标关键词做了优化。SEOJuice MCP用户可以运行查看带有严重等级的内容衰减告警——/seojuice:content-strategy工具可以自动拉取流量流失的页面。list_content_decay