Content Strategy
Plan pillar pages, topic clusters, and an editorial calendar so organic traffic compounds after you ship.
Overview
Content Strategy is an agent skill most often used in Launch (also Validate, Grow) that plans SEO topic clusters, pillar pages, cluster articles, and an editorial calendar from keyword and product context.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill content-strategyWhat is this skill?
- Structures topic clusters with pillar pages and supporting cluster articles
- Builds editorial calendars aligned to keyword clusters and business goals
- Uses product-led SEO framing (proof points, audience, existing content inventory)
- Reads `.claude/project-context.md` or `.cursor/project-context.md` when present for audience and positioning
- Pairs with keyword-research for discovery and content-marketing for cross-channel editorial mix
- metadata version 1.1.1
Adoption & trust: 913 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have keywords or a product but no coherent pillar-and-cluster plan, so every article competes with itself and nothing ranks.
Who is it for?
Solo founders shipping a marketing site, docs-heavy SaaS, or content business who already did or will do keyword research and need an execution map.
Skip if: Teams that only need a single ad-hoc blog outline, full-funnel email/social editorial (use content-marketing), or translation/localization workflow without SEO architecture.
When should I use this skill?
User wants content strategy, content plan, topic clusters, pillar content, editorial calendar, content hub, or content strategy for SEO.
What do I get? / Deliverables
You leave with a structured SEO content hub plan—pillars, clusters, and calendar priorities—ready to draft pages or hand off to content-marketing and publishing workflows.
- Topic cluster map with pillar and supporting articles
- Editorial calendar aligned to SEO priorities
- Assessment of existing content and capacity
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
SEO content strategy is the canonical launch/SEO shelf because it turns keyword research into a publishable site architecture and calendar aimed at ranking. Subphase seo matches triggers like pillar content, topic clusters, and content strategy for SEO—not one-off posts.
Where it fits
Decide which pillar topics are worth a landing proof versus full cluster investment before you code the whole site.
Map pillar URLs and cluster articles for launch-week publishing so new pages reinforce one intent.
Refresh the editorial calendar with new cluster gaps found in Search Console without breaking hub structure.
How it compares
Use for SEO hub architecture and calendars—not generic brainstorming chat or one-channel content marketing playbooks.
Common Questions / FAQ
Who is content-strategy for?
Indie builders and small teams who own their site and want repeatable organic growth through clusters and pillars, not sporadic posts.
When should I use content-strategy?
During Validate when scoping what to prove with content, at Launch when designing SEO hubs before publish, and in Grow when expanding clusters without cannibalizing keywords.
Is content-strategy safe to install?
It is procedural planning guidance; review the Security Audits panel on this Prism page before installing from any marketplace.
Workflow Chain
Requires first: keyword research
Then invoke: content marketing
SKILL.md
READMESKILL.md - Content Strategy
# 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 an