# Content Types Overview

Quick-reference index covering all 23 content-type templates. Use this file to pick the right content type for a SERP, check its target word count, dominant schema, snippet format, and H1/H2 skeleton without loading the full per-type file. Load the individual `content-types/<type>.md` only when you need the depth (process detail, anti-AI focus, common mistakes, example topics).

## Decision table

| Content type | Dominant intent | Word count | Primary schema | Snippet format | H1 pattern | Key H2s (first 3-4) |
|---|---|---|---|---|---|---|
| how-to | Informational | 1,500-3,000 | HowTo + FAQ | Ordered list | "How to [Action] [Qualifier]" | Quick answer / Prerequisites / Step-by-step / Common mistakes |
| definition | Informational | 1,000-2,000 | DefinedTerm + FAQ | Paragraph | "What Is [Term]? [Subtitle]" | Quick definition / How it works / Types / Benefits |
| pillar-page | Informational + navigational | 3,000-5,000+ | Article + FAQ | Paragraph (list per section) | "The Complete Guide to [Topic] [Year]" | Table of contents / Overview / Core subtopics / Practical steps |
| faq-page | Informational | 1,500-2,500 | FAQPage + BreadcrumbList | Paragraph (per Q) | "[Topic] FAQ: Veelgestelde vragen over [topic]" | Intro / Category 1 / Category 2 / Costs |
| statistics | Informational | 2,000-3,500 | Article + Dataset | List | "[Topic] Statistics [Year]: [X] Key Facts and Trends" | Key highlights / Category stats / Regional data / Trends |
| news | Informational + navigational | 800-1,500 | NewsArticle + FAQ | Paragraph | "[News event]: [Impact or what it means]" | Key takeaways / What happened / Why it matters / What to expect |
| thought-leadership | Informational | 1,200-2,500 | Article + Person | Paragraph (low priority) | "[Strong opinion or provocative question]" | Conventional wisdom / Why it's wrong / Supporting arguments / Counterarguments |
| glossary | Informational | 5,000-15,000 (200-400/term) | DefinedTermSet + BreadcrumbList | Paragraph (per term) | "[Industry] Woordenlijst: [X] Begrippen Uitgelegd" | Intro / A / B / C ... |
| comparison | Commercial investigation | 1,200-2,500 | FAQ + Product | Table | "[Product A] vs [Product B]: [Outcome promise]" | Quick verdict / At-a-glance table / How we compared / Head-to-head |
| listicle | Commercial investigation | 2,000-4,000 | ItemList + FAQ | List | "Best [Category] for [Audience/Use Case] in [Year]" | Top picks at a glance / How we evaluated / 1. Top pick / 2. Second pick |
| alternatives | Commercial investigation | 1,500-3,000 | ItemList + FAQ | List | "[X] Alternatieven: [N] Beste Opties in [Year]" | Why look for alternatives / Comparison table / Alternative 1 / Alternative 2 |
| product-review | Commercial investigation | 1,500-2,500 | Review + Product | Paragraph | "[Product] Review [Year]: [Honest verdict]" | Quick verdict / What is [Product] / Our experience / Pros |
| buying-guide | Commercial investigation | 2,000-3,500 | Article + FAQ | List | "[Category] Kopen: Waar Moet Je Op Letten?" | Quick checklist / Criterion 1 / Criterion 2 / Budget guide |
| product-page | Transactional | 1,000-1,500 | Product + Offer + AggregateRating | Product rich result | "[Product Name] — [Key Differentiator]" | Description / Features and specs / What's included / Who is this for |
| category-page | Commercial + navigational | 300-1,000 (editorial) | CollectionPage + ItemList | List | "[Category Name]" | Intro / Product grid / Koopgids / Subcategories |
| landing-page | Transactional | 800-1,200 | WebPage or Service + FAQ | Not primary | "[Clear value proposition in one line]" | Problem statement / Solution / How it works / Social proof |
| pricing-page | Transactional | 500-1,500 | Product + Offer | Table | "Prijzen" or "[Product] Pricing" | Pricing tiers / Feature comparison table / Which plan / What's included |
| integration-page | Commercial + navigational | 800-1,500 | SoftwareApplication + HowTo | List | "[Your Product] + [Partner Tool] Integratie" | What it does / Key features / How to set it up / Use cases |
| service-page | Commercial + transactional | 1,200-2,000 | Service + LocalBusiness + FAQ | List | "[Service Name] — [Key Benefit or Location]" | What we do / Who this is for / How it works / Deliverables |
| location-page | Local + transactional | 1,200-1,500 | LocalBusiness + Service + FAQ | Paragraph | "[Service] in [Location]" | Local context / Services in [Location] / Why choose us / Recent projects |
| case-study | Commercial investigation | 1,500-2,500 | Article + Organization | Paragraph | "[Client/Industry]: [Key Result in Numbers]" | Overview / The challenge / Our approach / The results |
| about-page | Navigational + trust | 500-1,500 | Organization + Person | Knowledge Panel (not snippet) | "Over [Brand]" or "About [Brand]" | Mission / Our story / Our team / Expertise |
| programmatic-page | Informational + commercial | 500-1,200 | Depends on type + BreadcrumbList | Table | "[Variable A] [Connector] [Variable B]" | Data summary / Key data / How [B] compares / Trends over time |

## Intent → content type mapping

