content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

Content Strategy

You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.

Before Planning

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context

2. Customer Research

3. Current State

4. Competitive Landscape


Treat Content Like a Product

Every piece is its own launch. Content isn't overhead—it's brand surface area: each published piece is a new entry point where a stranger can discover you, and hundreds of pieces compound into hundreds of doorways working 24/7. Plan, ship, and promote each piece with the same intent you'd bring to a product release. A post that's written and forgotten has almost no surface area; a post that's distributed (see Create Once, Distribute Twice below) multiplies it.

This section covers the searchable/shareable lens, then the execution and prioritization layer: which pieces to make (scoring), how the calendar splits, and per-format discipline.

Searchable vs Shareable

Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.

Searchable content captures existing demand. Optimized for people actively looking for answers.

Shareable content creates demand. Spreads ideas and gets people talking.

When Writing Searchable Content

The information-gain gate: before committing to a searchable piece, read the current top results for its query and write one sentence on what yours will add that none of them have: original data, a real product example, a working tool or template, a clearer answer, a stronger opinion. If you can't write that sentence, don't write the piece. It will be the eleventh copy of the same article, and neither Google nor AI assistants have a reason to prefer it.

When Writing Shareable Content


Content Types

Searchable Content Types

Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords.

Hub and Spoke Hub = comprehensive overview. Spokes = related subtopics.

B0 Create hub first, then build spokes. Interlink strategically.

Note: Most content works fine under /blog. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's /agile guide). For typical blog posts, /blog/post-title is sufficient.

Template Libraries High-intent keywords + product adoption.

Shareable Content Types

Thought Leadership

Data-Driven Content

Expert Roundups 15-30 experts answering one specific question. Built-in distribution.

Case Studies Structure: Challenge → Solution → Results → Key learnings

Meta Content Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."

When the goal of a piece is backlinks specifically, format choice matters more than production effort. Foundation Inc.'s B2B Backlink Intelligence Report (March 2026 — a single vendor study of B2B SaaS sites, so treat as directional) measured each format's share of backlinks relative to its share of pages:

FormatBacklinks vs. page share
Statistics / data roundups4.25x
Glossary / definition pages1.47x
Interactive tools / calculators (see free-tools)1.38x
How-to / tutorials1.36x
Original research / reports0.80x
Ultimate guides0.77x
Thought leadership0.74x
Templates / frameworks0.68x

The counterintuitive read: curating statistics earns ~5x the links of producing original research. Writers link to whatever makes citation easiest — a maintained stat-roundup page is citation infrastructure, while original research often gets cited via the roundups that aggregate it. Implications: (1) publish a stats page for your category and keep it fresh — it's cheap and compounds, and citable one-line stats are also what LLMs lift, making it an AI-visibility play (see ai-seo); (2) when you do run original research, pair it with your own stat-roundup page that presents the findings as citable one-liners, so you capture the links your data generates. The formats at the bottom aren't dead — guides, templates, and thought leadership earn their keep on rankings, conversions, and brand. Judge each piece by the job it's for, and don't expect links from formats that don't earn them.

For programmatic content at scale, see programmatic-seo skill.


Content Pillars and Topic Clusters

Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.

Most of the time, all content can live under /blog with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like /guides/topic) are only needed when you're building comprehensive resources with multiple layers of depth.

How to Identify Pillars

  1. Product-led: What problems does your product solve?
  2. Audience-led: What does your ICP need to learn?
  3. Search-led: What topics have volume in your space?
  4. Competitor-led: What are competitors ranking for?

Pillar Structure

B1

Pillar Criteria

Good pillars should:


Keyword Research by Buyer Stage

Map topics to the buyer's journey using proven keyword modifiers:

Awareness Stage

Modifiers: "what is," "how to," "guide to," "introduction to"

Example: If customers ask about project management basics:

Consideration Stage

Modifiers: "best," "top," "vs," "alternatives," "comparison"

Example: If customers evaluate multiple tools:

