Back to Details

blog-decay

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Blog Decay

博客内容衰减

Use 
/blog decay
to find pages whose Google Search Console performance has declined quarter-over-quarter. The command compares a current-period export against a previous-period export, flags pages with a 20% or larger decline by default, and recommends the next content action.
使用
/blog decay
命令可查找Google Search Console中表现季度环比下滑的页面。该命令会对比当期与往期的导出数据，默认标记流量下滑20%及以上的页面，并给出后续内容优化建议。

Default Offline Workflow

默认离线工作流程

Run the local analyzer against two GSC page exports:
bash
python3 scripts/content_decay.py current.json previous.json
Useful options:
bash
python3 scripts/content_decay.py current.json previous.json --threshold 0.30
python3 scripts/content_decay.py current.json previous.json --metric impressions
python3 scripts/content_decay.py current.json previous.json --format markdown --output decay-report.md
The script accepts JSON lists of page rows with 
page
or 
url
, 
clicks
, and 
impressions
. It also accepts the object shape returned by 
blog-google
when the rows are under a top-level 
rows
key.
针对两份GSC页面导出数据运行本地分析工具：
bash
python3 scripts/content_decay.py current.json previous.json
实用选项：
bash
python3 scripts/content_decay.py current.json previous.json --threshold 0.30
python3 scripts/content_decay.py current.json previous.json --metric impressions
python3 scripts/content_decay.py current.json previous.json --format markdown --output decay-report.md
该脚本接受包含
page
或
url
、
clicks
和
impressions
字段的页面行JSON列表。当数据行位于顶级
rows
键下时，也支持
blog-google
返回的对象格式。

Optional Live GSC Export

可选的实时GSC导出流程

For live data, use 
/blog google gsc
or the underlying 
blog-google
command to create each period export, then run the offline analyzer:
bash
python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-current.json
python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-previous.json
python3 scripts/content_decay.py gsc-current.json gsc-previous.json --format markdown
Use adjacent periods of similar length for short-term checks. For seasonality, also run a year-over-year comparison using the same date length, filters, search type, device, country, and property. When possible, inspect up to 16 months of GSC history before diagnosing a traffic drop.
如需获取实时数据，可使用
/blog google gsc
命令或底层的
blog-google
命令生成各周期的导出数据，再运行离线分析工具：
bash
python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-current.json
python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-previous.json
python3 scripts/content_decay.py gsc-current.json gsc-previous.json --format markdown
短期检测可选择长度相近的相邻周期。针对季节性情况，需使用相同的日期长度、筛选条件、搜索类型、设备、国家/地区及属性进行同比对比。在诊断流量下降原因时，尽可能查看最多16个月的GSC历史数据。

Decay Model

衰减模型

The default metric is 
clicks
. Also review impressions, CTR, average position, query and page pairs, device, country, and search appearance deltas before choosing an action.
Severity:
DeclineSeverity
20% to 39.9%warning
40% to 59.9%high
60% or morecritical
Dropped pages are previous-period pages missing from the current export only after confirming identical filters, sufficient row limits, matching dimensions, and URL inspection. Otherwise mark them as 
needs_validation
, not 
dropped_out
.
默认指标为
clicks
（点击量）。在选择操作前，还需查看曝光量、点击率（CTR）、平均排名、查询词与页面的匹配情况、设备、国家/地区及搜索展示形式的变化。
严重程度：
下滑幅度严重程度
20% - 39.9%警告
40% - 59.9%高
60%及以上严重
只有在确认筛选条件一致、行限制足够、维度匹配且完成URL检查后，才能将当期导出数据中缺失的往期页面标记为“已消失页面”。否则应标记为
needs_validation
（需验证），而非
dropped_out
（已消失）。

Recommended Actions

推荐操作

Use the action as the first triage path only after checking indexation, canonical status, query loss, internal links, backlinks, seasonality, and business value:
ActionUse when
refresh/update contentThe page still has demand and likely needs freshness, title, internal link, or section updates.
investigate query shiftClicks fell while impressions held up, suggesting CTR, rank, SERP, or query mix changes.
consolidate/redirectThe page dropped out or the loss is severe enough that merging into a stronger URL may recover value faster.
pruneThe page had very low prior demand and may not justify rewrite effort.
只有在检查完索引状态、规范网址状态、查询词流失情况、内部链接、反向链接、季节性因素及商业价值后，才能将以下操作作为首要分类处理路径：
操作使用场景
刷新/更新内容页面仍有需求，可能需要更新内容时效性、标题、内部链接或部分章节。
调查查询方向变化点击量下降但曝光量保持稳定，表明点击率、排名、搜索结果页（SERP）或查询词组合发生变化。
整合/重定向页面已消失或流量流失严重，合并至更优质的URL可能更快恢复价值。
删除页面原本需求极低，不值得投入重写精力。

Cross-references

交叉引用

Use 
blog-google
to collect Search Console exports when live credentials are available. Use 
blog-rewrite
after decay detection when the recommended action is refresh/update content and the page is worth improving.
当有实时凭证时，可使用
blog-google
收集Search Console导出数据。当衰减检测后推荐操作是刷新/更新内容且页面值得优化时，可使用
blog-rewrite
命令。