blog-post-structure
This skill should be used when the user asks to "structure a blog post", "write a B2B blog post", "format a blog article", "outline a blog post", "design blog post structure", "blog post template", "how to write a SaaS blog post", "blog post formatting", or any variation of structuring, formatting, or outlining blog posts for B2B SaaS content marketing.
Blog Post Structure
A B2B SaaS blog post is a structured argument that educates a specific reader about a specific problem. It is not a personal essay, a press release, or a keyword-stuffed article. Every structural element exists to serve the reader and earn the ranking.
Most blog posts fail because they lack structure — they're rambling prose with no clear thesis, no scannable elements, and no next step. This skill defines the structural rules that separate rankable, shareable B2B posts from forgettable ones.
The Blog Post Skeleton
Every B2B SaaS blog post follows this skeleton. Customize content, never skip structural elements.
| Section | Purpose | Length |
|---|---|---|
| Title | Promise a specific outcome. Match the search query | 6-12 words |
| Meta description | Summarize the value prop. Earn the click from SERP | 1-2 sentences, ≤ 155 characters |
| Hook (first 2-3 sentences) | Answer the core question or state the thesis. Earn the read | 30-50 words |
| Context / why it matters | Why this topic matters now, for this audience | 1-2 short paragraphs |
| Body (3-7 sections with H2s) | The substance. Each section covers one subtopic | 200-500 words per section |
| Conclusion / what to do next | Summary + actionable next step | 2-3 sentences + CTA |
Target length: 1,200-2,500 words. Under 1,200 is usually too thin to rank. Over 2,500 signals the topic should be split into multiple posts or converted to a guide.
Title Rules
| Rule | Bad | Good |
|---|---|---|
| Match the search query | "Unleashing the Power of Data-Driven Decisions" | "How to Build a Sales Forecasting Model (Step-by-Step)" |
| Promise a specific outcome | "Thoughts on Lead Scoring" | "Lead Scoring for SaaS: The 5 Signals That Actually Predict Conversion" |
| Use numbers when applicable | "Ways to Improve Cold Email" | "7 Cold Email Mistakes That Kill Reply Rates" |
| No clickbait | "You Won't Believe What Happened When We Changed Our CRM" | "We Switched from Salesforce to HubSpot. Here's What Changed." |
| ≤ 60 characters for SEO display | "A Comprehensive Guide to Understanding and Implementing Account-Based Marketing Strategies for B2B SaaS Companies" | "ABM for SaaS: The Complete Playbook" |
Hook Rules (First 50 Words)
The first 2-3 sentences determine whether the reader continues or bounces. They also determine whether AI engines cite you.
The 3 hook types that work for B2B:
| Hook type | Structure | Example |
|---|---|---|
| Direct answer | Answer the post's core question immediately | "The ideal cold email sequence is 3 emails over 9 days. Here's exactly how to structure each one." |
| Contrarian | Challenge a common belief | "Most lead scoring models are broken. They weight job title over buying behavior — and it costs pipeline." |
| Data point | Lead with a specific, surprising number | "67% of B2B buyers use AI search before Google when evaluating vendors. Here's what that means for your content strategy." |
Never open with:
- "In today's fast-paced business environment..."
- "Have you ever wondered..."
- A dictionary definition
- A rhetorical question
- Your company history
Body Structure
H2 rules
- Every section gets an H2. No sections without headers
- H2s should be question-shaped when possible: "How does lead scoring work?", "What are the best CRM tools?"
- H2s must be descriptive enough to understand the section's content without reading it
- Aim for 3-7 H2 sections per post. Fewer than 3 means the topic is too narrow. More than 7 means the post should be split
H3 rules
- Use H3s to break up long sections (300+ words)
- H3s can be declarative: "Score decay rules", "Implementation timeline"
- Don't go deeper than H3. H4+ creates visual complexity without adding structure
Paragraph rules
- 2-4 sentences per paragraph. Never more than 5
- One idea per paragraph
- First sentence of each paragraph is the key claim (inverted pyramid)
- Short paragraphs are more readable on screens
Content elements
Vary content elements to keep the post scannable. A post that is 100% prose fails. Mix in:
| Element | When to use | Frequency |
|---|---|---|
| Tables | Comparing options, presenting criteria, showing data | At least 1 per post |
| Bullet / numbered lists | Steps, features, rules, examples | At least 2 per post |
| Pull quotes or callout boxes | Key stats, important rules, one-line takeaways | 1-2 per post |
| Code blocks / examples | Technical content, configuration, templates | As needed |
| Images / screenshots | UI walkthroughs, data visualizations | 1-3 per post |
Writing style
| Do | Don't |
|---|---|
| Short sentences (12-20 words average) | Long compound sentences with multiple clauses |
| Active voice ("SDRs should call within 5 minutes") | Passive voice ("Calls should be made within 5 minutes") |
| Specific claims with numbers | Vague claims ("many companies", "significant improvement") |
| Imperative form ("Set the threshold at 50 points") | Hedged suggestions ("You might want to consider setting...") |
| Second person ("you") or first-person plural ("we") | Third-person academic ("One might observe that...") |
CTA Design
Every post ends with a next step. The CTA type depends on the post's funnel stage.
| Post type (funnel stage) | CTA | Format |
|---|---|---|
| TOFU (educational) | Related guide, newsletter, template | "Download the [framework] template" or "Get the weekly newsletter" |
| MOFU (evaluative) | Comparison page, demo, trial | "See how [product] compares" or "Start a free trial" |
| BOFU (decision) | Demo, case study, pricing | "Book a 15-minute demo" or "See pricing" |
CTA rules:
- One primary CTA per post. Not 3 different asks
- Place at the end of the post. Mid-post CTAs interrupt reading flow unless the post is 2,000+ words
- For long posts (2,000+), add one mid-post CTA (usually a related content link) and one end-of-post CTA
- Match CTA to reader intent. TOFU readers aren't ready for "Book a demo." BOFU readers don't need "Subscribe to our newsletter"
SEO + AEO Formatting
| Element | SEO purpose | AEO purpose |
|---|---|---|
| Title tag | Matches search query for ranking | Not used by AI engines |
| Meta description | Earns click from SERP | Not used by AI engines |
| H2s | Structure for crawling and indexing | Extraction anchors — AI engines locate sections via headers |
| First 50 words | Not directly weighted by Google | Heavily weighted — AI engines extract the opening |
| Tables | No direct ranking benefit | High extraction priority — AI engines parse tables well |
| FAQ section | Eligible for PAA rich results | FAQPage schema drives AI extraction |
| Internal links | Link equity distribution | Minor — helps crawling |
For maximum impact, optimize for both. Write the first 50 words for AEO (direct answer). Write the title tag for SEO (keyword match). Add FAQ section with schema for both.
Pre-Publish Checklist
- [ ] Title matches target search query and is ≤ 60 characters
- [ ] First 50 words contain a direct answer or strong thesis
- [ ] 3-7 H2 sections with descriptive, question-shaped headers
- [ ] At least 1 table and 2 lists in the post
- [ ] Every paragraph is ≤ 4 sentences
- [ ] No filler intros ("In today's...", "Have you ever...")
- [ ] Specific claims include numbers, names, or data
- [ ] One clear CTA matched to the post's funnel stage
- [ ] Internal links to 3-5 related pages
- [ ] FAQ section added with FAQPage schema (for AEO)
- [ ] Meta description written (≤ 155 characters)
- [ ] Author byline with real name and bio
- [ ]
datePublishedanddateModifiedin Article schema
Anti-Pattern Check
- Post opens with "In today's rapidly evolving landscape..." → Cut. Start with the answer or a specific data point. AI engines skip filler intros and readers bounce
- 2,000 words of unbroken prose → Add tables, lists, H2s, and callout boxes. A post with no visual variety loses readers at paragraph 3
- H2s are clever instead of descriptive → "The Secret Sauce" tells readers nothing. "How to Set Up Lead Scoring in HubSpot" tells them exactly what the section covers. AI engines need descriptive headers
- No CTA or 5 different CTAs → One CTA matched to funnel stage. A TOFU post with "Book a demo" pushes too hard. A BOFU post with "Subscribe to our blog" is a missed conversion
- Post is 4,000 words → Split it. Long-form guides are their own content type. Blog posts should be 1,200-2,500 words focused on one topic. If it's longer, it's trying to cover too much
- Same structure as every competitor's post → Differentiate through structure. If everyone writes listicles, write a framework post. If everyone writes how-tos, lead with contrarian data. Same structure = same outcome
Want agents that use skill files like this?
We customize skill files for your brand voice and methodology, then run content agents against them.
Book a call