中文导读
Content Refresh Calendar 是一套面向一人公司的增长 playbook，帮助你用更少的人力完成更稳的增长、交付与决策。
概览
Content Refresh Calendar is the skill of deciding what to update, when to update it, and why. For a one-person company, refresh discipline compounds faster than publishing volume. A structured refresh rhythm keeps good pages current, protects rankings, and increases answer-engine citation potential.
适用场景
Use this when you already have a real content library, when old pages are drifting, or when too many refresh decisions are happening ad hoc.
这个技能能做什么
This skill helps you create a practical refresh rhythm tied to page value, traffic signals, and content decay patterns.
如何使用
Step 1: Split pages into tiers. Tier 1 pages get monthly or biweekly review. Tier 2 pages get quarterly review. Tier 3 pages get light maintenance or wait for demand.
Step 2: Define refresh triggers. Use drops in clicks, rising impressions with weak CTR, stale dates, outdated examples, missing FAQs, and new competitor angles.
Step 3: Choose the refresh depth. Some pages need a title and intro fix. Some need a new FAQ block. Some need full structural rewrite.
Step 4: Batch by theme. Refresh related pages together so internal linking, examples, and positioning stay consistent.
Step 5: Record what changed. Keep a short change log so you can tie traffic movement to actual page edits.
Step 6: Recheck after the refresh window. If a page did not improve, decide whether to iterate again, merge it, or stop investing.
输出结果
The output should include:
- A calendar by page tier
- The trigger for each refresh
- The planned scope of work
- A follow-up check date
常见错误
Do not refresh everything equally. Do not treat an updated date as a real refresh. Do not forget to strengthen links and FAQs during the refresh. Do not keep touching pages that never mattered in the first place.
Evidence and Source Links
- Google explicitly recommends substantial, people-first updates and warns against making superficial date-only changes:
https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Use Search Analytics query data (clicks, impressions, CTR, average position) to decide whether a refresh actually improved visibility:
https://developers.google.com/webmaster-tools/v1/searchanalytics/query
- If your refresh adds or changes FAQ sections, follow supported FAQPage structured data requirements to keep markup valid:
https://developers.google.com/search/docs/appearance/structured-data/faqpage
- After a major refresh, request recrawl so indexing can pick up meaningful updates faster:
https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl
SKILL.md 原文件
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# content-refresh-calendar
Content Refresh Calendar
Overview
Content Refresh Calendar is the skill of deciding what to update, when to update it, and why. For a one-person company, refresh discipline compounds faster than publishing volume. A structured refresh rhythm keeps good pages current, protects rankings, and increases answer-engine citation potential.
When to Use This Skill
Use this when you already have a real content library, when old pages are drifting, or when too many refresh decisions are happening ad hoc.
What This Skill Does
This skill helps you create a practical refresh rhythm tied to page value, traffic signals, and content decay patterns.
How to Use
Step 1: Split pages into tiers. Tier 1 pages get monthly or biweekly review. Tier 2 pages get quarterly review. Tier 3 pages get light maintenance or wait for demand.
Step 2: Define refresh triggers. Use drops in clicks, rising impressions with weak CTR, stale dates, outdated examples, missing FAQs, and new competitor angles.
Step 3: Choose the refresh depth. Some pages need a title and intro fix. Some need a new FAQ block. Some need full structural rewrite.
Step 4: Batch by theme. Refresh related pages together so internal linking, examples, and positioning stay consistent.
Step 5: Record what changed. Keep a short change log so you can tie traffic movement to actual page edits.
Step 6: Recheck after the refresh window. If a page did not improve, decide whether to iterate again, merge it, or stop investing.
Output
The output should include:
A calendar by page tier
The trigger for each refresh
The planned scope of work
A follow-up check date
Common Mistakes
Do not refresh everything equally.
Do not treat an updated date as a real refresh.
Do not forget to strengthen links and FAQs during the refresh.
Do not keep touching pages that never mattered in the first place.
Evidence and Source Links
- Google explicitly recommends substantial, people-first updates and warns against making superficial date-only changes:
https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Use Search Analytics query data (clicks, impressions, CTR, average position) to decide whether a refresh actually improved visibility:
https://developers.google.com/webmaster-tools/v1/searchanalytics/query
- If your refresh adds or changes FAQ sections, follow supported FAQPage structured data requirements to keep markup valid:
https://developers.google.com/search/docs/appearance/structured-data/faqpage
- After a major refresh, request recrawl so indexing can pick up meaningful updates faster:
https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# content-refresh-calendar
Content Refresh Calendar
Overview
Content Refresh Calendar is the skill of deciding what to update, when to update it, and why. For a one-person company, refresh discipline compounds faster than publishing volume. A structured refresh rhythm keeps good pages current, protects rankings, and increases answer-engine citation potential.
When to Use This Skill
Use this when you already have a real content library, when old pages are drifting, or when too many refresh decisions are happening ad hoc.
What This Skill Does
This skill helps you create a practical refresh rhythm tied to page value, traffic signals, and content decay patterns.
How to Use
Step 1: Split pages into tiers. Tier 1 pages get monthly or biweekly review. Tier 2 pages get quarterly review. Tier 3 pages get light maintenance or wait for demand.
Step 2: Define refresh triggers. Use drops in clicks, rising impressions with weak CTR, stale dates, outdated examples, missing FAQs, and new competitor angles.
Step 3: Choose the refresh depth. Some pages need a title and intro fix. Some need a new FAQ block. Some need full structural rewrite.
Step 4: Batch by theme. Refresh related pages together so internal linking, examples, and positioning stay consistent.
Step 5: Record what changed. Keep a short change log so you can tie traffic movement to actual page edits.
Step 6: Recheck after the refresh window. If a page did not improve, decide whether to iterate again, merge it, or stop investing.
Output
The output should include:
A calendar by page tier
The trigger for each refresh
The planned scope of work
A follow-up check date
Common Mistakes
Do not refresh everything equally.
Do not treat an updated date as a real refresh.
Do not forget to strengthen links and FAQs during the refresh.
Do not keep touching pages that never mattered in the first place.
Evidence and Source Links
- Google explicitly recommends substantial, people-first updates and warns against making superficial date-only changes:
https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Use Search Analytics query data (clicks, impressions, CTR, average position) to decide whether a refresh actually improved visibility:
https://developers.google.com/webmaster-tools/v1/searchanalytics/query
- If your refresh adds or changes FAQ sections, follow supported FAQPage structured data requirements to keep markup valid:
https://developers.google.com/search/docs/appearance/structured-data/faqpage
- After a major refresh, request recrawl so indexing can pick up meaningful updates faster:
https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl
评论与讨论
添加评论