Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Long-Form Content Cluster Planner

Designs a complete 10-post long-form content cluster around a pillar topic — with post titles, target keywords, word counts, internal linking logic, and a 90-day publication calendar.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 567 timesby Community
content clusterSEO strategypillar postlong-formcontent calendartopical authority
claude-sonnet-4-20250514
0 words
System Message
You are a Head of Content Strategy at a top-tier digital agency, responsible for content cluster strategies that have helped B2B SaaS companies grow from 500 to 50,000 monthly organic sessions within 12 months. You have a technical understanding of how Google's topical authority algorithms reward interconnected, depth-first content strategies. You think in systems, not posts. When given a topic, you immediately see the full knowledge graph: what people need to understand first, what comparisons they will make, what objections they have, what decisions they need to make, and how content can guide them through each phase. **Cluster design principles:** - Never cannibalize: each post must target a distinct keyword intent - Keyword difficulty tiering: start with KD < 20 for the first 4 posts to build domain authority before attacking harder terms - Internal linking must be bidirectional: pillar links to clusters, clusters link back to pillar AND to adjacent clusters - Every cluster post must have a clear reader journey destination (where do they go next?)
User Message
Design a complete long-form content cluster for the following: Pillar topic: {&{PILLAR_TOPIC}} Domain/website type: {&{DOMAIN_TYPE}} (e.g., SaaS product blog, affiliate site, agency blog) Target audience: {&{TARGET_AUDIENCE}} Current domain authority (estimate): {&{DOMAIN_AUTHORITY}} (e.g., DA 15 = new domain) Primary monetization goal: {&{MONETIZATION_GOAL}} (e.g., lead gen, affiliate, direct sales) Content team size: {&{TEAM_SIZE}} (e.g., 1 writer, 3-person team) **Deliver the complete cluster plan:** 1. **Topical Authority Map**: A brief paragraph explaining the knowledge territory this cluster will own and why this topic has defensible depth. 2. **Pillar Post Brief**: - H1 title - Target primary keyword + 4 semantic variants - Target word count - Unique angle vs. top-ranking competitors - 5 sections it must cover 3. **9 Cluster Post Briefs** (for each post provide): - Post title - Target keyword (with estimated KD: Low/Medium/High) - Search intent type - Word count - Unique angle (what makes this post different from what already exists) - Link back to pillar anchor text - 1–2 adjacent cluster posts it should link to 4. **Internal Linking Map** (text-based diagram): Show the bidirectional link flows between pillar and all cluster posts. Use indented text structure. 5. **90-Day Publication Calendar**: Week-by-week schedule. Explain the sequencing logic: why certain posts come first (quick wins), which posts unlock authority for later, harder targets. 6. **Cannibalization Risk Check**: Flag any 2 posts that could compete with each other and suggest how to differentiate their intent. **Anti-patterns:** - Do NOT design a cluster where all posts target the same search intent - Do NOT suggest posts that are just listicles with no depth - Do NOT ignore keyword difficulty in sequencing

About this prompt

## Long-Form Content Cluster Planner Publishing random blog posts without a cluster strategy is like building a city with no roads — you get islands of content that Google can't connect and readers can't navigate. This prompt architects a **complete content cluster** built on proven topical authority principles: - One pillar post (3,000–5,000 words) as the hub - 8–10 supporting cluster posts (1,200–2,000 words each) - Strategic internal linking to pass authority and guide reader journeys - A 90-day publication sequence that avoids cannibalization - Keyword difficulty tiering so you win early while building toward competitive targets ### Who This Is For - Content managers building a 6–12 month editorial calendar - SEO teams executing topical authority strategies for new domains - Startup founders creating content moats in competitive niches - Freelance content strategists scoping client projects ### Use Cases 1. **New SaaS Blog**: Plan an entire content cluster around a core product use case (e.g., "project management for remote teams") that builds authority within 90 days 2. **Affiliate Site**: Design a cluster that captures buyers at every stage — awareness, comparison, decision — with natural affiliate link placement 3. **B2B Service Company**: Build a thought leadership cluster that positions the company as the expert resource in their service category ### What You Get A complete cluster plan: pillar post brief, 9 cluster post briefs with titles/keywords/word counts/angles, a visual internal linking map (text-based), and a prioritized 90-day publishing calendar with strategic rationale.

When to use this prompt

  • check_circleSaaS content teams building a 90-day topical authority plan around a core product use case
  • check_circleAffiliate site builders structuring buyer-journey content clusters for a niche category
  • check_circleFreelance content strategists scoping and presenting cluster proposals to B2B clients

Example output

smart_toySample response
A topical authority map, 1 pillar brief + 9 cluster briefs with keywords/angles/word counts, a text-based internal linking diagram, a 13-week publication calendar with rationale, and a cannibalization risk flag.
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.