Blog Post Outliner

---
name: blog-post-outliner
description: "Use when outlining blog posts. Headlines and structure."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [blog, writing, outlining, structure, content]
    related_skills: [blog-idea-generator, blog-seo-post-optimizer, blog-publishing-workflow]
---

# Blog Post Outliner

## Overview

A complete framework for structuring blog posts from headline to call-to-action. Covers headline formulas, intro frameworks, body structure (H2/H3 hierarchy), conclusion patterns, and formatting guidance. Consistently structured posts perform better in search, hold readers longer, and convert at higher rates.

## When to Use

- You have a topic but no outline yet
- You're co-writing and need a shared structural template
- You want to improve reader retention or conversion on existing posts
- You're reviewing a draft and need a structural checklist

## Headline Formulas

### 9 Proven Structures

| # | Formula | Pattern | Example |
|---|---------|---------|---------|
| 1 | **Listicle** | `[Number] [Adjective] [Topic] [for/that verbs]` | "17 Proven SEO Strategies for 2025" |
| 2 | **How-To** | `How to [Achieve Outcome] [without/with X constraint]` | "How to Rank #1 Without Building Backlinks" |
| 3 | **Question** | `[Question word] [aux] [reader] [action/belief?]` | "Why Is Your Blog Traffic Flat Despite 50+ Posts?" |
| 4 | **Controversial** | `Why [Common Belief] Is [Wrong/Dead/Misleading]` | "Why SEO Is Dead (And What Actually Works)" |
| 5 | **Ultimate Guide** | `The Ultimate Guide to [Topic] [in Year]` | "The Ultimate Guide to Technical SEO in 2025" |
| 6 | **Comparison** | `[X] vs [Y]: Which One Is Better for [Goal]?` | "Ahrefs vs Semrush: Which SEO Tool Is Right for You?" |
| 7 | **Curiosity Gap** | `[Uncommon observation] — [reveal outcome]` | "I Used AI for 30 Days. Here's What Happened." |
| 8 | **Benefit-First** | `[Achieve X] with [method/tool]` | "Cut Bounce Rate 40% with One Layout Change" |
| 9 | **Command/Imperative** | `[Verb] [direct object] [like/when/in context]` | "Stop Writing Boring Intros. Do This Instead." |

**Headline Tester Tools:**
- CoSchedule Headline Analyzer (emotional value, word balance)
- MonsterInsights Headline Analyzer (SEO + readability)
- Sharethrough Headline Optimizer (engagement prediction)

## Intro Frameworks

### The Hook→Problem→Solution→Preview (HPSP) Pattern

Every intro must answer: *Why should I keep reading?*

```
Paragraph 1 — HOOK
  Grab attention with: surprising stat, bold claim, relatable confession, or vivid question.
  "Did you know that 94% of blog posts never get a single external backlink?"

Paragraph 2 — PROBLEM
  Validate the reader's pain. Make them feel seen.
  "You've been writing consistently, publishing weekly, yet traffic stays flat..."

Paragraph 3 — SOLUTION (hinted)
  Tease the answer without giving it away.
  "The issue isn't your writing — it's your post structure. Here's what top-performing posts do differently."

Paragraph 4 — PREVIEW
  Set expectations: what they'll learn, how long it takes, what tools needed.
  "In this guide, you'll learn the 7-section framework behind our highest-traffic posts, with before/after examples."
```

### 5 Intro Hooks by Style

| Style | Example |
|-------|---------|
| **Stat/Data** | "Only 3% of B2B blogs generate 75% of total traffic. Here's what they do differently." |
| **Story/Anecdote** | "Two years ago, I published a post that flopped. Then I changed one thing." |
| **Question** | "What if everything you've been told about backlinks is wrong?" |
| **Bold Claim** | "The headline is more important than the post itself." |
| **Relatable Frustration** | "You spent three hours writing this post. Nobody read it." |

## Body Structure (H2 / H3 Hierarchy)

### Standard Deep-Dive Outline

```
H1: [Headline]
  H2: [Main Section 1 — The What/Why]
    H3: Sub-point 1
    H3: Sub-point 2
    H3: Pro tip / Example
  H2: [Main Section 2 — The How]
    H3: Step-by-step breakdown
      Bullet list of sub-steps
    H3: Common mistake to avoid
    H3: Expert counterpoint (if applicable)
  H2: [Main Section 3 — Real Examples / Case Study]
    H3: Example A
    H3: Example B
  H2: [Main Section 4 — Tools / Resources / Templates]
  H2: [Main Section 5 — Advanced Tips]
  H2: [FAQ — People Also Ask answers]
```

