Pillar Page Template
Template: Pillar Page

Description: Comprehensive topic authority guide that serves as the central hub for a topic cluster.
# Template: Pillar Page **Description:** Comprehensive topic authority guide that serves as the central hub for a topic cluster. Pillar pages provide broad, thorough coverage of a subject and link out to supporting articles that dive deeper into sub-topics. **Target Word Count:** 3,000-4,000 words --- ## When to Use This Template - **Content Goal:** Establish topical authority and create an SEO hub that ranks for high-volume head terms - **Search Intent:** Informational (users want a complete understanding of a topic) - **Funnel Stage:** Top-of-funnel awareness and mid-funnel education - **Use When:** - Targeting a broad, competitive keyword with high search volume - You have (or plan to create) 5+ supporting articles on sub-topics - The topic is complex enough to warrant 3,000+ words of coverage - You want to build a content cluster architecture around this topic
Overview
Description: Comprehensive topic authority guide that serves as the central hub for a topic cluster. Pillar pages provide broad, thorough coverage of a subject and link out to supporting articles that dive deeper into sub-topics.
Manual install (npx, ZIP)
npx skills add AgriciDaniel/claude-blog --skill template-pillar-page -g -a claude-codeConnects with Agent Alley MCP · agentalley.io/mcp
Files included
pillar-page.md13.2 KB
Read pillar-page.md here
AgriciDaniel/
Show the full text310 lines
Template: Pillar Page
Description: Comprehensive topic authority guide that serves as the central hub for a topic cluster. Pillar pages provide broad, thorough coverage of a subject and link out to supporting articles that dive deeper into sub-topics.
Target Word Count: 3,000-4,000 words
When to Use This Template
- Content Goal: Establish topical authority and create an SEO hub that ranks for high-volume head terms
- Search Intent: Informational (users want a complete understanding of a topic)
- Funnel Stage: Top-of-funnel awareness and mid-funnel education
- Use When:
- Targeting a broad, competitive keyword with high search volume
- You have (or plan to create) 5+ supporting articles on sub-topics
- The topic is complex enough to warrant 3,000+ words of coverage
- You want to build a content cluster architecture around this topic
Section-by-Section Structure
Title
Format: "The Complete Guide to [Topic] in [Year]"
Guidelines:
- Include primary keyword naturally
- The year signals freshness and improves CTR
- Keep under 60 characters for full SERP display
# The Complete Guide to [Topic] in [Year]
[IMAGE] Hero image that visually represents the topic. Use a custom graphic or high-quality photo - not a generic stock image. Alt text should include the primary keyword.
TL;DR Box (40-60 words)
[ANSWER-FIRST] Provide a concise summary that directly answers the searcher's core question. A reader should be able to stop here and walk away informed. This box improves dwell time by immediately delivering value and earns featured snippet potential.
> **TL;DR:** [One to two sentences defining the topic and its importance.] [One sentence on the key takeaway or most surprising finding.] [One sentence on what action to take.] [STAT: key statistic that grounds the summary]
Table of Contents
Auto-generated from H2 headings. Use anchor links for jump navigation. This improves UX on long-form content and can generate sitelinks in SERPs.
## Table of Contents
- [What Is [Topic]?](#what-is-topic)
- [Why [Topic] Matters](#why-topic-matters)
- [Core Section 1](#core-section-1)
- [Core Section 2](#core-section-2)
- [Core Section 3](#core-section-3)
- [Core Section 4](#core-section-4)
- [Core Section 5](#core-section-5)
- [Core Section 6](#core-section-6)
- [Advanced: [Expert-Level Sub-topic]](#advanced-expert-level-sub-topic)
- [Tools & Resources](#tools-resources)
- [Getting Started](#getting-started)
- [FAQ](#faq)
Introduction (200-300 words)
[ANSWER-FIRST] Open with a clear, direct statement about what [Topic] is and why it matters right now. Do not bury the lead with backstory or fluff.
Structure:
- Opening hook (1-2 sentences): Lead with a compelling statistic or trend that creates urgency
- [STAT: current year statistic showing the scale or growth of this topic]
- Topic overview (2-3 sentences): Define the topic clearly for someone encountering it for the first time
- Relevance statement (1-2 sentences): Why this matters right now - what has changed recently?
- What the reader will learn (2-3 sentences): Preview the guide's coverage - set expectations so the reader commits to reading
- Credibility indicator (1 sentence): Why should the reader trust this guide? (experience, data sources, methodology)
[INFO-GAIN: personal experience] Include a brief mention of your direct experience or research that qualifies this guide.
[INTERNAL-LINK] If you have a related "Why [Topic] Matters" article, link it from the relevance statement.
What Is [Topic]? (200-300 words)
[ANSWER-FIRST] Start with a one-sentence definition that could serve as a featured snippet. Keep it jargon-free for accessibility.
Structure:
- Clear definition (1-2 sentences): Simple, authoritative definition of the topic
- Context and scope (2-3 sentences): Where this fits in the broader landscape - what category does it belong to?
- Key components (3-5 bullet points): Break the topic into its essential parts or characteristics
- Common misconceptions (1-2 sentences): Address what this topic is NOT to prevent confusion
- Brief history or evolution (2-3 sentences): How the topic has developed to its current state
[VISUAL: chart-type] Include a diagram or infographic showing the key components and how they relate to each other. Suggested: labeled diagram, flowchart, or concept map.
[STAT: definition-supporting data point] Include at least one data point that contextualizes the topic's scope or importance.
[INTERNAL-LINK] Link key terms to their own dedicated articles if they exist in the cluster.
Why [Topic] Matters (200-300 words)
[ANSWER-FIRST] Lead with the single most compelling reason this topic deserves attention. Quantify the impact wherever possible.
Structure:
- Primary impact statement (1-2 sentences): The most important reason backed by data
- [STAT: impact or ROI statistic]
- Industry trends (2-3 sentences): Market data showing growth, adoption, or shifting priorities
- [STAT: trend or growth statistic]
- Consequences of ignoring (2-3 sentences): What happens if you do not engage with this topic?
- Opportunity framing (2-3 sentences): What is possible if you get this right?
- Who this affects (1-2 sentences): Specific roles, industries, or use cases
[VISUAL: chart-type] Bar chart or line graph showing growth trend, adoption curve, or impact data over time.
[INFO-GAIN: unique analysis] Include a data point or trend observation that is not commonly cited - something from your own research or analysis.
[INTERNAL-LINK] Link to case studies or data-driven articles that expand on the impact claims.
Core Sections (6-8 H2s, 300-400 words each)
Each core section covers a major sub-topic within the pillar. These sections should be comprehensive enough to stand alone but concise enough that a dedicated supporting article can go deeper.
For each core section, use this structure:
## [Sub-topic as H2 - written as a clear, keyword-rich heading]
[ANSWER-FIRST] Open with a 1-2 sentence answer or definition of this sub-topic before elaborating.
Structure per section:
- Direct answer or definition (1-2 sentences): What is this sub-topic and why does it matter within the broader topic?
- Key principles or steps (150-200 words): The essential knowledge, broken into:
- Numbered steps (for processes)
- Bullet points (for principles or characteristics)
- Sub-headings H3 (for complex sub-topics)
- Example or evidence (50-100 words): A specific, concrete example that illustrates the concept
- [INFO-GAIN: real-world example] Use a first-hand example, case study, or original observation when possible
- Common mistakes or pitfalls (50-75 words): What do people get wrong about this sub-topic?
- Transition to deeper content (1-2 sentences): Bridge to the next section or to a supporting article
[STAT: sub-topic-specific statistic] Include at least one data point per core section.
[IMAGE] Where applicable, include screenshots, process diagrams, or example visuals that support the explanation.
[INTERNAL-LINK] Link to the dedicated supporting article for this sub-topic. Use contextual anchor text (not "click here" or "read more").
Repeat this structure for each of the 6-8 core sections.
Advanced: [Expert-Level Sub-topic] (200-300 words)
[ANSWER-FIRST] Signal immediately that this section is for experienced practitioners, then deliver an advanced insight they will not find in beginner guides.
Structure:
- Audience gate (1 sentence): "If you're already [doing X], here's how to [achieve Y]."
- Advanced insight (100-150 words): A technique, framework, or perspective that goes beyond standard advice
- Evidence or application (50-75 words): Where this has been applied successfully
- Caution or prerequisite (25-50 words): What you need to have in place before attempting this
[INFO-GAIN: expert knowledge] This section MUST contain original insight from direct experience, proprietary data, or expert interviews. This is where the pillar page differentiates from competitors.
[INTERNAL-LINK] Link to advanced-level supporting articles or case studies.
Tools & Resources (200-300 words)
[ANSWER-FIRST] Start by naming the top 1-2 recommended tools before listing the full set.
Structure:
- Organize tools into 2-3 categories (e.g., "Free Tools," "Premium Tools," "Learning Resources")
- For each tool, include:
- Tool name (linked if appropriate)
- One-line description of what it does
- Best for: Who should use this tool
- Price: Free, freemium, or pricing tier
[INFO-GAIN: personal experience] Note which tools you have personally used and your honest assessment.
[INTERNAL-LINK] Link to any dedicated tool reviews or comparison articles in the cluster.
Getting Started (150-200 words)
[ANSWER-FIRST] Give the reader their very first action step in the opening sentence. Remove all friction to starting.
Structure:
- Step 1 (2-3 sentences): The lowest-friction first action - what can someone do in the next 5 minutes?
- Step 2 (2-3 sentences): The next logical step that builds on Step 1
- Step 3 (2-3 sentences): A step that creates momentum and leads to ongoing engagement
- Encouragement (1 sentence): Address the most common hesitation and counter it
[INTERNAL-LINK] Link each step to relevant supporting articles or tool guides that provide detailed walkthroughs.
FAQ (5-7 questions)
[FAQ] Each Q&A pair should be structured for featured snippet eligibility. Use the <details> pattern or H3 headings.
Guidelines for FAQ questions:
- Source questions from People Also Ask, forums, and comment sections
- Each answer should be 40-80 words - concise and direct
- The first sentence of each answer should be a standalone answer (featured snippet format)
- Include [STAT: supporting statistic] in at least 2 answers
- Cover a range: basic definitions, practical how-tos, comparisons, and cost/time questions
### [Question 1 - basic definition or "what is" question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] [STAT: relevant statistic if applicable.]
### [Question 2 - "how to" or process question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]
### [Question 3 - comparison or "vs" question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]
### [Question 4 - cost, time, or effort question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] [STAT: relevant statistic if applicable.]
### [Question 5 - common misconception or "is it worth" question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]
### [Question 6 - advanced or edge-case question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]
### [Question 7 - future-looking or trend question]?
[ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.]
[INTERNAL-LINK] Link FAQ answers to relevant supporting articles where the reader can learn more.
Conclusion with Internal Link Hub (150-200 words)
[ANSWER-FIRST] Restate the single most important takeaway from the guide in the opening sentence.
Structure:
- Key takeaway (1-2 sentences): The single most important thing to remember
- Brief recap (2-3 sentences): Summarize the guide's main points without repeating section headings verbatim
- Forward-looking statement (1-2 sentences): How this topic is evolving and why staying current matters
- Call to action (1 sentence): What should the reader do next?
Internal Link Hub: List all supporting articles in the topic cluster, organized by category:
### Continue Learning
**Fundamentals:**
- [INTERNAL-LINK] [Supporting Article 1 Title]
- [INTERNAL-LINK] [Supporting Article 2 Title]
**How-To Guides:**
- [INTERNAL-LINK] [Supporting Article 3 Title]
- [INTERNAL-LINK] [Supporting Article 4 Title]
**Advanced:**
- [INTERNAL-LINK] [Supporting Article 5 Title]
- [INTERNAL-LINK] [Supporting Article 6 Title]
**Tools & Reviews:**
- [INTERNAL-LINK] [Supporting Article 7 Title]
- [INTERNAL-LINK] [Supporting Article 8 Title]
Pre-Publish Checklist
- Total word count is 3,000-4,000 words
- All [ANSWER-FIRST] prompts have been fulfilled - every section leads with the answer
- All [STAT] markers replaced with real, cited statistics (with source and year)
- All [VISUAL] markers replaced with actual charts or diagrams
- All [IMAGE] markers replaced with relevant, optimized images with alt text
- All [INFO-GAIN] markers replaced with original data, experience, or insight
- All [INTERNAL-LINK] zones populated with real links to supporting articles
- All [FAQ] answers are concise (40-80 words) and lead with a direct answer
- Table of Contents links are functional
- Meta title is under 60 characters and includes primary keyword
- Meta description is 150-160 characters with primary keyword and CTA
- At least 6 supporting articles exist (or are planned) for the internal link hub
- Content has been reviewed for E-E-A-T signals (experience, expertise, authority, trust)
| 1 | # Template: Pillar Page |
| 2 | |
| 3 | **Description:** Comprehensive topic authority guide that serves as the central hub for a topic cluster. Pillar pages provide broad, thorough coverage of a subject and link out to supporting articles that dive deeper into sub-topics. |
| 4 | |
| 5 | **Target Word Count:** 3,000-4,000 words |
| 6 | |
| 7 | |
| 8 | |
| 9 | ## When to Use This Template |
| 10 | |
| 11 | **Content Goal:** Establish topical authority and create an SEO hub that ranks for high-volume head terms |
| 12 | **Search Intent:** Informational (users want a complete understanding of a topic) |
| 13 | **Funnel Stage:** Top-of-funnel awareness and mid-funnel education |
| 14 | **Use When:** |
| 15 | Targeting a broad, competitive keyword with high search volume |
| 16 | You have (or plan to create) 5+ supporting articles on sub-topics |
| 17 | The topic is complex enough to warrant 3,000+ words of coverage |
| 18 | You want to build a content cluster architecture around this topic |
| 19 | |
| 20 | |
| 21 | |
| 22 | ## Section-by-Section Structure |
| 23 | |
| 24 | |
| 25 | |
| 26 | ### Title |
| 27 | |
| 28 | **Format:** "The Complete Guide to [Topic] in [Year]" |
| 29 | |
| 30 | **Guidelines:** |
| 31 | Include primary keyword naturally |
| 32 | The year signals freshness and improves CTR |
| 33 | Keep under 60 characters for full SERP display |
| 34 | |
| 35 | |
| 36 | # The Complete Guide to [Topic] in [Year] |
| 37 | |
| 38 | |
| 39 | [IMAGE] Hero image that visually represents the topic. Use a custom graphic or high-quality photo - not a generic stock image. Alt text should include the primary keyword. |
| 40 | |
| 41 | |
| 42 | |
| 43 | ### TL;DR Box (40-60 words) |
| 44 | |
| 45 | [ANSWER-FIRST] Provide a concise summary that directly answers the searcher's core question. A reader should be able to stop here and walk away informed. This box improves dwell time by immediately delivering value and earns featured snippet potential. |
| 46 | |
| 47 | |
| 48 | > **TL;DR:** [One to two sentences defining the topic and its importance.] [One sentence on the key takeaway or most surprising finding.] [One sentence on what action to take.] [STAT: key statistic that grounds the summary] |
| 49 | |
| 50 | |
| 51 | |
| 52 | |
| 53 | ### Table of Contents |
| 54 | |
| 55 | Auto-generated from H2 headings. Use anchor links for jump navigation. This improves UX on long-form content and can generate sitelinks in SERPs. |
| 56 | |
| 57 | |
| 58 | ## Table of Contents |
| 59 | |
| 60 | - [What Is [Topic]?](#what-is-topic) |
| 61 | - [Why [Topic] Matters](#why-topic-matters) |
| 62 | - [Core Section 1](#core-section-1) |
| 63 | - [Core Section 2](#core-section-2) |
| 64 | - [Core Section 3](#core-section-3) |
| 65 | - [Core Section 4](#core-section-4) |
| 66 | - [Core Section 5](#core-section-5) |
| 67 | - [Core Section 6](#core-section-6) |
| 68 | - [Advanced: [Expert-Level Sub-topic]](#advanced-expert-level-sub-topic) |
| 69 | - [Tools & Resources](#tools-resources) |
| 70 | - [Getting Started](#getting-started) |
| 71 | - [FAQ](#faq) |
| 72 | |
| 73 | |
| 74 | |
| 75 | |
| 76 | ### Introduction (200-300 words) |
| 77 | |
| 78 | [ANSWER-FIRST] Open with a clear, direct statement about what [Topic] is and why it matters right now. Do not bury the lead with backstory or fluff. |
| 79 | |
| 80 | **Structure:** |
| 81 | **Opening hook** (1-2 sentences): Lead with a compelling statistic or trend that creates urgency |
| 82 | [STAT: current year statistic showing the scale or growth of this topic] |
| 83 | **Topic overview** (2-3 sentences): Define the topic clearly for someone encountering it for the first time |
| 84 | **Relevance statement** (1-2 sentences): Why this matters right now - what has changed recently? |
| 85 | **What the reader will learn** (2-3 sentences): Preview the guide's coverage - set expectations so the reader commits to reading |
| 86 | **Credibility indicator** (1 sentence): Why should the reader trust this guide? (experience, data sources, methodology) |
| 87 | |
| 88 | [INFO-GAIN: personal experience] Include a brief mention of your direct experience or research that qualifies this guide. |
| 89 | |
| 90 | [INTERNAL-LINK] If you have a related "Why [Topic] Matters" article, link it from the relevance statement. |
| 91 | |
| 92 | |
| 93 | |
| 94 | ### What Is [Topic]? (200-300 words) |
| 95 | |
| 96 | [ANSWER-FIRST] Start with a one-sentence definition that could serve as a featured snippet. Keep it jargon-free for accessibility. |
| 97 | |
| 98 | **Structure:** |
| 99 | **Clear definition** (1-2 sentences): Simple, authoritative definition of the topic |
| 100 | **Context and scope** (2-3 sentences): Where this fits in the broader landscape - what category does it belong to? |
| 101 | **Key components** (3-5 bullet points): Break the topic into its essential parts or characteristics |
| 102 | **Common misconceptions** (1-2 sentences): Address what this topic is NOT to prevent confusion |
| 103 | **Brief history or evolution** (2-3 sentences): How the topic has developed to its current state |
| 104 | |
| 105 | [VISUAL: chart-type] Include a diagram or infographic showing the key components and how they relate to each other. Suggested: labeled diagram, flowchart, or concept map. |
| 106 | |
| 107 | [STAT: definition-supporting data point] Include at least one data point that contextualizes the topic's scope or importance. |
| 108 | |
| 109 | [INTERNAL-LINK] Link key terms to their own dedicated articles if they exist in the cluster. |
| 110 | |
| 111 | |
| 112 | |
| 113 | ### Why [Topic] Matters (200-300 words) |
| 114 | |
| 115 | [ANSWER-FIRST] Lead with the single most compelling reason this topic deserves attention. Quantify the impact wherever possible. |
| 116 | |
| 117 | **Structure:** |
| 118 | **Primary impact statement** (1-2 sentences): The most important reason backed by data |
| 119 | [STAT: impact or ROI statistic] |
| 120 | **Industry trends** (2-3 sentences): Market data showing growth, adoption, or shifting priorities |
| 121 | [STAT: trend or growth statistic] |
| 122 | **Consequences of ignoring** (2-3 sentences): What happens if you do not engage with this topic? |
| 123 | **Opportunity framing** (2-3 sentences): What is possible if you get this right? |
| 124 | **Who this affects** (1-2 sentences): Specific roles, industries, or use cases |
| 125 | |
| 126 | [VISUAL: chart-type] Bar chart or line graph showing growth trend, adoption curve, or impact data over time. |
| 127 | |
| 128 | [INFO-GAIN: unique analysis] Include a data point or trend observation that is not commonly cited - something from your own research or analysis. |
| 129 | |
| 130 | [INTERNAL-LINK] Link to case studies or data-driven articles that expand on the impact claims. |
| 131 | |
| 132 | |
| 133 | |
| 134 | ### Core Sections (6-8 H2s, 300-400 words each) |
| 135 | |
| 136 | Each core section covers a major sub-topic within the pillar. These sections should be comprehensive enough to stand alone but concise enough that a dedicated supporting article can go deeper. |
| 137 | |
| 138 | **For each core section, use this structure:** |
| 139 | |
| 140 | |
| 141 | ## [Sub-topic as H2 - written as a clear, keyword-rich heading] |
| 142 | |
| 143 | |
| 144 | [ANSWER-FIRST] Open with a 1-2 sentence answer or definition of this sub-topic before elaborating. |
| 145 | |
| 146 | **Structure per section:** |
| 147 | **Direct answer or definition** (1-2 sentences): What is this sub-topic and why does it matter within the broader topic? |
| 148 | **Key principles or steps** (150-200 words): The essential knowledge, broken into: |
| 149 | Numbered steps (for processes) |
| 150 | Bullet points (for principles or characteristics) |
| 151 | Sub-headings H3 (for complex sub-topics) |
| 152 | **Example or evidence** (50-100 words): A specific, concrete example that illustrates the concept |
| 153 | [INFO-GAIN: real-world example] Use a first-hand example, case study, or original observation when possible |
| 154 | **Common mistakes or pitfalls** (50-75 words): What do people get wrong about this sub-topic? |
| 155 | **Transition to deeper content** (1-2 sentences): Bridge to the next section or to a supporting article |
| 156 | |
| 157 | [STAT: sub-topic-specific statistic] Include at least one data point per core section. |
| 158 | |
| 159 | [IMAGE] Where applicable, include screenshots, process diagrams, or example visuals that support the explanation. |
| 160 | |
| 161 | [INTERNAL-LINK] Link to the dedicated supporting article for this sub-topic. Use contextual anchor text (not "click here" or "read more"). |
| 162 | |
| 163 | **Repeat this structure for each of the 6-8 core sections.** |
| 164 | |
| 165 | |
| 166 | |
| 167 | ### Advanced: [Expert-Level Sub-topic] (200-300 words) |
| 168 | |
| 169 | [ANSWER-FIRST] Signal immediately that this section is for experienced practitioners, then deliver an advanced insight they will not find in beginner guides. |
| 170 | |
| 171 | **Structure:** |
| 172 | **Audience gate** (1 sentence): "If you're already [doing X], here's how to [achieve Y]." |
| 173 | **Advanced insight** (100-150 words): A technique, framework, or perspective that goes beyond standard advice |
| 174 | **Evidence or application** (50-75 words): Where this has been applied successfully |
| 175 | **Caution or prerequisite** (25-50 words): What you need to have in place before attempting this |
| 176 | |
| 177 | [INFO-GAIN: expert knowledge] This section MUST contain original insight from direct experience, proprietary data, or expert interviews. This is where the pillar page differentiates from competitors. |
| 178 | |
| 179 | [INTERNAL-LINK] Link to advanced-level supporting articles or case studies. |
| 180 | |
| 181 | |
| 182 | |
| 183 | ### Tools & Resources (200-300 words) |
| 184 | |
| 185 | [ANSWER-FIRST] Start by naming the top 1-2 recommended tools before listing the full set. |
| 186 | |
| 187 | **Structure:** |
| 188 | Organize tools into 2-3 categories (e.g., "Free Tools," "Premium Tools," "Learning Resources") |
| 189 | For each tool, include: |
| 190 | **Tool name** (linked if appropriate) |
| 191 | **One-line description** of what it does |
| 192 | **Best for:** Who should use this tool |
| 193 | **Price:** Free, freemium, or pricing tier |
| 194 | |
| 195 | [INFO-GAIN: personal experience] Note which tools you have personally used and your honest assessment. |
| 196 | |
| 197 | [INTERNAL-LINK] Link to any dedicated tool reviews or comparison articles in the cluster. |
| 198 | |
| 199 | |
| 200 | |
| 201 | ### Getting Started (150-200 words) |
| 202 | |
| 203 | [ANSWER-FIRST] Give the reader their very first action step in the opening sentence. Remove all friction to starting. |
| 204 | |
| 205 | **Structure:** |
| 206 | **Step 1** (2-3 sentences): The lowest-friction first action - what can someone do in the next 5 minutes? |
| 207 | **Step 2** (2-3 sentences): The next logical step that builds on Step 1 |
| 208 | **Step 3** (2-3 sentences): A step that creates momentum and leads to ongoing engagement |
| 209 | **Encouragement** (1 sentence): Address the most common hesitation and counter it |
| 210 | |
| 211 | [INTERNAL-LINK] Link each step to relevant supporting articles or tool guides that provide detailed walkthroughs. |
| 212 | |
| 213 | |
| 214 | |
| 215 | ### FAQ (5-7 questions) |
| 216 | |
| 217 | [FAQ] Each Q&A pair should be structured for featured snippet eligibility. Use the `<details>` pattern or H3 headings. |
| 218 | |
| 219 | **Guidelines for FAQ questions:** |
| 220 | Source questions from People Also Ask, forums, and comment sections |
| 221 | Each answer should be 40-80 words - concise and direct |
| 222 | The first sentence of each answer should be a standalone answer (featured snippet format) |
| 223 | Include [STAT: supporting statistic] in at least 2 answers |
| 224 | Cover a range: basic definitions, practical how-tos, comparisons, and cost/time questions |
| 225 | |
| 226 | |
| 227 | ### [Question 1 - basic definition or "what is" question]? |
| 228 | |
| 229 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] [STAT: relevant statistic if applicable.] |
| 230 | |
| 231 | ### [Question 2 - "how to" or process question]? |
| 232 | |
| 233 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] |
| 234 | |
| 235 | ### [Question 3 - comparison or "vs" question]? |
| 236 | |
| 237 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] |
| 238 | |
| 239 | ### [Question 4 - cost, time, or effort question]? |
| 240 | |
| 241 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] [STAT: relevant statistic if applicable.] |
| 242 | |
| 243 | ### [Question 5 - common misconception or "is it worth" question]? |
| 244 | |
| 245 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] |
| 246 | |
| 247 | ### [Question 6 - advanced or edge-case question]? |
| 248 | |
| 249 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] |
| 250 | |
| 251 | ### [Question 7 - future-looking or trend question]? |
| 252 | |
| 253 | [ANSWER-FIRST] [Direct 1-sentence answer.] [2-3 sentences of supporting detail.] |
| 254 | |
| 255 | |
| 256 | [INTERNAL-LINK] Link FAQ answers to relevant supporting articles where the reader can learn more. |
| 257 | |
| 258 | |
| 259 | |
| 260 | ### Conclusion with Internal Link Hub (150-200 words) |
| 261 | |
| 262 | [ANSWER-FIRST] Restate the single most important takeaway from the guide in the opening sentence. |
| 263 | |
| 264 | **Structure:** |
| 265 | **Key takeaway** (1-2 sentences): The single most important thing to remember |
| 266 | **Brief recap** (2-3 sentences): Summarize the guide's main points without repeating section headings verbatim |
| 267 | **Forward-looking statement** (1-2 sentences): How this topic is evolving and why staying current matters |
| 268 | **Call to action** (1 sentence): What should the reader do next? |
| 269 | |
| 270 | **Internal Link Hub:** |
| 271 | List all supporting articles in the topic cluster, organized by category: |
| 272 | |
| 273 | |
| 274 | ### Continue Learning |
| 275 | |
| 276 | **Fundamentals:** |
| 277 | - [INTERNAL-LINK] [Supporting Article 1 Title] |
| 278 | - [INTERNAL-LINK] [Supporting Article 2 Title] |
| 279 | |
| 280 | **How-To Guides:** |
| 281 | - [INTERNAL-LINK] [Supporting Article 3 Title] |
| 282 | - [INTERNAL-LINK] [Supporting Article 4 Title] |
| 283 | |
| 284 | **Advanced:** |
| 285 | - [INTERNAL-LINK] [Supporting Article 5 Title] |
| 286 | - [INTERNAL-LINK] [Supporting Article 6 Title] |
| 287 | |
| 288 | **Tools & Reviews:** |
| 289 | - [INTERNAL-LINK] [Supporting Article 7 Title] |
| 290 | - [INTERNAL-LINK] [Supporting Article 8 Title] |
| 291 | |
| 292 | |
| 293 | |
| 294 | |
| 295 | ## Pre-Publish Checklist |
| 296 | |
| 297 | [ ] Total word count is 3,000-4,000 words |
| 298 | [ ] All [ANSWER-FIRST] prompts have been fulfilled - every section leads with the answer |
| 299 | [ ] All [STAT] markers replaced with real, cited statistics (with source and year) |
| 300 | [ ] All [VISUAL] markers replaced with actual charts or diagrams |
| 301 | [ ] All [IMAGE] markers replaced with relevant, optimized images with alt text |
| 302 | [ ] All [INFO-GAIN] markers replaced with original data, experience, or insight |
| 303 | [ ] All [INTERNAL-LINK] zones populated with real links to supporting articles |
| 304 | [ ] All [FAQ] answers are concise (40-80 words) and lead with a direct answer |
| 305 | [ ] Table of Contents links are functional |
| 306 | [ ] Meta title is under 60 characters and includes primary keyword |
| 307 | [ ] Meta description is 150-160 characters with primary keyword and CTA |
| 308 | [ ] At least 6 supporting articles exist (or are planned) for the internal link hub |
| 309 | [ ] Content has been reviewed for E-E-A-T signals (experience, expertise, authority, trust) |
| 310 |
Details
- Updated
- Sep 18, 2026
- License
- MIT
- Stars on the repo
- ★ 2,219
- Checked
- Source
- AgriciDaniel/claude-blog ↗
- Creator
- AgriciDaniel · 129 listings
Similar skills
See all →
SkillContent Calendar Planner
SkillFacebook Content Planner
AgentContent Outline Planner
AgentContent Engine Architect
SkillSemantic Topic Clustering
SkillGSC Content PlannerMore from AgriciDaniel
SkillAgent Browsing Auditor
SkillAI Search Optimization
SkillBacklink Profile Analysis
SkillAmazon Ads Auditor
SkillApple Search Ads Auditor
SkillAttribution Auditor