Decision Stage

Modifiers: "pricing," "reviews," "demo," "trial," "buy"

Example: If pricing comes up in sales calls:

Implementation Stage

Modifiers: "templates," "examples," "tutorial," "how to use," "setup"

Example: If support tickets show implementation struggles:


Content Ideation Sources

1. Keyword Data

If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:

Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |

2. Call Transcripts

If user provides sales or customer call transcripts, extract:

Output content ideas with supporting quotes.

3. Survey Responses

If user provides survey data, mine for:

4. Forum Research

Use web search to find content ideas:

Reddit: site:reddit.com [topic]

Quora: site:quora.com [topic]

Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord

Extract: FAQs, misconceptions, debates, problems being solved, terminology used.

5. Competitor Analysis

Use web search to analyze competitor content:

Find their content: site:competitor.com/blog

Analyze:

Identify opportunities:

6. Sales and Support Input

Extract from customer-facing teams:


Prioritizing Content Ideas

Score each idea on four factors:

1. Customer Impact (40%)

2. Content-Market Fit (30%)

3. Search Potential (20%)

4. Resource Requirements (10%)

Scoring Template

IdeaCustomer Impact (40%)Content-Market Fit (30%)Search Potential (20%)Resources (10%)Total
Topic A89768.0
Topic B67987.1

Score 1-10 per factor, multiply by the weight, sum for the total. Rank the list; make the top-scoring pieces first.


Calendar Split: 60/30/10

Balance the editorial calendar so search compounds while shareable pieces keep you visible:

This is a starting ratio, not a rule. A brand-new blog may over-index on searchable to build a base; an established brand chasing category leadership may push shareable higher.


Per-Format Execution Discipline

Treating content like a product means each format has a production standard, not just a topic:


Create Once, Distribute Twice

Creating content is half the job—distribution is the other half, and most teams skip it. The philosophy: one exceptional piece, reformatted and repurposed across every channel, not a fresh piece per platform. Pouring effort into a single flagship and then distributing it everywhere beats spreading thin effort across many mediocre platform-native posts.

Build distribution hooks into the piece at creation time, not after: write subheads that stand alone as social posts, structure sections to be lifted out modularly, and pull quotes/stats you already know you'll graphic-ify. A well-designed guide is a distribution kit in disguise.

The ORB Framework as a funnel — route attention from borrowed → rented → owned, which maps to discovery → engagement → conversion:

ORB mechanics live in the launch skill (channel-type playbook) and content atomization/repurposing lives in social; the value here is consolidating the distribute half of content strategy so it has a home.

Failure modes to avoid:

For the full distribution spine—the Content Distribution Flywheel, platform half-lives, and the atomization checklist—see the reference below.


Output Format

When creating a content strategy, provide:

1. Content Pillars

2. Priority Topics

For each recommended piece:

3. Topic Cluster Map

Visual or structured representation of how content interconnects.


Task-Specific Questions

  1. What patterns emerge from your last 10 customer conversations?
  2. What questions keep coming up in sales calls?
  3. Where are competitors' content efforts falling short?
  4. What unique insights from customer research aren't being shared elsewhere?
  5. Which existing content drives the most conversions, and why?

References



References

Content Distribution

content-distribution.md

Content Distribution Spine

The "distribute" half of content strategy. Creating a great piece is table stakes; the leverage is in getting it seen. This reference expands the Create Once, Distribute Twice section of the skill.

Cross-links: ORB channel-type playbook lives in launch; atomization/repurposing workflows (podcast → clips, blog → thread) live in social. This file consolidates the strategy that ties them together—don't re-derive ORB from scratch here.

Create Once, Distribute Twice

One exceptional piece, reformatted across channels—not a fresh piece per platform. The math is simple: a flagship piece plus ten repurposed cuts reaches far more people than eleven mediocre native posts, at a fraction of the effort.

The discipline is designing the piece to be distributed:

Treat the flagship as the master; every channel gets a cut derived from it.