### Formatting Rules

- **One idea per H2.** If you need more than 3 H3s under an H2, consider splitting into a new H2.
- **H3s are optional** for short sections (300 words or fewer).
- **Paragraphs max 3–4 lines** on desktop, 2–3 on mobile.
- **Use ordered lists** for sequential steps, **unordered lists** for features/reasons.
- **One sentence per list item** if possible — if items need explanation, make them H3s.
- **Bold key phrases** that skimmers would catch.
- **Add a table** when comparing 2+ items across 2+ dimensions (readers love tables).
- **Blockquote** expert insights, reader comments, or key takeaways.
- **Add an image/video** every ~400 words to break up text.

### Length Guidelines by Content Type

| Type | Target Words | H2 Count | Avg Reading Time |
|------|-------------|----------|------------------|
| List post | 1,500–2,500 | 5–10 | 7–12 min |
| How-to guide | 2,000–4,000 | 6–12 | 10–20 min |
| Pillar page | 4,000–8,000 | 10–20 | 20–40 min |
| News/opinion | 800–1,200 | 3–5 | 4–6 min |
| Comparison | 2,000–3,500 | 5–8 | 10–17 min |
| Case study | 2,500–5,000 | 6–10 | 13–25 min |

## Conclusion Patterns

Pick one pattern based on post type:

### 1. Summary → Insight → CTA (Default)
```
SUMMARY: "You've learned the 5-step framework..."
INSIGHT: "The real key isn't the steps — it's consistency."
CTA: "Download the checklist to track your progress."
```

### 2. Cliffhanger → Next → Subscribe (Series posts)
```
CLIFFHANGER: "But there's one problem with this approach that we haven't addressed..."
NEXT: "In Part 2, we'll tackle..."
SUBSCRIBE: "Get notified when it drops — join 5K subscribers."
```

### 3. Comparison → Verdict → Offer (Review/Affiliate posts)
```
COMPARISON: "Tool A wins on features, Tool B wins on price."
VERDICT: "If you're a solo creator, go with B. For agencies, A."
OFFER: "Get 20% off Tool A with this link."
```

### 4. Stance → Prediction → Invite (Opinion posts)
```
STANCE: "I believe generative AI won't replace writers."
PREDICTION: "In 5 years, the best writers will be the best prompt engineers."
INVITE: "Agree or disagree? Let me know in the comments."
```

### CTA Formats
```markdown
- **[Soft]** "What would you add? Drop it in the comments."
- **[Medium]** "Subscribe to get next week's deep-dive."
- **[Hard]** "Start your free trial and implement this today."
- **[Social]** "Share this with a teammate who needs to see it."
- **[Lead gen]** "Download the free PDF checklist."
```

## Formatting Guidance

### Visual Break Pattern
```
Text → Image/Diagram → Text → Pull quote → Text → Bullet list → Text → H2
```

### SEO-Ready Formatting Checklist
- [ ] H1 = exact target keyword or close variant
- [ ] H2s include 2–3 secondary keywords naturally
- [ ] First 100 words contain primary keyword
- [ ] At least one image has keyword-rich alt text
- [ ] FAQ H2 section targets People Also Ask terms
- [ ] Internal links to 2–3 related posts
- [ ] External link to one authority source
- [ ] Meta description drafted (under 160 chars)

## Common Pitfalls

- **No scannable elements:** Walls of text cause 80%+ bounce rates
- **Headline mismatch:** If the headline promises "10 tools" but the post covers 5, readers leave
- **Missing a clear H2 structure:** Google uses H2s for featured snippets — no structure means no snippet
- **CTA overdose:** More than one CTA per 1,000 words dilutes action
- **Intro too long:** If the reader hasn't reached the first H2 within 5 seconds of skimming, you've lost them
- **Weak transitions:** Each H2 should flow into the next — use bridging sentences between sections
- **Zero proof points:** Claims without data, stats, or examples erode trust

## Verification Checklist

- [ ] Headline uses a proven formula from the list above
- [ ] Intro follows HPSP framework (hook → problem → solution → preview)
- [ ] H2 count matches content type guidelines
- [ ] Every H2 has at least 2–3 supporting sentences (no empty headings)
- [ ] Paragraphs kept under 4 lines
- [ ] At least one table, list, or pull quote per 500 words
- [ ] Conclusion has summary + CTA
- [ ] Formatting checklist completed (keyword placement, links, alt text)
- [ ] Estimated reading time added (near headline or in metadata)
- [ ] Outline shared with a reviewer before drafting begins