blog-calendar

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Blog Calendar -- Editorial Planning

博客日历 -- 编辑规划

Generates editorial calendars with topic clusters, publishing cadence, freshness update schedules, content decay detection, template recommendations, distribution planning, and seasonal hooks. Optimized for building topical authority (Google) and maintaining citation freshness (AI platforms).
生成包含主题集群、发布节奏、新鲜度更新日程、内容衰减检测、模板推荐、分发规划及季节性切入点的编辑日历。针对构建主题权威性(适配Google)和维持引用新鲜度(适配AI平台)进行优化。

Cross-reference

交叉参考

This skill operates at the FLOW Find stage. Before selecting topics, run
/blog flow find
for keyword discovery, content prioritization, and audience avatar prompts that should inform cluster selection and topic sequencing.
此技能处于FLOW Find阶段。在选择主题前,运行
/blog flow find
进行关键词挖掘、内容优先级排序及受众画像提示,这些信息将为集群选择和主题排序提供依据。

Workflow

工作流程

Step 1: Understand the Blog

步骤1:了解博客

Gather context:
  1. Niche/industry -- What is the blog about?
  2. Existing content -- Scan for existing blog posts (Glob for *.md, *.mdx, *.html)
  3. Publishing cadence -- How often can they publish? (default: 2x/week)
  4. Timeframe -- Monthly or quarterly calendar?
  5. Business goals -- What should the blog drive? (traffic, leads, authority)
收集背景信息:
  1. 细分领域/行业 -- 博客的主题是什么?
  2. 现有内容 -- 扫描现有博客文章(支持通配符匹配*.md、.mdx、.html文件)
  3. 发布节奏 -- 发布频率是多少?(默认:每周2次)
  4. 时间范围 -- 需要月度还是季度日历?
  5. 业务目标 -- 博客要达成什么目标?(流量、潜客、权威性)

Step 2: Topic Cluster Design

步骤2:主题集群设计

Design 3-5 topic clusters (pillar + supporting content):
Cluster: [Pillar Topic]
├── Pillar Page: [Comprehensive guide - 3,000+ words]
├── Supporting: [Subtopic 1 - 2,000 words]
├── Supporting: [Subtopic 2 - 2,000 words]
├── Supporting: [Subtopic 3 - 1,500 words]
├── Comparison: [X vs Y - 1,500 words]
└── FAQ: [Common questions - 1,500 words]
Each cluster should:
  • Target a primary keyword theme
  • Cover the topic comprehensively for topical authority
  • Include varied content types (guides, comparisons, how-tos, listicles)
  • Support internal linking between cluster pages
设计3-5个主题集群(支柱内容+支撑内容):
Cluster: [Pillar Topic]
├── Pillar Page: [Comprehensive guide - 3,000+ words]
├── Supporting: [Subtopic 1 - 2,000 words]
├── Supporting: [Subtopic 2 - 2,000 words]
├── Supporting: [Subtopic 3 - 1,500 words]
├── Comparison: [X vs Y - 1,500 words]
└── FAQ: [Common questions - 1,500 words]
每个集群需满足:
  • 瞄准一个核心关键词主题
  • 全面覆盖主题以构建权威性
  • 包含多样内容类型(指南、对比文、教程、清单文)
  • 支持集群内页面的内部链接

Step 2.5: Content Decay Detection

步骤2.5:内容衰减检测

Scan existing blog posts for
lastUpdated
or
date
fields in frontmatter. Classify each post by staleness using these thresholds:
Traffic LevelStale ThresholdAt-Risk Threshold
High-traffic posts>30 days since update>90 days
Medium-traffic posts>90 days since update>180 days
Low-traffic posts>180 days since update>365 days
Reference: 76% of top AI citations are from content updated within 30 days.
Output a decay report:
undefined
扫描现有博客文章前置元数据中的
lastUpdated
date
字段。根据以下阈值对每篇文章的陈旧程度进行分类:
流量等级陈旧阈值风险阈值
高流量文章距离上次更新超过30天超过90天
中流量文章距离上次更新超过90天超过180天
低流量文章距离上次更新超过180天超过365天
参考数据:76%的顶级AI引用来自30天内更新的内容。
输出衰减报告:
undefined

Content Decay Report

内容衰减报告

PostLast UpdatedDays StalePriorityAction
[slug][date][N]CriticalRefresh immediately
[slug][date][N]HighSchedule this month
[slug][date][N]MediumSchedule this quarter