Search intent is the primary filter. Pick based on what the top 5 SERP results are actually doing, not what you think they should be doing.

**Informational.** User wants to understand something. Not buying yet.
- "how to [x]" / "[x] tutorial" → how-to
- "what is [x]" / "[x] meaning" → definition
- "[topic] explained" / "guide to [topic]" → pillar-page
- "[topic] questions" / PAA cluster → faq-page
- "[topic] statistics" / "[topic] data [year]" → statistics
- "[term] vocabulary" / 30+ terms in niche → glossary
- "[event] [year]" / breaking topic → news
- "why [industry belief]" / contrarian query → thought-leadership

**Commercial investigation.** User is shopping but hasn't picked a product.
- "best [category] for [audience]" → listicle
- "[A] vs [B]" → comparison
- "[product] alternatives" → alternatives
- "[product] review" → product-review
- "[category] buying guide" / "what to look for in [x]" → buying-guide
- "[service] results" / "[industry] case study" → case-study

**Transactional.** User is ready to convert.
- "[product name]" / "[product] kopen" → product-page
- "[product] pricing" / "[product] kosten" → pricing-page
- "[service] aanvragen" / "[tool] free trial" → landing-page
- "[service] inhuren" / "[service] kosten" → service-page
- "[tool A] + [tool B] integration" → integration-page
- "[service] in [city]" / "[service] near me" → location-page

**Navigational + trust.** User is verifying who you are.
- "[brand] about" / "who is behind [brand]" → about-page
- "[category]" root browse → category-page
- Long-tail pattern at scale with structured data → programmatic-page

Note: several content types span two intent classes. Pillar pages are informational but also navigational (hub for the cluster). Category pages are commercial but also navigational (people type the category name to browse). Pick the dominant intent, but don't be surprised when a page has to satisfy both.

A few more overlaps worth flagging. Integration pages and category pages both straddle commercial and navigational. Programmatic pages can skew either informational or commercial depending on the variable. Service pages are commercial in SERP but behave like transactional once the visitor lands.

## When to load the full per-type file

The decision table gives you enough to pick the type and draft the skeleton. Load the full `content-types/<type>.md` when:

- **pillar-page**: you need the hub-and-spoke linking architecture, the visual-break rhythm (image/table every 300-500 words), and the regular-update cadence rules. The overview doesn't capture the "every cluster article links back" rule, which is the whole point of the pattern.
- **comparison**: you need the full 10-section framework, especially the "verdict first per criterion" rule at the H3 level. Comparison articles fail hard if you just know the H2 skeleton.
- **how-to**: you need the quick-answer targeting (40-60 words, ordered list after the most relevant H2) and the step-by-step "one action per step" constraint. The anti-AI section on error messages and version numbers is the highest-signal part.
- **case-study**: you need the PAS-adjacent structure (challenge → approach → results → takeaways) and the "lead with the number in H1 and first 50 words" rule. The overview skips the client-permission and visual-proof requirements.
- **product-review**: you need the "who should skip" framing and the Google review-update requirements around hands-on evidence.
- **programmatic-page**: you need the quality-gate logic (noindex thin pages, conditional template copy, sibling linking). Shipping programmatic without reading the full file gets you penalized.
- **listicle**: you need the "methodology section + updated quarterly" rule and the 7-10 item sweet spot.
- **glossary**: you need the A-Z navigation pattern, anchor-link scheme, and the cross-reference style between terms.
- **location-page**: you need the doorway-page warning. Location pages without genuinely unique per-city content get penalized. The overview doesn't make this loud enough.

For everything else the overview table is usually enough to draft the first pass. Go deeper if the draft feels generic or if you're unsure about a specific structural element.

## Cross-reference: YMYL-sensitive types

