# Technique 04: EEAT Signal Embedding

## What It Is
Systematically embedding Experience, Expertise, Authoritativeness, and Trustworthiness signals into content — not as claims ("we're experts") but as demonstrated proof through content structure, source attribution, and writing patterns.

## Why It Works
Google's algorithm leak confirmed that EEAT is evaluated through proxy signals. Google cannot independently verify if content is accurate — it uses structural indicators that correlate with knowledgeable sources. Content that SHOWS expertise through depth, specificity, and honest nuance outranks content that merely CLAIMS expertise.

The December 2025 Core Update specifically intensified EEAT evaluation, particularly the "Experience" component — first-hand involvement signals.

## The Four EEAT Components — What They Actually Mean

### Experience (Most underrated)
- **What Google says**: Content created by someone with first-hand experience
- **What it actually means**: Specific details only someone who DID the thing would know
- **Signal strength**: Very high since the "first E" was added in December 2022

**Weak experience signals (don't work):**
- "I have 15 years of experience in marketing"
- "As an expert in this field..."
- Author bio listing credentials

**Strong experience signals (actually work):**
- "When we ran this campaign for [Client], the Facebook CPC averaged €2.40 — until we changed the creative on day 7 and it dropped to €0.85"
- "The first time I set this up, I forgot to configure the DNS TXT record and spent 3 hours debugging. Save yourself the trouble: do it first."
- Mentioning specific tool versions, error messages, unexpected results
- Describing what DIDN'T work before finding what did

### Expertise (Depth over breadth)
- **What it actually means**: Content that demonstrates understanding of nuance, edge cases, and tradeoffs — not surface-level coverage of everything
- **The expertise paradox**: Real experts narrow their scope. Beginners try to cover everything. Content that says "this works for B2B SaaS with >€5K ACV but NOT for consumer apps" demonstrates more expertise than content covering all business types generically.

**Expertise signals:**
- Discussing when advice DOESN'T apply
- Explaining the "why" behind each recommendation
- Acknowledging tradeoffs ("this increases conversion but may increase support tickets")
- Using precise terminology correctly (not keyword-stuffing but natural domain language)
- Addressing edge cases and exceptions

### Authoritativeness (Being cited, not claiming)
- **What it actually means**: Other people and sites reference you as a source
- **This is mostly a domain-level signal**, not a content-level one
- Content can support it through: accurate citations of others (builds reciprocal authority), original research that others want to cite, named author with verifiable credentials

### Trustworthiness (Transparency and accuracy)
- **What it actually means**: The content is verifiable, transparent about limitations, and doesn't mislead
- Every statistic has a named source with date
- Affiliate relationships or biases are disclosed
- Claims are hedged when appropriate ("in our experience" vs "always")
- Errors are corrected (dated correction notes build trust)

## Step-by-Step Process

### Step 1: Experience Signal Planning
1. Before writing, identify 3-5 experience markers to embed:
   - A specific project/client/implementation story
   - A mistake made and lesson learned
   - A specific tool, metric, or process detail
   - An unexpected result or counterintuitive finding
   - A comparison between expected and actual outcome
2. These CANNOT be generated by AI — they must come from the human author

### Step 2: Expertise Signal Architecture
3. Structure the article to demonstrate depth:
   - Cover the "advanced" angle, not the "intro" angle (unless intent is beginner)
   - Include "when NOT to do this" sections
   - Discuss tradeoffs explicitly
   - Address 2-3 edge cases or exceptions
4. Use precise domain terminology naturally (not forced)

### Step 3: Source Attribution (Trustworthiness)
5. Every factual claim must have a source:
   - Academic papers → Author, year, journal
   - Industry reports → Organization, year, specific finding
   - Statistics → Source name, year, methodology note
   - Expert opinions → Named person, credentials, context
6. Replace ALL instances of:
   - "Studies show..." → "[Organization]'s [year] study of [N] [subjects] found..."
   - "Experts agree..." → "[Named expert], [credentials], argues that..."
   - "Research suggests..." → "A [year] [journal] paper by [author] demonstrated..."

### Step 4: Author Authority Integration
7. Include author byline with specific credentials relevant to THIS topic
8. Link to author's other published work on the topic
9. Reference personal involvement: "In my role as [specific title] at [company], I..."
10. If applicable, reference speaking engagements, publications, or patents

### Step 5: Trust Signals
11. Date the content prominently
12. Note when information was last verified
13. Disclose any affiliations, sponsorships, or biases
14. Include a methodology section for any original research/data
15. Add a corrections section if updating previously published content

## Tips

- **The "screenshot proof" technique**: Including actual screenshots of dashboards, results, or tools is one of the strongest experience signals. It's nearly impossible to fake and instantly demonstrates first-hand involvement.
- **Date your screenshots**: Screenshots with visible dates prove recency and experience
- **Name specific dollar amounts**: "$2,400/month" is more trustworthy than "thousands per month." Real practitioners know exact numbers.
- **Cite yourself**: If you've written about this topic before, reference your own earlier work with what you've learned since. This creates a trail of genuine expertise.
- **Use first-person sparingly but specifically**: Not "I think" for opinions, but "I tested" for experience and "I found" for results.

## Common Mistakes

1. **EEAT as a checklist**: Adding an author bio and citing 3 sources doesn't make content trustworthy. The EEAT signals must be woven through the content, not bolted on.
2. **Fake experience markers**: "Imagine you're building a website..." is not an experience signal. "When I built [specific site]..." is. AI defaults to hypotheticals; real EEAT uses specifics.
3. **Over-attributing to build trust**: Every sentence having a citation reads like an academic paper, not expert content. Cite where it matters; assert where you have authority.
4. **Confusing EEAT with keywords**: Adding "expert" and "authoritative" into your content doesn't improve EEAT. Demonstrating expertise through depth and specificity does.

## Research Evidence

### Kyle Roof's Testing-Based Position
E-E-A-T elements will NOT help you rank, but they help you KEEP your rank once evaluated. Roof's controlled experiments (ranking a Lorem Ipsum page for "Rhinoplasty Plano") proved on-page keyword signals alone can achieve rankings. E-E-A-T is defensive, not offensive.

**The priority:** Trust > Expertise > Experience > Authoritativeness. Kyle Roof: "Who cares about the E or the A -- it's all about the T. Trust."

### Cyrus Shepard's 50-Site Case Study (4,000+ Websites)
Across 2023 Google 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 with ranking gains/losses

### December 2025 Core Update
Specifically intensified EEAT evaluation, particularly the "Experience" component -- first-hand involvement signals became stronger ranking factors.

# 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

# Knowledge Document Template: Worked Example

This is what a good interview output looks like. Use it to calibrate the final step of the skill: how to organize the user's answers into something `write-content` or `improve-content` can actually use. Pattern-match against this example, don't copy the topic.

## The four-section structure

Every knowledge document the skill produces should have these four sections, in this order:

1. **Key insight / contrarian take**: the one thing the user knows that most people don't
2. **Specific examples and data points**: named clients, real numbers, actual projects, dates
3. **Experience details**: what worked, what failed, what surprised them
4. **Scope and limitations**: who this applies to, who it doesn't, when it breaks down

That's it. No executive summary, no intro, no "further reading" section, no fluff. This document gets fed to a writing skill; it's not published anywhere. Compression is the goal.

## Worked example

Topic: bootstrapping a B2B tool to $100K ARR. The user interviewed is a founder who did this between 2023 and 2025.

---

**Expert Knowledge: bootstrapping a B2B tool to $100K ARR**

### Key insight / contrarian take

Cold outbound works in year one and then stops working, but not because of deliverability. It stops because the founder runs out of interesting things to say. Most advice tells you to scale outbound to 500 emails a day. The real constraint after month six is that your own product usage doesn't produce enough new angles for a second email to the same prospect. The founders who plateau at $40-60K ARR are usually the ones still writing generic outbound. The ones who break past $100K started publishing case studies instead and letting warm inbound replace cold around month eight.

*Why this section matters for downstream writing: this gives the article a thesis. The writer can now lead with "cold outbound works until it doesn't, and it stops working for a specific reason nobody talks about" instead of yet another generic "here's how I got to $100K" post. The contrarian take sets the angle for every other paragraph in the eventual article.*

### Specific examples and data points

- First ten customers came from a single Reddit post in r/smallbusiness (March 2023), 38 upvotes, 400 clicks to landing page, 11 trial signups, 9 converted at €49/mo
- Cold outbound ran from May 2023 to January 2024, peaked at 280 emails/week, hit-rate dropped from 4.2% reply rate in month one to 0.6% in month eight
- Pivoted to publishing one customer case study every two weeks starting Feb 2024. First case study about a Dutch accounting firm drove 14 signups in a week, which was more than the previous month of outbound combined
- $100K ARR crossed in November 2024, 20 months after launch, 183 paying customers, blended ACV €546/year
- CAC in outbound phase: €118. CAC once content took over: €31
- Biggest wasted spend: €3,400 on a Facebook ads experiment in summer 2023 that produced zero paying customers

*Why this section matters for downstream writing: named subreddits, specific date ranges, euro amounts, and conversion percentages are Tier 1 information gain. A generic AI can't invent "€3,400 on Facebook ads in summer 2023" convincingly, and if it does, it's wrong. The writer should weave these numbers into arguments, not dump them into a "my results" box at the bottom. Every one of these data points can anchor a section.*

### Experience details

- Tried Lemlist, Instantly, and Smartlead for outbound. Lemlist was the worst because of deliverability issues in month three (blacklisted two sending domains). Smartlead was the best because of the shared IP rotation, but switching mid-campaign lost two weeks.
- The thing that actually worked on outbound wasn't the email copy, it was the subject line format: "{first name}, question about {their tool} → {our tool}". Ugly but hit-rate doubled.
- Biggest surprise: the top three customers by revenue all came from content, not outbound. The outbound customers churned at 3x the rate. By month 18, outbound had become a net loss if you properly attributed churn.
- Failure story: spent two months in mid-2024 trying to build an annual plan discount flow because a consultant said it would raise ACV. It did, by 18%, but also doubled the refund rate because customers signed up annually without understanding the product. Killed it in September.
- Unexpected lesson: the founder's personal LinkedIn drove more demo requests than the company LinkedIn by a factor of roughly six, even at similar follower counts. Company pages are noise; personal pages are signal.

*Why this section matters for downstream writing: the "failure story" and "unexpected lesson" bullets are exactly what the write-content skill will turn into the "what went wrong" paragraphs that build EEAT trust. A specific named tool (Lemlist) with a specific named problem (deliverability in month three, two blacklisted domains) is more believable and more rankable than "we tried a cold outreach tool and it didn't work out". The failure story about the annual plan consultant is gold because it has a direction nobody else writes about: "raising ACV made refunds worse."*

### Scope and limitations

- This approach only works for products priced €30-€80/month. Below €30 the content-driven CAC math doesn't work. Above €80 you actually do need sales and outbound becomes important again.
- Assumes the founder can write. The pivot from outbound to content assumes the user is capable of writing case studies that convert, and maybe three founders in ten actually are. The others should probably stay on outbound and hire a copywriter before scaling.
- Assumes a single-founder or two-person team. A five-person team burning salary has a different math problem and probably needs to raise, not bootstrap.
- The Reddit launch trick is almost certainly dead by 2026. Worked in 2023 because r/smallbusiness was less aggressive about promotional posts. Don't replicate it literally. Replicate the principle (one high-signal organic post in the right community) in whichever community is currently viable.
- Everything above is B2B only. B2C bootstrapping at this price point has different dynamics, especially around refunds and support volume.

*Why this section matters for downstream writing: this is the "who should NOT follow this advice" section, and it's what turns a generic success story into actual thought leadership. Most $100K ARR posts leave readers thinking "will this work for me?" and never answer. The scope section answers that directly. The writer should not bury this at the end of the article; it should be near the top, so readers who aren't the right fit self-select out.*

---

## What makes this document good vs bad

**Good** means the document passes the 30% Rule: at least 30% of any article written from it could not be produced by a generic AI. The test is simple. Strip out the named tools, the euro amounts, the dated events, the specific failure stories, and the scope conditions. What's left? If what's left is an article, the human input wasn't doing any work. If what's left is obviously broken, the human input was doing the work.

**Bad** looks like this:

> Key insight: cold outbound is harder than people think. You need good copy, good targeting, and good follow-up. Many founders underestimate how much effort goes into it.

This is the LinkedIn thought leader version. No numbers, no names, no dates, no scope. Every sentence could have been produced by an LLM, and probably has been, many times. If your interview output looks like this, the interview wasn't good enough. Go back and ask follow-ups. Ask for a number. Ask for a named tool. Ask for a date. Ask what broke.

**The test you should run on the document before handing it off:**

1. Pick any paragraph. Could the words "many", "some", "often", "usually" be deleted without loss? If yes, the paragraph is generic.
2. Is there at least one proper noun per bullet (a tool, a client, a subreddit, a country, a month)?
3. Are there numbers with units, or just vibes?
4. Does the scope section answer "who is this wrong for?", and not just "here's who it's right for"?

If all four answers are yes, hand it off. If any answer is no, you have one more follow-up question to ask before the interview is done.

## Cross-reference

See `information-gain-writing.md` in this references folder for the theory behind why specificity is what makes this document valuable. The short version: Google's Information Gain patent scores content against what the searcher has already seen on the same topic. Named tools, real dates, specific failures, scope limits: those are the things that by definition can't be on the other pages, because nobody else has them. Everything else in the article can be AI-generated. This document is the part that can't be.

# Question Bank by Topic

The SKILL.md has four core questions. This file expands the bank so the agent has real options to pick from. You're still only asking 2-4 questions per interview. The point is that the quality of the picks matters more than the quantity asked, and a bigger bank means better picks.

## Core questions (the universal four)

These stay as-is from SKILL.md. Every interview should draw at least one of these, usually two.

1. "What do most people get wrong about [topic]?"
2. "Can you give me a specific example — a client, a project, a number?"
3. "What surprised you when you actually did this?"
4. "Who should NOT follow this advice, and why?"

Everything below is topic-specific. Pick questions that fit what the user is actually writing about. Don't ask them in order; pick the 2-3 that are most likely to surface something an AI couldn't fabricate.

## Technical / how-to content

For tutorials, step-by-step guides, setup walkthroughs, debugging posts, configuration docs.

1. "What error does almost everyone hit first?"
2. "What step do beginners always skip?"
3. "What did you waste the most time on when you first did this?"
4. "What's the edge case that breaks most tutorials?"
5. "Which assumption in the official docs is wrong or outdated?"
6. "What's the fastest way to know if you're doing it wrong?"
7. "Which tool from the tutorial is actually optional?"
8. "What's the thing you wish someone had told you before starting?"
9. "How do you know you're done — not just done with the first pass, but actually done?"
10. "What breaks at scale that doesn't break in a toy example?"
11. "Which step in the standard tutorial is a waste of time?"
12. "What's the debug command you reach for when nothing works?"

The goldmine questions here are #3 and #10. Time-wasters and scale failures are very hard for an AI to hallucinate convincingly because they depend on the user's actual stack and traffic profile. That specificity is what the downstream writing skill needs.

## Comparison / review content

For "X vs Y" posts, product roundups, tool reviews, stack recommendations.

1. "Which one would you actually recommend to a friend, and why?" (the real answer, not the official one)
2. "Where do reviewers always get X vs Y wrong?"
3. "What's the thing about X that the marketing hides?"
4. "Which is worse than it looks? Which is better than it looks?"
5. "When would you recommend neither of these?"
6. "Who is the wrong person to ask about this comparison?"
7. "What breaks your opinion — what would have to be true for you to switch?"
8. "Which feature sounds important but doesn't matter in practice?"
9. "What's the gotcha in the pricing?"
10. "What's a better comparison nobody is making?"
11. "Which one did you quietly migrate away from, and why?"

The best question in this set is usually #10. If the user names a comparison that nobody else is writing about, you've found the article angle before you've even finished the interview.

## Thought leadership / opinion content

For contrarian takes, industry commentary, predictions, strategy posts.

1. "What's the contrarian take you've been holding back?"
2. "What's the conventional wisdom you used to believe that you no longer do?"
3. "What's everyone in your field wrong about right now?"
4. "Where do you think this is heading in 2 years?"
5. "What would have to happen for your opinion to change?"
6. "What's the unpopular prediction you're willing to put a number on?"
7. "Which authority in your field do you respect least, and why?"
8. "What's the taboo question nobody will answer directly?"
9. "What are you actively wrong about right now, and how do you know?"
10. "What would you do differently if you were starting today?"
11. "What's the thing you say to clients that you'd never say on LinkedIn?"

Question #9 is the most powerful and the hardest to get a good answer to. If you get one, the article writes itself. "What I'm wrong about" is the rarest genre in SEO content because most thought leadership is defensive.

## Case study / results content

For client stories, before/after posts, "we tried X for 90 days" content, growth reports.

1. "Start with the result number — what did it actually change?"
2. "What did you try first that didn't work?"
3. "At what point did you think it wouldn't work?"
4. "What was the unexpected thing you learned?"
5. "Who was the one person whose input mattered most?"
6. "What did you spend the most money on? The most time on?"
7. "What would you do differently next time?"
8. "Can you put a cost on the mistake?"
9. "What's the thing you can't publish publicly but it matters?"
10. "What was the moment you knew it was working?"
11. "What did the client actually say when you showed them the result?"

Question #9 is a signal question. Even if the user can't use the answer, it tells you where the real story is. Once you know the part that's unpublishable, you can ask "what's the most you can share about that?" and usually get 60% of the value.

## How to pick 2-4 questions from this bank

The bank has ~45 questions across four content types. You'll ask maybe three. How to pick:

1. **One contrarian-seeking question.** Always. This is what gives the final article an angle. The core question #1 ("what do most people get wrong about X?") is the safe default. If the user is opinionated, the thought-leadership bank has sharper versions.
2. **One specificity-forcing question.** Always. The core question #2 ("specific example, client, number") is the safe default. For case study topics, start with "what did it actually change?". For how-to topics, "what did you waste the most time on?" gets a specific story faster.
3. **One failure or scope question.** Always. Either "who should NOT follow this advice" (good for opinion and comparison content) or "what breaks at scale" (good for technical content) or "at what point did you think it wouldn't work" (good for case studies).
4. **Optional fourth question.** Only if the first three answers were short. A fourth question is a cost, not a benefit, if answers have been flowing. Stop when you have enough.

If you're not sure which category the topic falls into, default to the four core questions and skip the topic-specific ones. The core four work on almost any topic.

## When an answer is weak

Sometimes a user gives a vague answer. Don't move on. Vague answers can almost always be rescued by one well-placed follow-up. Patterns that work:

- User says "it depends on the situation": ask "what's the most recent situation where it applied?"
- User says "a few years ago": ask "can you remember which year?"
- User says "a client of ours": ask "what industry were they in? how big?"
- User says "most people": ask "who specifically? can you name one?"
- User says "a lot": ask "roughly how many? order of magnitude?"
- User says "it worked well": ask "what changed numerically?"

The goal is not to interrogate. The goal is to give the user a specific hook to remember a specific moment. Once they're in a specific memory, the details come out naturally.

## A note on follow-ups

Ask one question at a time. Wait for the answer. Follow up before asking the next question on the list. Quality of follow-ups matters more than quantity of initial questions.

The funnel method from qualitative research is the pattern to copy: broad question, then narrower probes that drill into whatever the user said, then move on. A typical good interview looks like:

- Q1 (broad): "What do most people get wrong about running a small SaaS support team?"
- Follow-up: "You said two people is a bad number — why specifically two?"
- Follow-up: "What happens at the handoff?"
- Follow-up: "Can you give me a number — how often did that happen?"
- Q2 (specific): "Walk me through the one time it broke worst."

That's five exchanges off one initial question. By the end you have a named failure mode with a number attached to it. That's more valuable than asking five different initial questions and getting five surface answers.

Standard follow-up probes that work on almost any answer:

- "Can you put a number on that?"
- "When was the last time that happened?"
- "What did you try before that worked?"
- "How did that compare to what you expected?"
- "Who else was involved?"
- "What would you do differently?"

If an answer is vague, keep probing. If an answer is specific, write it down verbatim and move on.

## Cross-reference

See `information-gain-writing.md` in this references folder for the theory behind why specificity in answers is what makes content unrankable by an AI. The short version: Google's Information Gain scoring compares your content against what the user has already seen on the topic. A named client or a real failure mode can't be in the other results, because nobody else has them. Generic opinions can. Your job in this interview is to extract the stuff that can't be anywhere else.

# Technique 03: Voice & Personality Injection

## What It Is

A system for injecting genuine human voice, personality, and specificity into AI-generated content. Removing AI patterns (Technique 02) is necessary but insufficient -- "sterile, voiceless writing is just as obvious as slop" (blader/humanizer). This technique adds the human qualities that make content engaging, trustworthy, and undetectable.

## Why It Works

AI content is detectable primarily because it regresses to the mean of all writing. A specific voice has specific word preferences, sentence rhythms, opinions, and reference domains that break the low-perplexity pattern. Voice injection also directly addresses Google's E-E-A-T "Experience" signal -- content with genuine personality signals a real author with real opinions.

Voice consistency is one of the strongest anti-AI-detection signals AND brand trust signals. Readers recognize when content "sounds different" -- it breaks trust. AI-generated content without voice injection sounds like every other AI-generated piece, which is detectable by both humans and algorithms.

Google's EEAT framework implicitly rewards voice consistency: content from a recognizable, consistent voice signals a real author with real expertise. Generic AI voice signals generic AI.

## Step-by-Step Process

### Step 1: Voice Sample Collection
1. Gather 3-5 real articles written by the brand's actual writer(s)
2. Include variety: a formal piece, a casual piece, a technical piece
3. Each sample should be 500-1,500 words minimum
4. These samples are the SINGLE most important input for quality output
5. **Capture negative examples too**: "We NEVER say 'leverage'" or "We NEVER use bullet points for everything" is just as important as positive guidelines

### Step 2: Voice Analysis
6. Analyze the samples for:
   - **Sentence length patterns**: Does the writer use short, punchy sentences? Long, flowing ones? A mix?
   - **Vocabulary level**: Technical jargon? Plain language? Industry-specific terms?
   - **Tone markers**: Humorous? Direct? Academic? Conversational? Provocative?
   - **Structural preferences**: Lists vs prose? Subheadings frequency? Paragraph length?
   - **Personal pronouns**: "We" (corporate)? "I" (personal)? "You" (direct address)?
   - **Opening style**: Start with a story? A statistic? A question? A bold statement?
   - **Transition style**: Formal ("Furthermore")? Conversational ("But here's the thing")?
   - **Quirks**: Any distinctive patterns? Parenthetical asides? Rhetorical questions? Specific metaphors?

### Step 3: Voice Profile Creation
7. Create a voice profile document with this structure:

```
VOICE PROFILE: [Brand Name]

Tone: [e.g., "Direct and slightly irreverent. Not afraid to call out bad advice."]
Register: [e.g., "Professional but conversational -- like explaining to a smart colleague"]
Perspective: [e.g., "First person plural ('we') for company content, first person singular ('I') for author-attributed pieces"]

DO: [e.g., "Use short paragraphs, ask rhetorical questions, include specific numbers"]
DON'T: [e.g., "Don't use corporate jargon, don't hedge everything, don't use emojis"]

Vocabulary preferences:
- Say "customers" not "clients"
- Say "build" not "develop"
- Say "test" not "validate"

Example phrases that capture the voice:
- "Here's the thing nobody talks about..."
- "We tested this. The results surprised us."
- "Skip the theory. Here's what actually works."
```

### Step 4: Voice Integration in Prompts
8. Include the voice profile in every writing prompt
9. Include 1-2 voice sample excerpts as few-shot examples
10. Instruct the model: "Write as if you ARE [writer name]. Match their sentence patterns, vocabulary, and tone exactly."
11. After generation, compare output against samples for voice drift

### Step 5: Voice Consistency Audit
12. Read the draft next to a real sample -- do they sound like the same person?
13. Check for AI voice bleeding through (formality spikes, generic transitions)
14. Verify vocabulary consistency (using the brand's specific terms)
15. Check opening and closing style matches the brand pattern
16. **Update samples regularly**: If the brand's voice evolves (it will), update the samples. Stale samples produce dated-sounding content.

## The 10 Voice Injection Techniques

### 1. Named Persona

**What:** Give the AI a specific writer identity with documented quirks, opinions, and speech patterns.

**Mechanism:** Forces the model away from the statistical mean. A specific voice has specific word preferences, sentence rhythms, and opinions that break predictability.

**Implementation:**
```
You are writing as [Name], a [role] who has been doing this for [X years].
They are known for: [specific trait, e.g., "blunt honesty about what doesn't work"]
They frequently reference: [domain, e.g., "cooking analogies to explain technical concepts"]
They dislike: [specific pet peeve, e.g., "vague advice without data"]
They would never say: [banned phrases specific to this persona]
Example of their voice: "[2-3 example sentences]"
```

**Not:** "Write in an engaging, conversational tone." This is too vague and produces generic "friendly" AI writing.

### 2. Burstiness Enforcement

**What:** Explicitly vary sentence length dramatically.

**Mechanism:** Directly addresses the low-burstiness detection signal. Humans naturally produce "bursts" of complexity followed by simple punchy lines.

**Implementation:**
```
Vary sentence length dramatically. Follow a long, complex sentence with
a short punchy one. Some paragraphs should be a single sentence. Others
should be five or six sentences. Never let three consecutive sentences
be similar in length. Mix 5-word fragments with 35-word complex sentences.
```

**Example transformation:**
- AI: "Email marketing remains one of the most effective digital marketing strategies available to businesses today. It provides a direct line of communication with potential customers. The return on investment is consistently high across industries."
- Human: "Email marketing works. Not in the vague, 'it's part of a balanced strategy' way consultants love. I mean: for every euro you spend, you get 36 back. That's DKG's 2025 data across 4,000 campaigns, and it's been consistent for five years running."

### 3. Specificity Over Generality

**What:** Replace every general claim with a specific example, number, name, date, or anecdote.

**Mechanism:** Specific details are high-entropy tokens that break predictability. They also signal E-E-A-T (Experience, Expertise) to Google.

**Implementation:**
```
Never write a general claim without a specific example. Instead of
"many companies struggle with this," write "When Coolblue's marketing
team hit this wall in Q3 2025, they..." Every abstraction must be
grounded in a concrete particular. If you don't have a real example,
make the specificity about the scenario: exact numbers, exact steps,
exact consequences.
```

**The "30% Rule":** At least 30% of every page should contain details no generic AI could produce: proprietary data, original analysis, first-hand testing results, specific case studies, or named examples.

### 4. Contrarian/Opinionated Writing

**What:** Take clear stances. Disagree with conventional wisdom when appropriate.

**Mechanism:** AI is trained via RLHF to be balanced and inoffensive. Strong opinions are high-entropy by definition. They also drive engagement (comments, shares, backlinks) which are ranking signals via NavBoost.

**Implementation:**
```
Take a strong position on every topic. Don't hedge with "it depends"
unless you genuinely mean it. If something is bad, say it's bad. If
the conventional wisdom is wrong, say so and explain why with evidence.
You are allowed to be wrong -- that's what makes you interesting.

When appropriate, include phrases like:
- "Here's what most guides get wrong about this..."
- "I've tested this and the data says the opposite..."
- "Everyone recommends X but in my experience Y works better because..."
```

### 5. Cultural References & Temporal Anchoring

**What:** Reference specific cultural moments, current events, or shared experiences.

**Mechanism:** Real cultural references signal an author who lives in the world. They create "information gain" that generic content cannot replicate. They anchor content in a specific time and place.

**Implementation:**
```
Reference specific cultural touchstones where relevant -- recent news,
industry events, widely-known examples. Not as decoration but as genuine
analogies that illuminate your point. Use references your target audience
would know. For Dutch audiences: reference Prinsjesdag, Black Friday NL,
specific Dutch companies, known media personalities, etc.
```

### 6. Show Don't Tell

**What:** Demonstrate claims through mini-narratives and scenarios instead of stating them.

**Mechanism:** "Telling" produces low-perplexity text ("Page speed affects rankings"). "Showing" produces high-perplexity, engaging text ("You click a search result. Three seconds pass. Still loading. You hit back. Google noticed.").

**Implementation:**
```
Never just state a fact. Show it through a brief scenario. Instead of
"page speed affects rankings," write a mini-narrative: "You click a
search result. Three seconds pass. The page is still loading. You hit
back and click the next result. Google tracked every millisecond of that
interaction -- and it just cost the slow site a ranking position."
```

### 7. Read-Aloud Test (Paul Graham Method)

**What:** Every sentence should sound natural when spoken aloud to a friend.

**Mechanism:** Paul Graham claims this puts you "ahead of 95% of writers." Conversational language has naturally higher burstiness, uses contractions, and avoids the formal register AI defaults to.

**Implementation:**
```
Write as if talking to a smart friend over coffee. Use contractions
(don't, isn't, won't). Start sentences with "And" or "But" when natural.
Drop unnecessary qualifiers. If you wouldn't say it out loud, rewrite it.

Test: read every paragraph back. If it sounds like a textbook, rewrite
it until it sounds like a person.
```

### 8. Strategic Imperfection

**What:** Include deliberate human markers -- fragments, parenthetical asides, self-corrections.

**Mechanism:** AI produces unnaturally perfect grammar and structure. Human writing has quirks that increase both burstiness and perplexity.

**Implementation:**
```
You are allowed to be imperfect. Use sentence fragments for emphasis.
Start sentences with conjunctions. Use parenthetical asides (like this)
when you have a tangential thought. Occasionally correct yourself
mid-paragraph ("well, actually..." or "that's not quite right --").
Real writers do this naturally.
```

### 9. Register Shifts

**What:** Shift between formal and casual register within the same piece.

**Mechanism:** AI maintains a uniform register. Humans naturally shift -- a technical explanation followed by a casual aside, a formal point followed by a joke.

**Implementation:**
```
Shift between registers naturally. After a technical paragraph,
drop in something casual. After making a serious point, add a human
aside. The contrast is what makes writing feel alive.

Example: "The algorithm processes 12 trillion signals per query.
(Yes, trillion. With a T. And it does this in under 0.5 seconds.
Makes you feel productive, doesn't it?)"
```

### 10. The Gary Halbert "One Person" Principle

**What:** Write to one specific person, not an audience.

**Mechanism:** "Write your copy as if you're having a conversation with one reader." Using "I" and "you" creates intimacy. Specific, seemingly irrelevant details build trust.

**Implementation:**
```
Write to one specific person who already cares about this topic.
Use "you" and "I" (or "we" for brand content). Include specific,
concrete details even when they seem tangential -- they build trust.
Don't persuade; serve. Imagine the reader is sitting across from
you at a table, asking a real question.
```

## Voice Document Structure

The writing skill should load a Voice Document (from your saved business context or user-provided) with this structure:

```markdown
## Brand Voice Profile

### Identity
- Writer role/title:
- Years of experience:
- Known for:
- Industry perspective:

### Voice Characteristics
- Formality level: [casual / conversational / professional / formal]
- Uses contractions: [yes / no]
- Uses humor: [yes / sparingly / no]
- Takes strong positions: [yes / sometimes / rarely]
- Sentence length tendency: [short and punchy / mixed / flowing]

### Reference Domains
- Analogies drawn from: [e.g., cooking, sports, construction]
- Cultural references: [e.g., Dutch media, tech industry, specific era]

### Pet Peeves (things this voice NEVER does)
- [e.g., "never says 'at the end of the day'"]
- [e.g., "never hedges when they have data"]
- [e.g., "never uses business jargon"]

### Example Paragraphs (2-3 samples of the target voice)
[Actual writing samples that demonstrate the voice]

### Audience
- Writing for: [specific person description]
- Their knowledge level: [beginner / intermediate / expert]
- What they care about: [specific concerns]
```

**Voice varies by channel**: A brand's blog voice differs from their product page voice differs from their social media voice. Capture voice per content type if possible. The voice document should indicate which register applies to which content format.

## Copywriting Frameworks by Content Type

| Content Type | Best Framework | Why |
|-------------|---------------|-----|
| Service pages, landing pages | PAS (Problem-Agitate-Solve) | Forces emotional engagement |
| Commercial content, reviews | AIDA (Attention-Interest-Desire-Action) | Drives decision-making |
| Brand content, about pages | StoryBrand | Positions reader as hero |
| News, definitions, how-tos | Inverted Pyramid | Answer first, expand second |
| Email-style, newsletters | Gary Halbert "One Person" | Maximum intimacy |
| Data pages, comparisons | David Ogilvy "Facts First" | Specifics over superlatives |

## Tips

- **The "swap test"**: Put a paragraph from the AI draft next to a paragraph from a real sample. If a colleague could tell which is which, the voice is not matched yet.
- **Capture negative examples too**: "We NEVER say 'leverage'" or "We NEVER use bullet points for everything" is just as important as positive voice guidelines. What the brand avoids defines the voice as much as what it does.
- **Voice varies by channel**: A brand's blog voice differs from their product page voice differs from their social media voice. Capture voice per content type.
- **Update samples regularly**: If the brand's voice evolves (it will), update the samples. Stale samples produce dated-sounding content.
- **The "30% Rule"**: At least 30% of every page should contain details no generic AI could produce.
- **Voice before anti-slop**: Apply voice injection BEFORE running anti-slop audits (Technique 02). Removing patterns without adding personality produces sterile text.

## Common Mistakes

1. **"Write engagingly"** -- too vague, produces generic friendly AI. Specify exact voice characteristics.
2. **Using generic voice descriptions**: "Professional and friendly" describes 90% of brands. Be specific: "Slightly sarcastic, data-obsessed, uses 'actually' a lot"
3. **Adding personality to every sentence** -- exhausting; let some sentences be plain
4. **Forcing humor** -- bad jokes are worse than no jokes
5. **Overusing fragments** -- occasional fragments add punch; constant fragments are a new AI pattern
6. **Fake specificity** -- inventing plausible-sounding but false examples is worse than being general
7. **Voice inconsistency** -- voice should be consistent throughout; load voice document before EVERY section
8. **Over-constraining**: Too many rules make writing stiff. Focus on 5-7 key voice markers, not 50
9. **Ignoring audience awareness**: The writer's voice adjusts to audience. A piece for CTOs sounds different than a piece for marketers, even in the same brand voice
10. **One voice for all content**: Product descriptions, thought leadership, and technical docs require different registers within the same brand voice

## Key Sources

- [Paul Graham: Write Like You Talk](https://paulgraham.com/talk.html)
- [Gary Halbert: The Boron Letters (Enchanting Marketing)](https://www.enchantingmarketing.com/gary-halbert-boron-letters/)
- [David Ogilvy's 7 Principles (Cult Method)](https://cultmethod.com/articles/ogilvys-principles/)
- [StoryBrand Framework](https://storybrand.com/)
- [blader/humanizer](https://github.com/blader/humanizer) -- "Sterile, voiceless writing is just as obvious as slop"
- [haowjy/creative-writing-skills](https://github.com/haowjy/creative-writing-skills) -- Style learning from samples
- [viktorbezdek/definitive-llm-writing-style-guide](https://github.com/viktorbezdek/definitive-llm-writing-style-guide)