← 返回 Skills 市场
kostja94

content-strategy

作者 Kostja Zhang · GitHub ↗ · v1.1.1 · MIT-0
cross-platform ✓ 安全检测通过
227
总下载
0
收藏
0
当前安装
2
版本数
在 OpenClaw 中安装
/install content-strategy-seo
功能描述
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content p...
使用说明 (SKILL.md)

SEO Content: Content Strategy

Guides content strategy for SEO: topic clusters, pillar pages, cluster articles, and editorial planning. For content marketing across all channels (blog, email, social, video), see content-marketing. For translation workflow and multilingual content, see translation.

When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and proof points.

Identify:

  1. Keywords: From keyword research — see keyword-research for discovery and clustering
  2. Existing content: What already exists
  3. Resources: Content capacity, tools
  4. Goals: Traffic, conversions, authority

Product-Led SEO: Do SEO around product/users, not around industry/search engines. See seo-strategy for Product-Led SEO principle, products suited for SEO, and workflow order.

Topic Clusters

Topic clusters organize content by topic rather than isolated keywords. A pillar page covers a broad core topic; cluster articles cover subtopics; all connect via internal links. This signals topical authority to search engines and AI systems.

Structure

Pillar page (broad topic, 2,000-5,000+ words)
    \x3C-> internal links
Cluster 1 (subtopic, 800-2,500 words)
Cluster 2 (subtopic)
...
Cluster 6-12 (subtopics)
    \x3C-> cluster to cluster links

Pillar Page

Attribute Guideline
Length 2,000-5,000+ words; comprehensive guide
Keyword Broad head term with search volume
Role Hub; links to all cluster articles; targets primary topic
Conversion Link to product/feature pages where relevant

Cluster Articles

Attribute Guideline
Count 6-12 articles per pillar (minimum 6 for authority)
Length 800-2,500 words each; focused on one subtopic
Keyword Long-tail, specific intent per article
Links Each cluster links to pillar; pillar links back; related clusters link to each other

Internal Linking Model

Link type Purpose
Pillar to Cluster Hub distributes authority; users discover subtopics
Cluster to Pillar Signals relationship; passes equity to hub
Cluster to Cluster Related subtopics; strengthens topical coverage

Structure and Content Equally Important

Framework and body quality both matter: TOC, chapter logic, and content depth are all essential for SEO and UX. Weak structure undermines strong writing; weak writing undermines strong structure. Plan both from the start.

Why Topic Clusters Work

  • Topical authority: Rank for multiple variations; comprehensive coverage signals expertise
  • Avoid cannibalization: One page per topic/keyword; no competing pages
  • Better internal linking: Clear logic; crawlers understand structure
  • AI citations: Clustered content gets ~42% more AI citations than standalone
  • Traffic: ~30% more organic traffic; rankings hold ~2.5x longer

Implementation Steps

  1. Choose 3-7 core topics -> business relevance, search demand, competitive opportunity
  2. Map subtopics -> People Also Ask, competitor analysis, keyword tools
  3. Content audit -> Identify existing pages that can become pillar or cluster; find gaps
  4. Build clusters first (optional) -> Cluster pages often rank first; add pillar after
  5. Create pillar -> Comprehensive guide; link to all clusters
  6. Establish links -> Pillar \x3C-> cluster; cluster \x3C-> cluster
  7. Update quarterly -> Maintain freshness and authority

Example

  • Pillar: "SEO Guide" (targets "SEO")
  • Clusters: "Technical SEO," "On-Page SEO," "Link Building," "Content SEO," "Local SEO," "E-E-A-T"

Content Types

Type Use SEO Fit
How-to guides Informational intent; high share potential High -> matches search intent
Comparisons Commercial intent; "X vs Y" High
List posts "Top 10," "Best X" High
Glossaries Definition queries; internal link hub High
Tools/calculators Linkable assets; engagement High
Case studies Proof; conversion support Medium -> supports conversion
Funding / PR Funding rounds, acquisitions Low -> brand/PR, not search-driven
Product updates Feature launches, release notes Low -> internal audience
News / Trending Industry news, hot topics Medium -> quick spikes, short shelf life

Evergreen vs Timely Content Mix

  • Evergreen (70-75%): Pillar guides, how-tos, comparisons, glossaries. Drives long-term traffic, backlinks, authority. Refresh every 6-12 months.
  • Timely (25-30%): Seasonal, trending, news. Generates quick traffic, shows topical relevance. Link timely pieces into evergreen pillars.
  • Balance: Too much evergreen = blog feels stale; too much timely = irregular traffic, constant content churn.

Editorial Calendar

  • Map keywords to content pieces
  • Prioritize by opportunity (volume -> intent -> feasibility)
  • Schedule by capacity
  • Include update schedule for existing content

Output Format

  • Topic cluster map (pillar + 6-12 clusters)
  • Content calendar (topics, keywords, deadlines)
  • Internal linking plan
  • Update plan for existing content

Related Skills

  • content-marketing: Content types, formats, channels, repurposing; SEO content is one channel
  • translation: Multilingual content; translation workflow, glossary; avoid thin translations
  • seo-strategy: SEO workflow order, Product-Led SEO, audit approach; use when planning SEO from scratch
  • website-structure: Plan which pages to build; structure informs content clusters and pillar placement
  • keyword-research: Keywords drive content plan
  • programmatic-seo: Programmatic SEO for scaling pages with template + data; complements topic clusters
  • content-optimization: Word count, H2 keywords, keyword density, multimedia, lists -> on-page content optimization
  • internal-links: Clusters need internal linking
  • link-building: Content strategy creates linkable assets
  • heading-structure: Content structure uses headings
安全使用建议
This skill appears coherent and low-risk: it is instruction-only and asks only to read optional project-context files for useful context. Before installing, check whether .claude/project-context.md or .cursor/project-context.md (if present) contain sensitive secrets or proprietary data you don't want the agent to read; if so, remove or redact those files or avoid enabling the skill for sensitive projects. If you are concerned about autonomous agent actions, control agent invocation policies (rather than leaving the agent fully autonomous) or review outputs before publishing content.
能力评估
Purpose & Capability
The name/description (content strategy, topic clusters, editorial calendar) match the SKILL.md guidance. The skill does not request unrelated credentials, binaries, or installs that would be inappropriate for a content-planning helper.
Instruction Scope
Instructions are narrowly focused on SEO content planning, topic clusters, pillar/cluster structure, and editorial calendars. The only file reads it suggests are .claude/project-context.md or .cursor/project-context.md for product/audience context — reasonable for content work but those files can contain sensitive internal info, so granting access to workspace files is the main runtime surface to review.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or downloaded during install, which minimizes risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. There is no disproportionate request for secrets or unrelated service tokens.
Persistence & Privilege
always:false (default) and normal autonomous invocation are used. The skill does not request persistent system-wide privileges or modification of other skills' configs.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install content-strategy-seo
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /content-strategy-seo 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.1.1
Automated batch sync
v1.1.0
Automated batch sync
元数据
Slug content-strategy-seo
版本 1.1.1
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 2
常见问题

content-strategy 是什么?

When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content p... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 227 次。

如何安装 content-strategy?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install content-strategy-seo」即可一键安装,无需额外配置。

content-strategy 是免费的吗?

是的,content-strategy 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

content-strategy 支持哪些平台?

content-strategy 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 content-strategy?

由 Kostja Zhang(@kostja94)开发并维护,当前版本 v1.1.1。

💬 留言讨论