Priority levels:
- **Critical**: High-traffic post stale >30 days -- refresh immediately
- **High**: Any post stale beyond its threshold -- schedule this month
- **Medium**: Posts approaching their threshold -- schedule this quarter
- **Low**: Posts within threshold -- no action needed
文章上次更新时间陈旧天数优先级行动
[slug][date][N]紧急立即更新
[slug][date][N]本月安排更新
[slug][date][N]本季度安排更新

优先级说明:
- **紧急**:高流量文章陈旧超过30天——立即更新
- **高**:任何超过对应阈值的文章——本月安排更新
- **中**:接近阈值的文章——本季度安排更新
- **低**:在阈值范围内的文章——无需操作

Step 3: Freshness Update Schedule

步骤3:新鲜度更新日程

AI platforms heavily favor fresh content (76% of top citations updated within 30 days).
Plan update cycles:
  • High-priority posts (traffic drivers): Update every 30 days
  • Medium-priority posts: Update every 90 days
  • Low-priority posts: Update annually
  • Evergreen posts: Update when data changes
AI平台高度偏好新鲜内容(76%的顶级AI引用来自30天内更新的内容)。
规划更新周期:
  • 高优先级文章(流量驱动型):每30天更新一次
  • 中优先级文章:每90天更新一次
  • 低优先级文章:每年更新一次
  • 常青内容:数据发生变化时更新

Step 4: Seasonal & Trending Hooks

步骤4:季节性与热点切入点

Research seasonal opportunities:
  1. Industry events -- Conferences, product launches, algorithm updates
  2. Seasonal trends -- Use WebSearch to check Google Trends for the niche
  3. Annual reports -- When do major studies release new data?
  4. Algorithm updates -- Google core updates (typically 3-4 per year)
调研季节性机会:
  1. 行业活动——会议、产品发布、算法更新
  2. 季节性趋势——使用WebSearch查询细分领域的Google Trends数据
  3. 年度报告——重要研究报告的发布时间
  4. 算法更新——Google核心更新(通常每年3-4次)

Seasonal Trends Integration

季节性趋势整合

  • Map seasonal peaks to content production schedule
  • Plan content 4-6 weeks before seasonal peaks for indexing lead time
  • Create "evergreen with seasonal hook" content (e.g., "X Guide [Year]" updated annually)
  • Track industry report release cycles:
    • Ahrefs Annual State of SEO (typically Q1)
    • Google Year in Search (December)
    • HubSpot State of Marketing (Q1)
    • Gartner Hype Cycle (August)
    • Major conference dates in the niche
  • Use WebSearch to validate timing of trends before scheduling
  • 将季节性峰值与内容制作日程匹配
  • 在季节性峰值前4-6周规划内容,预留索引时间
  • 创建“常青内容+季节性切入点”的内容(例如:每年更新的《[年份] X指南》)
  • 追踪行业报告发布周期:
    • Ahrefs年度SEO现状报告(通常Q1发布)
    • Google年度搜索回顾(12月发布)
    • HubSpot年度营销现状报告(Q1发布)
    • Gartner技术成熟度曲线(8月发布)
    • 细分领域的重要会议日期
  • 安排前使用WebSearch验证趋势时间

Step 5: Generate the Calendar

步骤5:生成日历

Content Mix Formula

内容组合公式

Apply the recommended content mix ratio: 60% new content / 30% freshness updates / 10% repurposed content
CadenceMonthly PostsNewRefreshesRepurposed
2 posts/week8521
3 posts/week12741
4 posts/week161051
1 post/week42-310-1
Within new posts, aim for content type diversity:
  • Guides/How-tos: 30-40% of new content
  • Comparisons/Alternatives: 15-20%
  • Listicles/Roundups: 15-20%
  • Case studies/Data research: 10-15%
  • Thought leadership/News analysis: 10-15%
应用推荐的内容组合比例: 60%全新内容 / 30%新鲜度更新 / 10%二次创作内容
发布节奏月度文章数量全新内容更新内容二次创作内容
每周2篇8521
每周3篇12741
每周4篇161051
每周1篇42-310-1
在全新内容中,需保证内容类型多样性:
  • 指南/教程:占全新内容的30-40%
  • 对比/替代方案:15-20%
  • 清单/汇总文:15-20%
  • 案例研究/数据调研:10-15%
  • 思想领导力/新闻分析:10-15%

Template Integration

模板集成

For each new post entry, recommend a content template from these 12 available:
how-to-guide
,
listicle
,
case-study
,
comparison
,
pillar-page
,
product-review
,
thought-leadership
,
roundup
,
tutorial
,
news-analysis
,
data-research
,
faq-knowledge
Reference:
references/content-templates.md
for full template details.
为每篇新文章条目推荐以下12种可用内容模板之一:
how-to-guide
,
listicle
,
case-study
,
comparison
,
pillar-page
,
product-review
,
thought-leadership
,
roundup
,
tutorial
,
news-analysis
,
data-research
,
faq-knowledge
参考:
references/content-templates.md
获取完整模板详情。

