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 plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.
Best use case
content-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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 plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.
Teams using content-strategy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/content-strategy/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How content-strategy Compares
| Feature / Agent | content-strategy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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 plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
SKILL.md Source
# 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)
<-> internal links
Cluster 1 (subtopic, 800-2,500 words)
Cluster 2 (subtopic)
...
Cluster 6-12 (subtopics)
<-> 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 <-> cluster; cluster <-> 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 headingsRelated Skills
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.
pricing-strategy
When the user wants to plan, design, or optimize pricing strategy and structure. Also use when the user mentions "pricing strategy," "pricing model," "pricing tiers," "freemium," "value-based pricing," "anchoring," "price structure," or "monetization strategy." For pricing page, use pricing-page-generator.
discount-marketing-strategy
When the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.
paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
open-source-strategy
When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.
localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.