YMYL ("your money or your life") topics trigger elevated E-E-A-T and Trust scrutiny from Google's quality raters. The content types that live closest to YMYL need named authors, visible credentials, transparent methodology, and verifiable evidence. That list: **pricing-page**, **service-page**, **product-review** (Google's review update explicitly targets this type), **case-study**, **about-page** (the page raters read to assess the whole site's trust), **thought-leadership**, and any **news** article about health, finance, legal, or safety topics. For these, skip stock photos, add real author bylines with linked credentials, include dated evidence (screenshots, numbers, timelines), and publish visible update logs. If you're writing in a regulated niche (medical, financial advice, legal), the Trust bar is higher than any of the per-type files capture. Add a subject-matter expert reviewer byline and cite primary sources (regulators, peer-reviewed studies) rather than secondary blogs.

## Word count targets by intent

The overriding rule: match the average word count of the top 5 ranking results, then add roughly 10%. Don't pad to hit a number. Don't under-write to stay "concise" when the SERP is hungry for depth.

| Intent class | Typical range | Rule of thumb |
|---|---|---|
| Informational (simple) | 800-1,500 | Match SERP average; news and short definitions fall here |
| Informational (deep) | 1,500-3,500 | How-to, statistics, FAQ, buying guide: depth signals expertise |
| Informational (hub) | 3,000-5,000+ | Pillar pages only; every section earns its place |
| Commercial investigation | 1,200-3,000 | Comparison, listicle, alternatives, review: enough to build confidence before conversion |
| Transactional | 500-1,500 | Pricing, product, landing, integration: short and scannable, conversion over coverage |
| Trust / navigational | 500-1,500 | About, category: authentic over long, unique content over padding |
| Programmatic at scale | 500-1,200 per page | Quality gates first; noindex anything thin |

When the SERP has mixed formats (one pillar, three listicles, one FAQ), write for the dominant format but cover the angles the minority formats introduce. If the top 5 are all 3,500 words and yours is 1,200, you're not competing. You're just hoping.

## Related reference files

If you need the underlying methodologies rather than the content-type skeletons, load these from the same `references/` directory:

- `intent-matching.md`: the full intent-classification logic and SERP-reading playbook
- `serp-driven-writing.md`: how to read the top 5 and extract the winning format
- `structured-data-snippets.md`: the full schema-markup catalog with examples
- `anti-slop-ruleset.md`: the banned-vocabulary list and structural tells
- `voice-injection-playbook.md`: how to inject first-person experience into any type
- `eeat-signal-embedding.md`: where and how to place author, credentials, and evidence

# Technique 17: Human Input Framework -- The Critical Differentiator

## What It Is
A structured system for collecting and integrating human-provided content into AI-assisted articles -- because AI without human input produces high-quality slop. The human's experiences, data, opinions, and case studies are what transform generic AI content into genuinely valuable, ranking-worthy articles.

## Why It Works
Every technique in this research converges on one truth: **AI content that ranks is content that includes things only a human could provide.** Information Gain requires unique data. EEAT requires demonstrated experience. Anti-AI-detection requires genuine opinions and idiosyncratic phrasing. NavBoost requires content that actually satisfies users.

AI alone cannot provide:
- First-party data from your business
- Case studies with real clients, real numbers, real timelines
- Genuine opinions and contrarian perspectives based on experience
- Specific tool interactions, error messages, and unexpected results
- The "what went wrong" stories that build trust

## The Human Input Hierarchy

### Tier 1: Essential (Content won't rank without these)
1. **First-party data**: Numbers from your own business, research, or analysis
2. **Case study details**: Client name (or anonymized), problem, solution, specific results
3. **Genuine opinion**: What the author actually thinks about the topic, including disagreements with conventional wisdom

### Tier 2: High-Value (Significantly improves quality)
4. **Specific experience details**: Tool versions, error messages, unexpected behaviors encountered
5. **Process documentation**: The exact steps the author follows, with reasoning for each
6. **Failure stories**: What was tried and didn't work, and why
7. **Comparisons from actual usage**: "I used tool A and tool B for 3 months each. Here's what I found."

### Tier 3: Enhancing (Adds polish and authenticity)
8. **Analogies and metaphors**: The author's unique way of explaining a concept
9. **Predictions/opinions**: Where the author thinks the industry is heading
10. **Behind-the-scenes context**: Why certain decisions were made, what alternatives were considered
11. **Personal anecdotes**: Brief relevant stories that illustrate points

## Step-by-Step Process

### Step 1: Pre-Writing Interview (5-10 questions)
Before the AI pipeline starts, collect human input via structured questions:

**For blog posts / thought leadership:**
1. "What's YOUR take on [topic]? What do you disagree with that most people believe?"
2. "Can you share a specific example or case study related to [topic]?"
3. "What numbers or data do you have from your own experience?"
4. "What's the most common mistake you see people make with [topic]?"
5. "If you had to give one piece of counterintuitive advice on [topic], what would it be?"

**For how-to guides / tutorials:**
1. "When you do [process], what's the exact sequence of steps?"
2. "What usually goes wrong? What error messages do people see?"
3. "What prerequisite do beginners always forget?"
4. "Is there a shortcut or trick that makes this significantly easier?"
5. "What tools/versions do you use, and does it matter?"

**For product/comparison content:**
1. "Which option do you actually recommend and why?"
2. "What's the biggest hidden drawback that nobody mentions?"
3. "Who should NOT use this product/approach?"
4. "What's changed about this product/market in the last 6 months?"
5. "Can you share specific metrics from your usage?"

### Step 2: Input Integration
6. Map each human input to a specific section of the outline
7. Use direct quotes where the human's phrasing is distinctive
8. Weave data points into arguments (don't dump them in a "data" section)
9. Use case studies as section anchors (start sections with the story)
10. Let opinions drive the article's angle, not just flavor paragraphs

### Step 3: Input Verification
11. If the human provides statistics, verify they're reasonable
12. If the human names tools or products, verify they exist and are current
13. If the human references clients, confirm disclosure is appropriate
14. Flag any claims that need supporting evidence

### Step 4: Quality Gate
15. Before finalizing, check: "What in this article could ONLY come from this specific human?"
16. If the answer is "nothing" or "just the case study in paragraph 7," more human input is needed
17. Target: at least 20% of the article's value should be human-sourced

## The Input Collection Interface (MCP Skill Design)

A well-designed workflow should implement a structured input collection:

```
CONTENT WRITING REQUEST
========================
Topic: [user provides]
Content Type: [user selects from 10 types]
Target Keyword: [user provides]

HUMAN INPUT REQUIRED
========================
DATA: Do you have any data or numbers to include?
   [text input -- first-party data, metrics, percentages]

CASE STUDY: Can you share a specific case study or example?
   [text input -- client story, project outcome, before/after]

OPINION: What's YOUR opinion on this topic? Any disagreements with conventional wisdom?
   [text input -- personal take, contrarian view]

CONTRARIAN: What common advice on this topic do you think is WRONG?
   [text input -- things that don't work, outdated advice]

PROCESS: Any specific tools, processes, or methods you use?
   [text input -- exact steps, tool names, configurations]

FAILURES: What usually goes wrong with this? Any failure stories?
   [text input -- mistakes, unexpected results, lessons learned]

[Optional] Upload voice samples for brand voice matching
[Optional] Paste 2-3 example articles in your style
```

## Tips

- **Audio input is often better than text**: People share more detailed, natural-sounding experiences when speaking vs typing. If possible, accept voice memos and transcribe them.
- **The "why" follow-up**: When the human says "we use tool X," follow up with "why did you choose X over alternatives?" -- the reasoning is the information gain, not the tool name.
- **Anonymization template**: Provide a simple template for case studies that need anonymization: "A [industry] company with [X employees] in [region]..."
- **Capture the messy version**: Raw, unpolished human input often sounds MORE authentic than cleaned-up versions. Preserve the original voice.

## Common Mistakes

1. **Making human input optional**: If the pipeline allows "skip" on all human input fields, users will skip everything -- and the content will be generic
2. **Collecting input after writing**: Human input should shape the OUTLINE and WRITING, not be bolted on as quotes after the fact
3. **Over-processing human input**: Don't AI-rewrite the human's case study. Their natural phrasing is an anti-detection signal.
4. **One input, many articles**: Each article should have UNIQUE human input. Reusing the same case study across 10 articles weakens information gain.

# Technique 01: Information Gain Writing

## What It Is
Writing content that adds genuinely NEW information compared to what already ranks for a keyword. Based on Google's Information Gain patent (granted June 2024), which scores how much additional value a page provides beyond existing search results.

## Why It Works
Google's algorithm compares your content against other pages the user has already seen on the same topic. Pages that say the same thing as the top 10 get low Information Gain scores. Pages that add unique data, perspectives, or insights get high scores — and rank higher.

The API leak confirmed this via `OriginalContentScore` — a separate metric that evaluates content uniqueness across the index.

**Algorithm reasoning:** If 10 pages all explain "how to do X" the same way, Google gains nothing by showing an 11th identical page. But if page 11 adds a case study, original data, or a contrarian perspective? That's information gain — value the user can only get from YOUR page.

## Step-by-Step Process

### Step 1: SERP Gap Analysis
1. Search the target keyword and read the top 10 results fully
2. Create a spreadsheet: rows = topics covered, columns = each competitor
3. Mark what each competitor covers and — critically — what they DON'T cover
4. Identify patterns: where do all 10 say the same thing? Where do they disagree?
5. Note the "missing angles": perspectives, data types, or use cases nobody addresses

### Step 2: Unique Value Identification
6. Ask: "What do I know about this topic that these 10 pages don't include?"
7. Sources of unique value:
   - **First-party data**: "We analyzed 500 customer accounts..."
   - **Original case studies**: "Client X tried this and here's what happened..."
   - **Expert interviews**: "I spoke with [Name], who said..."
   - **Contrarian perspective**: "Most guides say X. In our experience, Y works better because..."
   - **Process documentation**: "Here's the exact 9-step process we use internally..."
   - **Failure stories**: "We tried the common approach and it failed because..."
   - **Tool comparison**: "We tested 4 tools and measured actual results..."
8. Select 3-5 information gain elements to include

### Step 3: Content Architecture
9. Structure the article to lead with unique insights, not rehashed basics
10. Place information gain elements in the first 30% of the content (Google evaluates engagement early)
11. Use unique headings that signal novel content (not generic "What is X?" and "Benefits of X")
12. Plan specific data points, quotes, and examples for each section

### Step 4: Writing with Information Gain
13. Every section must answer: "What can the reader ONLY learn here?"
14. Replace generic statements with specific ones:
    - Bad: "Many companies have seen success with this approach"
    - Good: "We implemented this for 12 e-commerce clients in 2025. Average conversion improvement was 23%, but 3 clients saw no change — all in the B2B space"
15. Add "not found elsewhere" sections: edge cases, failure modes, advanced tips

## Hidden Tips & Tricks

- **The "So What?" test**: After every paragraph, ask "So what? Where can I ONLY read this?" If the answer is "anywhere," the paragraph has zero information gain.
- **Use your analytics**: Your GSC data, your customer data, your A/B test results — these are information gain goldmines that competitors literally cannot replicate.
- **Cite non-obvious sources**: Everyone cites HubSpot and Ahrefs. Cite academic papers, industry reports from niche organizations, or government data nobody else uses.
- **The 10-10-80 rule**: 10% covering basics (for context), 10% discussing what the competition says, 80% unique content. Most AI content is 80-10-10 — the opposite.

## Common Mistakes

1. **Thinking "more words" = information gain** — A 5,000-word article repeating the same points as competitors has zero information gain. A 1,500-word article with original data has high gain.
2. **Adding information gain at the end** — Google evaluates engagement early. Put unique insights in the first 500 words, not the conclusion.
3. **Fabricating data** — Never make up statistics for information gain. One fabricated stat that gets fact-checked destroys all credibility.
4. **Confusing "different format" with "different information"** — Putting the same information in a table instead of paragraphs isn't information gain.

## When to Use This Technique

- **Always** for competitive keywords (keyword difficulty > 30)
- For any content where you have access to unique data or experiences
- When updating content that lost rankings (likely lost due to competitors with higher information gain)
- Critical for pillar/hub content that anchors a topic cluster

## Algorithm Confirmation (from Google Leak)

The Information Gain patent (granted June 2024) explicitly describes the scoring system:

> "Information gain scores indicate how much more information one source may bring to a person who has seen other sources on the same topic. Pages with higher information gain scores may be ranked higher."

This means Google is not just comparing your page to competitors -- it's comparing it to pages the *specific user* has already seen in their search session. Returning to search after reading 3 similar articles? The 4th needs to add something NEW.

**Tools Used:**
- keyword search — identify target keyword landscape
- competitor data — analyze who ranks for this topic
- opportunity detection — find keywords where we rank 4-20
- SERP feature detection — identify featured snippet / PAA opportunities
- page-level SEO data — analyze current page performance if updating

# Technique 10: Search Intent Matching

## What It Is
Writing content that matches the exact type of information a user expects when they search a keyword -- not just covering the topic, but delivering it in the FORMAT and DEPTH the user needs at that moment in their journey.

## Why It Works
Google's NavBoost system (confirmed by the 2024 API leak) tracks what happens after a user clicks a search result: do they stay, engage, and convert -- or do they bounce back to try another result? Content that mismatches intent causes pogo-sticking, which directly harms rankings.

The December 2025 Core Update doubled down on intent matching: pages optimized for the wrong intent dropped 30-90% regardless of content quality or domain authority.

## The Four Intent Types

### 1. Informational ("I want to learn")
- **Keywords**: "how to...", "what is...", "why does...", "guide to..."
- **User expectation**: Comprehensive answer, step-by-step instructions, explanations
- **Format**: Long-form articles, how-to guides, explainers, tutorials
- **Critical first 100 words**: Must signal "this page teaches you [exact topic]"
- **SEO signals**: HowTo schema, FAQ schema, table of contents

### 2. Commercial Investigation ("I want to compare")
- **Keywords**: "best...", "vs...", "review...", "top 10...", "comparison..."
- **User expectation**: Hands-on comparison, recommendations, honest assessment
- **Format**: Comparison tables, review articles, listicles with scoring
- **Critical first 100 words**: Must mention the things being compared and signal real testing
- **SEO signals**: Product schema, Review schema, comparison tables

### 3. Transactional ("I want to buy/do")
- **Keywords**: "buy...", "price...", "sign up...", "download...", "[product name]"
- **User expectation**: Clear pricing, easy purchase path, conversion-focused
- **Format**: Product pages, landing pages, pricing pages
- **Critical first 100 words**: Value proposition + CTA visibility
- **SEO signals**: Product schema, Offer schema, clear CTAs

### 4. Navigational ("I want to find a specific page")
- **Keywords**: "[brand name]", "[brand] login", "[product] pricing"
- **User expectation**: The exact page they're looking for
- **Format**: The actual page (homepage, login, pricing)
- **SEO signals**: Brand entity signals, sitelinks

## Step-by-Step Process

### Step 1: Intent Classification
1. Search the target keyword in Google
2. Look at the TOP 3 results -- Google has already classified intent
3. Note the content TYPE ranking: are they blog posts? Product pages? Comparison articles? YouTube videos?
4. If top 3 are all comparison articles and you write a how-to guide, you WILL NOT rank

### Step 2: Format Matching
5. Match the dominant format in the SERP:
   - All listicles -> write a listicle
   - All how-to guides -> write a how-to guide
   - Mix of formats -> the intent is fragmented; pick the one that aligns with your content type
6. Exception: if ALL top 10 use the same format, there's an opportunity to differentiate IF you still match intent (e.g., a video among all text results)

### Step 3: Depth Calibration
7. Measure competitor word counts for the top 5 results
8. Your content should match or slightly exceed the depth level
9. **But**: more words does not equal better depth. A 5,000-word article for "what time is it in Tokyo" is absurd. Match the COMPLEXITY of the intent.

### Step 4: First-100-Words Optimization
10. The first 100 words must immediately signal intent match
11. **Informational**: Answer the core question within the first paragraph, then expand
12. **Commercial**: Name the products/options being compared and establish credibility
13. **Transactional**: State the value proposition and make the CTA visible
14. Users who don't see intent match in 5 seconds bounce -- NavBoost penalizes this

### Step 5: Content Structure for Intent
15. Structure the article to match how users consume content for each intent:
    - **Informational**: TL;DR -> detailed sections -> summary/checklist
    - **Commercial**: Quick comparison table -> detailed reviews -> recommendation
    - **Transactional**: Benefit headline -> features -> social proof -> CTA
    - **Mixed**: Address primary intent first, secondary intents in supporting sections

## Content Length by Intent

Ahrefs found near-zero correlation (0.04) between word count and ranking. Match the SERP, not a word count target.

| Intent | Optimal Length | Rationale |
|--------|---------------|-----------|
| Informational (comprehensive guide) | 1,500-3,000+ | Needs to cover the full topic |
| Informational (specific question) | 800-1,500 | Answer directly, don't pad |
| Commercial investigation (comparison) | 1,200-2,500 | Depth in evaluation criteria |
| Commercial investigation (roundup) | 2,000-4,000 | Multiple items need coverage |
| Transactional | Minimal needed | No fluff; specs, pricing, CTA |
| Local service | 300-500 unique words | Must be genuinely unique per location |

**Key rule:** Match the SERP. If top 5 results average 2,000 words, write 2,000-2,500. If they average 800, writing 3,000 wastes effort and may signal wrong intent.

## Tips

- **Check "People Also Ask"**: These reveal the JOURNEY. If PAA for "best CRM" includes "is Salesforce worth it?" and "CRM pricing comparison," users are in commercial investigation -- not informational.
- **Search intent can shift**: "AI writing tools" in 2023 = informational ("what are they?"). In 2026 = commercial investigation ("which one should I use?"). Always verify current SERP, don't assume.
- **Mobile vs desktop intent**: The same keyword can have different intent on mobile (quick answer) vs desktop (deep research). Optimize for both, but prioritize based on traffic split.
- **Featured snippet = informational confirmation**: If Google shows a featured snippet, the intent is informational. Structure your content to capture it (direct answer in 40-60 words).

## Common Mistakes

1. **Writing a blog post for a transactional keyword**: "Buy running shoes" -> users want a product page, not a 2,000-word guide
2. **Writing a product page for an informational keyword**: "How to choose running shoes" -> users want guidance, not a buy button
3. **Ignoring mixed intent**: Some keywords have genuinely mixed intent. Your page must address the primary intent fully and nod to secondary intents
4. **Over-optimizing for one intent type**: Don't force transactional CTAs into informational content. It feels manipulative and users bounce.

# Technique 05: SERP-Driven Writing

## What It Is

Writing content based on what ACTUALLY ranks in Google, not what theoretically should work. Every structural decision -- headings, length, format, keyword placement -- is derived from analysis of the current top 10 results for the target keyword.

## Why It Works

Google's ranking system is empirical. What ranks IS what Google rewards. SERP analysis reverse-engineers the patterns that currently win for a specific query. This approach beats theoretical best practices because it accounts for query-specific factors: intent, competition level, SERP features, and user expectations.

Kyle Roof's 400+ controlled experiments at PageOptimizer Pro proved that on-page signals alone can achieve rankings -- but only when those signals match what Google expects for that specific query.

## E-E-A-T: What Actually Matters

### The Reality (vs. What Google Says)

**Kyle Roof's tested position:** E-E-A-T elements will NOT help you rank, but they help you KEEP your rank once evaluated. He ranked a Lorem Ipsum page for "Rhinoplasty Plano" using on-page signals alone. E-E-A-T is defensive, not offensive.

**The priority:** Trust > Expertise > Experience > Authoritativeness

**Cyrus Shepard's 50-site case study (4,000+ websites across 2023 updates):**
- Winners: used first-person pronouns, demonstrated first-hand experience
- Losers: excessive ads (14.01 per page vs. 6.32 on winners), over-optimized anchor text
- 17 on-page features showed statistically significant correlations

### E-E-A-T Signals the Writing Skill Should Produce

**Experience signals (the new "E"):**
- First-person language: "in my testing," "when I tried," "our data shows"
- Specific case studies with real numbers and dates
- References to original photos, screenshots, or videos
- Practical tips that only come from doing the thing

**Expertise signals:**
- Depth of coverage (not just mentioning a topic, but explaining the WHY)
- Correct use of industry terminology
- Nuanced positions (not just repeating the obvious)
- Citing specific sources (not "experts say")

**Trust signals:**
- Author attribution with verifiable credentials
- Transparent methodology ("here's how we tested this")
- Honest limitations ("this approach doesn't work for X")
- Clear source attribution for claims

## Keyword Placement (Kyle Roof's Tested Hierarchy)

Based on 400+ controlled experiments:

**Group A (Highest weight):**
- Meta title -- the undisputed #1 on-page signal

**Group B:**
- URL path
- H1 heading
- Body content (~2% density, naturally distributed)
- H2 headings (primary keyword or close variation in 2-3 H2s)
- H3/H4 headings
- Anchor text of internal links TO this page

**Group C:**
- Bold text
- Italic text
- Image alt text

**Group D (Lowest):**
- Schema markup text
- HTML tags
- Open graph text

**Not indexed at all:**
- Meta description (doesn't affect rankings, but affects CTR)
- Meta keyword tag

**Kyle Roof's evolved position:** Stop counting exact-match keywords. Instead, ensure the page includes the FULL VOCABULARY of the topic. Topical completeness matters more than keyword density.

## Content Length by Intent

Ahrefs found near-zero correlation (0.04) between word count and ranking. The data by intent:

| Intent | Optimal Length | Rationale |
|--------|---------------|-----------|
| Informational (comprehensive guide) | 1,500-3,000+ | Needs to cover the full topic |
| Informational (specific question) | 800-1,500 | Answer directly, don't pad |
| Commercial investigation (comparison) | 1,200-2,500 | Depth in evaluation criteria |
| Commercial investigation (roundup) | 2,000-4,000 | Multiple items need coverage |
| Transactional | Minimal needed | No fluff; specs, pricing, CTA |
| Local service | 300-500 unique words | Must be genuinely unique per location |

**Key rule:** Match the SERP. If top 5 results average 2,000 words, write 2,000-2,500. If they average 800, writing 3,000 wastes effort and may signal wrong intent.

## Featured Snippet Optimization

**Format distribution:** Paragraph (70%), List, Table, Video

**Optimal answer length:** 40-50 words (293 characters average)

**Query-format mapping:**
- "How" queries -> ordered list snippets (46.91%)
- "Does/Are/Is/Can/Should/Will" queries -> paragraph snippets
- Comparison queries -> table snippets
- "What is" queries -> paragraph snippets (definition format)

**Implementation:** Place a 40-60 word direct answer immediately after the relevant H2. Format it as the snippet type Google expects for that query. Then expand below.

## People Also Ask Coverage

PAA prevalence spiked 34.7% on mobile and 37.5% on desktop (2024-2025). Your site does NOT need to rank #1 to appear in PAA.

**Strategy:**
- Include 3-5 PAA questions as H2 or H3 headings
- Answer each in 40-60 words immediately after the heading
- Then expand with detail below the direct answer
- Use the exact question phrasing when natural

## Algorithm Signals That Matter (From the Leak)

### NavBoost (Confirmed)
Uses rolling 13-month window of click data. Tracks:
- **goodClicks** -- positive engagement
- **badClicks** -- negative engagement
- **lastLongestClicks** -- where the user's search ENDED (strongest signal)

**Writing implication:** Content must immediately engage. The first screen of content determines whether users stay or pogo-stick back. Front-load value.

### Information Gain (Patent Granted June 2024)
Measures how much UNIQUE information a document provides beyond what already exists. NOT about length -- about saying something competitors don't.

**Writing implication:** Every article must contain at least one section that adds genuinely new information: original data, unique analysis, contrarian perspective, or specific case study.

### Site Authority (Confirmed in Leak)
Despite public denials, Google has a site-level authority metric. Homepage authority influences the entire domain.

**Writing implication:** Each piece of content contributes to site-level authority. Thin, low-quality content hurts the whole domain (HCU classifier operates site-wide).

## Content Scoring Tools: Reality Check

Surfer SEO, Clearscope, Frase analyze top-ranking pages and identify patterns. Ahrefs tested correlation with actual rankings:
- NeuronWriter + Ahrefs: Strongest (but modest) correlation
- Clearscope: ~0.30
- Surfer SEO: ~0.27

**The fundamental limitation:** These tools measure FIRST-STAGE retrieval signals only (lexical matching, BM25-style). After that:
1. RankEmbed adds candidates keyword matching missed
2. Mustang applies ~100+ signals including NavBoost, quality scores
3. DeepRank applies BERT-based understanding to final 20-30 results

**Bottom line:** Use SERP-derived topical completeness as a baseline check, not a ranking guarantee. The writing skill should ensure all SERP-common topics are covered, but the real ranking signals come from engagement, uniqueness, and authority.

## Content Freshness

### QDF (Query Deserves Freshness)
Activates for: breaking news, recurring events, topics with frequent updates. When active, newer content temporarily outranks stronger traditional signals.

### AI Citation Freshness
ChatGPT shows strongest recency preference: 76.4% of most-cited pages were updated within 30 days.

### Practical Rules
- Date-stamp all content with publication and last-updated dates
- Update high-traffic content every 3-6 months
- Don't just change the date -- Google detects fake freshness
- 51% of companies report updating content is more effective than creating new

## Tips

- Match SERP format exactly: if the top 5 all use comparison tables, include a comparison table
- Check SERP features before writing: featured snippets, PAA, video carousels each require different content structures
- Use SERP feature detection to identify which SERP features are available for target keywords
- Monitor ranking changes after publishing to validate SERP-driven decisions

## Common Mistakes

1. **Ignoring the SERP entirely** -- writing based on assumptions instead of what currently ranks
2. **Over-optimizing for content scoring tools** -- these only measure first-stage retrieval signals
3. **Writing longer than needed** -- if the SERP rewards 800-word answers, a 3,000-word article signals wrong intent
4. **Copying competitor structure without adding value** -- matching format is necessary but insufficient; you still need information gain

## Key Sources

- Kyle Roof -- PageOptimizer Pro: [nichepursuits.com](https://www.nichepursuits.com/kyle-roof-hcu/), [pageoptimizer.pro](https://www.pageoptimizer.pro/bestplacestoputakeyword)
- Cyrus Shepard -- [zyppy.com](https://zyppy.com/seo/google-update-case-study/)
- [Content Scoring: First Gate in Google's Pipeline (Search Engine Land)](https://searchengineland.com/content-scoring-tools-work-but-only-for-the-first-gate-in-googles-pipeline-469871)
- [Ahrefs Content Score Study](https://ahrefs.com/blog/seo-content-score-study/)
- [NavBoost Analysis (Hobo)](https://www.hobo-web.co.uk/navboost-how-google-uses-large-scale-user-interaction-data-to-rank-websites/)
- [Google Leak Analysis (Hobo)](https://www.hobo-web.co.uk/the-google-content-warehouse-leak-2024/)
- [Information Gain Patent (SEJ)](https://www.searchenginejournal.com/googles-information-gain-patent-for-ranking-web-pages/524464/)
- [Featured Snippet Statistics 2025](https://mycodelesswebsite.com/featured-snippet-statistics/)

# Technique 13: Structured Data & SERP Feature Capture

## What It Is
Using structured data (JSON-LD schema markup) and content formatting to capture SERP features -- featured snippets, FAQ dropdowns, How-To cards, and rich results that increase visibility, CTR, and NavBoost signals.

## Why It Works
SERP features occupy prime real estate above or within organic results. Pages with rich results get 20-40% higher CTR than plain blue links. Higher CTR feeds NavBoost (Google's click-based ranking signal), creating a compound ranking advantage.

Additionally, structured data is how content gets cited by AI Overviews and AI search engines. Without it, your content is less likely to be selected as a source for AI-generated answers.

## SERP Features by Content Type

| Content Type | Target SERP Features | Schema Types |
|-------------|---------------------|-------------|
| Blog post | Featured snippet, PAA | Article, FAQPage |
| How-to guide | HowTo card, Featured snippet | HowTo, FAQPage |
| Product page | Product rich result, Review stars | Product, Review, Offer |
| FAQ page | AI Overview citation, PAA | FAQPage |
| Comparison | Comparison table, Review stars | Article, Product, Review |
| Recipe | Recipe card | Recipe |
| Event | Event listing | Event |
| Local business | Local pack, Knowledge panel | LocalBusiness |

## Step-by-Step Process

### Step 1: Identify Feature Opportunities
1. Use SERP feature detection from to see which features appear for target keywords
2. Search the keyword manually -- what features are currently showing?
3. Note: featured snippets, PAA boxes, HowTo cards, video carousels
4. Check if any competitor has a SERP feature you could capture

### Step 2: Content Formatting for Featured Snippets
5. **Paragraph snippets** (most common):
   - Place a direct answer in 40-60 words immediately after an H2 matching the query
   - Start with the definition/answer, then expand
   - Example: "What is information gain?" -> H2 -> 45-word direct answer -> detailed explanation
6. **List snippets**:
   - Use numbered or bulleted lists with clear H2 header
   - 5-8 items is optimal
   - Each item should be a clear, scannable point
7. **Table snippets**:
   - Use HTML tables with clear column headers
   - 3-5 columns, 4-10 rows
   - Comparison data is ideal for table snippets

### Step 3: FAQ Schema Implementation
8. Identify 3-5 questions users ask about the topic (use PAA boxes as source)
9. Include each question as an H2 or H3
10. Answer directly in 40-100 words
11. Implement FAQPage schema with each Q&A pair:
   ```json
   {
     "@context": "https://schema.org",
     "@type": "FAQPage",
     "mainEntity": [{
       "@type": "Question",
       "name": "What is information gain in SEO?",
       "acceptedAnswer": {
         "@type": "Answer",
         "text": "Information gain in SEO measures how much new, unique information your content provides compared to other pages on the same topic. Google's patented Information Gain Score rewards pages that add original data, perspectives, or insights not found in competing results."
       }
     }]
   }
   ```

### Step 4: HowTo Schema
12. For tutorial/guide content, implement HowTo schema:
    - Each step as a separate `HowToStep`
    - Include `estimatedCost` and `totalTime` when applicable
    - Add `tool` and `supply` arrays
    - Include images per step when possible

### Step 5: Article/Product Schema
13. **Article schema** (for blog posts, guides):
    - `author` with name and URL
    - `datePublished` and `dateModified`
    - `image` (required for rich results)
    - `headline` matching H1
14. **Product schema** (for product/review pages):
    - `offers` with price, availability, currency
    - `review` with `ratingValue` and `bestRating`
    - `brand` entity

### Step 6: Validation
15. Test all structured data with Google's Rich Results Test
16. Monitor Search Console for structured data errors
17. Verify rich results appear in SERPs after indexing

## Tips

- **PAA as keyword research**: "People Also Ask" questions are literally Google telling you what related queries users search. Answer them in your content -> PAA placement and AI Overview citations.
- **Featured snippet "sniping"**: Find a keyword where the current featured snippet is mediocre. Write a better, more direct answer in the same format. Google swaps snippets regularly.
- **Don't over-schema**: Adding 50 FAQ items or marking up content that doesn't qualify for a schema type can trigger manual actions. Only mark up content that genuinely matches the schema type.
- **AI Overview sourcing**: Structured data helps your content get selected as a source for AI Overviews. Content with clear schema markup is easier for AI systems to parse and cite.

## Common Mistakes

1. **FAQ schema for non-questions**: Only use FAQPage schema for actual Q&A content. Using it for bullet points or regular content is a misuse.
2. **Missing required fields**: Schema without required fields (like `image` for Article) won't generate rich results
3. **Duplicate schema**: Having both FAQPage and HowTo on the same page can conflict. Choose the primary schema type.
4. **Not monitoring**: Structured data can break (especially after CMS updates). Monitor Search Console regularly.

## GEO (AI Citation) Impact

Structured data directly impacts AI citation rates:
- **FAQ schema has 3.2x higher citation rate** in AI Overviews
- **92% of AI Overview citations** come from top-10 ranking pages -- SERP features help you get there
- **Answer-first formatting** (40-60 word direct answers under H2s) produces +340% AI citations
- Content with clear schema markup is easier for AI systems to parse and cite

Write comprehensive content (for Google) with clear, extractable summary answers at the start of each section (for AI). The overlap between SERP feature optimization and AI citation optimization is ~80%.

## Tools Used
- SERP feature detection -- identify which features appear for target keywords
- keyword search -- find keywords with featured snippet opportunities
- page-level SEO data -- check current SERP feature status for existing pages