Monthly Calendar Format

月度日历格式

undefined
undefined

Editorial Calendar: [Month Year]

编辑日历:[年月]

Publishing Cadence: [N] posts/week

发布节奏:每周[N]篇

Content Mix: [N] new / [N] refreshes / [N] repurposed

内容组合:[N]篇全新 / [N]篇更新 / [N]篇二次创作

Week 1: [Date Range]

第1周:[日期范围]

DayTypeTitleTemplateClusterTarget KeywordStatus
MonNew[Title]how-to-guide[Cluster][keyword]Draft
ThuUpdate[Existing post]--[Cluster][keyword]Refresh
日期类型标题模板集群目标关键词状态
周一全新[标题]how-to-guide[集群][keyword]草稿
周四更新[现有文章]--[集群][keyword]更新中

Week 2: [Date Range]

第2周:[日期范围]

DayTypeTitleTemplateClusterTarget KeywordStatus
MonNew[Title]comparison[Cluster][keyword]Brief
ThuNew[Title]listicle[Cluster][keyword]Brief
日期类型标题模板集群目标关键词状态
周一全新[标题]comparison[集群][keyword]大纲
周四全新[标题]listicle[集群][keyword]大纲

Week 3: [Date Range]

第3周:[日期范围]

[...]
[...]

Week 4: [Date Range]

第4周:[日期范围]

[...]
[...]

Content Mix This Month

本月内容组合

  • New posts: [N]
  • Freshness updates: [N]
  • Repurposed content: [N]
  • Content types: [guides, comparisons, how-tos, listicles, ...]
  • 全新文章:[N]
  • 新鲜度更新:[N]
  • 二次创作内容:[N]
  • 内容类型:[指南、对比文、教程、清单文...]

Freshness Update Queue

新鲜度更新队列

PostLast UpdatedPriorityScheduled
[slug][date]HighWeek 2
[slug][date]MediumWeek 4
文章上次更新时间优先级安排时间
[slug][date]第2周
[slug][date]第4周

Seasonal Hooks

季节性切入点

  • [Event/trend and how to leverage it]
undefined
  • [事件/趋势及利用方式]
undefined

Quarterly Calendar Format

季度日历格式

undefined
undefined

Quarterly Editorial Plan: Q[N] [Year]

季度编辑规划:第[N]季度 [年份]

Content Strategy

内容策略

  • Topic clusters: [N] active
  • New posts planned: [N]
  • Freshness updates planned: [N]
  • Repurposed content: [N]
  • Total content actions: [N]
  • 主题集群:[N]个活跃集群
  • 计划发布全新文章:[N]
  • 计划进行新鲜度更新:[N]
  • 二次创作内容:[N]
  • 内容行动总数量:[N]

Month 1: [Month]

第1个月:[月份]

Focus: [Primary cluster or theme]

重点:[核心集群或主题]

WeekTypeTitleTemplateClusterKeyword
W1New...how-to-guide......
W1Update...--......
W2New...comparison......
[...]
类型标题模板集群关键词
W1全新...how-to-guide......
W1更新...--......
W2全新...comparison......
[...]

Month 2: [Month]

第2个月:[月份]

Focus: [Primary cluster or theme]

重点:[核心集群或主题]

[...]
[...]

Month 3: [Month]

第3个月:[月份]

Focus: [Primary cluster or theme]

重点:[核心集群或主题]

[...]
[...]

Quarterly Goals

季度目标

  • Publish [N] new posts
  • Update [N] existing posts for freshness
  • Complete [Cluster] pillar + [N] supporting pages
  • Achieve [metric target]
undefined
  • 发布[N]篇全新文章
  • 完成[N]篇现有文章的新鲜度更新
  • 完成[集群]支柱内容 + [N]篇支撑页面
  • 达成[指标目标]
undefined

Step 5.5: Topic Cluster Progress Tracking

步骤5.5:主题集群进度追踪

Track the build-out state of each topic cluster. Prioritize completing partially-built clusters over starting new ones.
undefined
追踪每个主题集群的构建状态。优先完成部分构建的集群,而非启动新集群。
undefined

Topic Cluster Progress

主题集群进度

ClusterPillarSpokes PublishedSpokes PlannedCoverage
[Topic]Published5/105 this quarter50%
[Topic]Draft2/83 this quarter25%
[Topic]Not started0/61 this quarter0%