The ORB Framework as a Funnel

Own, Rent, Borrow—read as a discovery → engagement → conversion funnel:

LayerChannelsFunnel roleYou control
BorrowedPodcasts, guest posts, partnerships, PR, other people's audiencesDiscovery / breakthroughNothing—it's a loan
RentedSocial platforms, ad networks, marketplacesEngagement / reachThe content, not the audience or algorithm
OwnedEmail list, blog, community, appConversion / retentionEverything—the durable asset

The strategic move: use borrowed and rented reach to funnel strangers into owned channels where you can convert and retain them. Borrowed and rented are rented land; owned is the only asset you keep.

The Ownership Paradox

Most teams invert the priority: they spend ~90% of effort on borrowed and rented channels they don't control, and neglect the owned assets that actually convert. The paradox is that the channels getting the least attention (email, blog, community) are the ones that compound and can't be revoked. Rebalance toward owned as the destination for all upstream effort.

Failure Modes

Platform Half-Lives

Content decays at wildly different rates by channel. Match the piece to the channel's shelf life:

ChannelRough half-lifeImplication
Twitter/X postMinutes–hoursPost often; repost; thread for reach
Instagram / Facebook~a dayFrequent cadence; stories are ephemeral by design
LinkedIn post~a day, longer for strong performersFewer, higher-effort posts
TikTok / Reels / ShortsDays–weeks (algorithmic resurfacing)Evergreen hooks can re-surface long after posting
YouTube videoMonths–yearsSearch-driven; compounds like a blog post
Blog post / SEOYearsThe long tail; the compounding asset
EmailSent once, but archived / repurposableOne-shot attention; harvest into other formats

Short half-life channels reward frequency and repetition; long half-life channels reward depth and evergreen framing. Owned, long-half-life formats (blog, YouTube, email archive) are where distribution effort compounds.

The Content Distribution Flywheel

Distribution isn't a linear checklist—it's a loop that feeds itself:

  1. Create one exceptional flagship piece (guide, video, podcast, original research), with distribution hooks built in.
  2. Atomize it into channel-native cuts—clips, threads, carousels, quote graphics, email, subhead-posts.
  3. Distribute across owned → rented → borrowed, routing everything back to owned.
  4. Engage with the responses; capture the questions, objections, and reactions.
  5. Feed back — the engagement surfaces the next flagship topic (what resonated, what got asked), and top-performing atoms signal what to make more of.

Each turn of the loop lowers the cost of the next piece (you learn what lands) and grows the owned audience that amplifies it. The flywheel is why consistent distributors pull away from one-off publishers over time.

Atomization Checklist (per flagship)

For each major piece, produce (see social for the platform-native execution):

Headless Cms

headless-cms.md

Headless CMS Guide

Reference for choosing, modeling, and implementing a headless CMS for marketing content.

When to Use This Reference

Use this when selecting a CMS for a new project, designing content models for marketing sites, setting up editorial workflows, or connecting CMS content to programmatic pages.


Headless vs Traditional CMS

A headless CMS separates content management from presentation. Content is stored in a structured backend and delivered via API to any frontend.

When Headless Makes Sense

When Traditional Works Better

Decision Checklist

FactorHeadlessTraditional
Multi-channel deliveryYesLimited
Developer controlFullConstrained
Non-technical editingRequires setupBuilt-in
Time to launchLongerFaster
Content reuseNativeManual
Hosting flexibilityAny frontendPlatform-dependent

Content Modeling for Marketing

Core Principles

  1. Think in types, not pages. A "Landing Page" is a content type with fields — not an HTML file. This lets you reuse components across pages.
  2. Separate content from presentation. Store the headline text, not the styled headline. Presentation belongs in the frontend.
  3. Design for reuse. If testimonials appear on 5 pages, create a Testimonial type and reference it — don't duplicate.
  4. Keep models flat. Deeply nested structures are hard to query and maintain. Prefer references over nesting.