Rules for cluster prioritization:
- Clusters at 50%+ coverage: highest priority to complete
- Clusters with published pillar but few spokes: second priority
- New clusters: only start when existing clusters reach 75%+ coverage
- Never have more than 3 clusters in active build-out simultaneously
集群支柱内容状态已发布支撑内容计划支撑内容覆盖度
[主题]已发布5/10本季度5篇50%
[主题]草稿2/8本季度3篇25%
[主题]未启动0/6本季度1篇0%

集群优先级规则:
- 覆盖度50%+的集群:最高优先级完成
- 已发布支柱内容但支撑内容较少的集群:次优先级
- 新集群:仅当现有集群覆盖度达75%+时启动
- 同时进行构建的集群数量不超过3个

Step 5.6: Distribution Scheduling

步骤5.6:分发日程规划

For each new post, plan distribution across channels. Include distribution timing in the calendar output.
undefined
为每篇新文章规划多渠道分发,并在日历输出中包含分发时间。
undefined

Distribution Schedule

分发日程

PostPublish DateLinkedInRedditEmailYouTube
[Title][Date]Same day+2-3 daysNext batchIf pillar

Channel timing rules:
- **LinkedIn**: Same day as publish (share key insight + link)
- **Reddit**: 2-3 days after publish (share genuine insight, not a link drop)
- **Email newsletter**: Batch weekly (include 2-3 posts per newsletter)
- **YouTube**: Plan companion video for pillar posts only (resource-intensive)
- **Twitter/X**: Same day as publish (thread key takeaways)

Reference: `references/distribution-playbook.md` for detailed channel tactics.
文章发布日期LinkedInReddit邮件YouTube
[标题][Date]发布当日发布后2-3天下一批邮件仅支柱内容制作

渠道时间规则:
- **LinkedIn**:发布当日分享(分享核心见解+链接)
- **Reddit**:发布后2-3天分享(分享真实见解,而非直接发链接)
- **邮件通讯**:每周批量发送(每封邮件包含2-3篇文章)
- **YouTube**:仅为支柱内容制作配套视频(资源消耗大)
- **Twitter/X**:发布当日分享(拆分核心要点成推文串)

参考:`references/distribution-playbook.md`获取详细渠道策略。

Step 5.7: Freshness Automation

步骤5.7:新鲜度自动化

Set up a system for ongoing freshness maintenance:
undefined
搭建持续新鲜度维护系统:
undefined

Freshness Schedule: Next 30 Days

新鲜度日程:未来30天

PostLast UpdatedNext Refresh DatePriorityOwner
[slug][date][date + 30]High[name]
[slug][date][date + 90]Medium[name]

Automation recommendations:
- Set calendar reminders for 30-day refresh cycles on high-traffic posts
- List posts by "next refresh date" in ascending order (most urgent first)
- Prioritize refresh order by traffic/importance
- After each refresh, update the `lastUpdated` frontmatter field
- Track refresh history to measure freshness impact on rankings/citations
- Suggest running `/blog rewrite` for each scheduled refresh
文章上次更新时间下次更新日期优先级负责人
[slug][date][date + 30][姓名]
[slug][date][date + 90][姓名]

自动化建议:
- 为高流量文章的30天更新周期设置日历提醒
- 按“下次更新日期”升序排列文章(最紧急的排在前面)
- 按流量/重要性优先排序更新顺序
- 每次更新后,更新前置元数据中的`lastUpdated`字段
- 追踪更新历史,衡量新鲜度对排名/引用的影响
- 建议为每个计划更新的文章运行`/blog rewrite`

Step 6: Save & Next Steps

步骤6:保存与后续步骤

Save the calendar and suggest:
  1. Start with
    /blog brief <first-topic>
    to create the first content brief
  2. Use
    /blog write
    to generate articles from briefs
  3. Use
    /blog rewrite
    for freshness updates on existing content
  4. Re-run
    /blog calendar
    next month/quarter for the next plan
  5. Review the Content Decay Report weekly and address Critical items first
  6. Track Topic Cluster Progress monthly to ensure clusters reach completion
保存日历并建议:
  1. 先运行
    /blog brief <first-topic>
    创建首个内容大纲
  2. 使用
    /blog write
    根据大纲生成文章
  3. 使用
    /blog rewrite
    对现有内容进行新鲜度更新
  4. 下月/下季度重新运行
    /blog calendar
    生成新规划
  5. 每周查看内容衰减报告,优先处理紧急项
  6. 每月追踪主题集群进度,确保集群完成构建