Common Marketing Content Types

TypeKey FieldsNotes
Landing Pagetitle, slug, hero, sections[], seoModular sections for flexibility
Blog Posttitle, slug, body, author, category, tags, publishedAt, seoRich text or Portable Text body
Case Studytitle, customer, challenge, solution, results, metrics[], logoLink to related products/features
Testimonialquote, author, role, company, avatar, ratingReference from landing pages
FAQquestion, answer, categoryGroup by category for programmatic pages
Authorname, bio, avatar, social linksReference from blog posts
CTA Blockheading, body, buttonText, buttonUrl, variantReusable across pages

SEO Fields Checklist

Every page-level content type needs:


Editorial Workflows

Draft → Review → Publish Cycle

  1. Draft — Author creates or edits content
  2. Review — Editor reviews for accuracy, brand voice, SEO
  3. Approve — Stakeholder signs off
  4. Schedule — Set publish date/time
  5. Publish — Content goes live via API

Preview APIs

All major headless CMS platforms support draft previews:

Set up a preview route in your frontend (e.g., /api/preview) that authenticates and renders draft content.

Roles and Permissions

RoleCan CreateCan EditCan PublishCan Delete
AuthorYesOwnNoOwn drafts
EditorYesAllYesDrafts
AdminYesAllYesAll

Exact permission models vary by platform. Sanity uses role-based access. Contentful has space-level roles. Strapi has granular RBAC.


Platform Comparison

FeatureSanityContentfulStrapi
HostingCloud (managed)Cloud (managed)Self-hosted or Cloud
Query LanguageGROQREST / GraphQLREST / GraphQL
Free TierGenerousLimitedOpen source (free)
Real-time CollabYes (built-in)LimitedNo
Best ForDeveloper flexibilityEnterprise multi-localeBudget / self-hosted
Content ModelingSchema-as-codeWeb UIWeb UI or code
Media HandlingBuilt-in DAMBuilt-inPlugin-based

Sanity

Strengths: GROQ query language is powerful and flexible. Schema defined in code (version-controlled). Real-time collaborative editing. Portable Text for rich content. Generous free tier.

Considerations: Steeper learning curve for non-developers. Studio customization requires React knowledge. Vendor lock-in on GROQ queries.

Marketing fit: Best when developers and marketers collaborate closely. Strong for content-heavy sites with complex models.

Contentful

Strengths: Mature enterprise platform. Excellent multi-locale support. Strong ecosystem of integrations. Composable content with Studio. Well-documented APIs.

Considerations: Pricing scales with content types and locales. Two separate APIs (Delivery and Management). Rate limits can be tight on lower plans.

Marketing fit: Best for enterprises with multi-market content needs. Good when you need established vendor reliability.

Strapi

Strengths: Open source, self-hosted option. Full control over data. No per-seat pricing. Customizable admin panel. Plugin ecosystem. REST by default, GraphQL via plugin.

Considerations: Self-hosting means you handle infrastructure. Smaller ecosystem than Sanity/Contentful. V5 migration can be significant from V4.

Marketing fit: Best for teams with DevOps capability who want full control and no vendor lock-in. Good for budget-conscious projects.

Others Worth Knowing


Integration with Marketing Skills

Programmatic SEO

Use CMS as the data source for programmatic pages. Store structured data (FAQs, comparisons, city pages) as content types and generate pages from queries. See programmatic-seo skill.

Copywriting

CMS content models enforce consistent structure. Define fields that match your copy frameworks (headline, subheadline, social proof, CTA). See copywriting skill.

Site Architecture

URL structure, navigation hierarchy, and internal linking all depend on how content is organized in the CMS. Plan your content model and site architecture together. See site-architecture skill.

Email Sequences

Pull CMS content into email templates for consistent messaging across web and email. Case studies, testimonials, and blog posts can feed email nurture sequences. See emails skill.


Implementation Checklist


Relevant Integration Guides


Exported from Marketing Skills on 2026-10-12