Content Creation Process

There is one production process that produces content that ranks: Research, Structure, Write, Optimize. Skip a phase or do them in the wrong order, and you’ll spend three times as long fixing the draft as you would have spent producing it correctly.

TL;DR

Research is half the work. Read the entire top 10 SERP, the People Also Ask, the AI Overview if present, and at least three primary sources before you write a sentence. Skipping this stage is why most articles read like book reports of other articles.
Structure before prose. The outline must be ratified before drafting; the outline is what wins or loses the page. Every H2 should map to a query, an entity, or a SERP feature you’re chasing.
Optimize after writing, not during. Drafting for keyword density produces brittle prose. Drafting for clarity, then sweeping for entity coverage and readability, produces content that ranks and converts.

The mental model

Content production is like film production: pre-production (research) is where the project succeeds or fails, principal photography (writing) is shorter than people expect, and post-production (optimization) is where rough work becomes shippable. Skip pre-production and you’ll be reshooting in post; skip post and your perfectly shot scene never reaches the audience.

The four phases map to specific deliverables:

Research produces a research dossier — a single document with SERP notes, primary-source links, quote candidates, and the gaps you’ve identified.
Structure produces a ratified outline — H1, H2s, H3s, opening hook, closing CTA, internal-link targets — that an editor signs off on before drafting begins.
Write produces a first draft against the outline. The writer’s job is prose quality and original insight, not keyword placement.
Optimize produces the publish-ready article: entity sweep, readability pass, schema markup, internal links, image alt text, CTA placement.

Most amateur teams do all four simultaneously, in real time, in the same Google Doc. Professional teams gate each phase and don’t enter the next until the prior is signed off.

Deep dive: the 2026 reality

The 2026 SERP is not the 2018 SERP. A first-page result now competes with:

An AI Overview (powered by Gemini 2.0 in Google AI Search) that synthesizes the top results into a 100–300 word answer above the organic listings
An AI Mode conversational pane that the user may bounce in and out of
A PAA accordion that has expanded to 8–12 questions deep
People Also Search For chips
Often a Reddit result in positions 2–4 that didn’t exist there a year ago

Research therefore must include the AI Overview itself. If the Overview already answers the query in 200 words, you need to bring something the Overview can’t: original data, an opinionated take, an updated date, a video, an interactive tool, or a level of depth the synthesis can’t replicate. Pretending the Overview isn’t there is how teams waste $4,000 on a piece that gets 60 clicks.

Word count reality: the median ranking page in 2026 is shorter than it was in 2020. Google’s data on user satisfaction shows long pages have higher pogo-stick rates on informational queries. Backlinko’s 2024 analysis pegged the median first-page result at 1,447 words; in commodity B2B SaaS, top results often sit at 800–1,200. The “long content wins” myth was mostly correlation: long content was written by more invested teams. The correlation broke once everyone wrote long content and Google’s quality models adapted.

Readability measurement is non-negotiable. Use Hemingway Editor and target Grade 8 or below for consumer content, Grade 11 or below for technical content. Aim for Flesch Reading Ease ≥60 for general readers. The 2024 update to Google’s Quality Rater Guidelines explicitly added “needlessly complex” as a low-quality signal. Long sentences, passive voice, and jargon all hurt.

AI-assisted writing is now standard. The line is: AI for scaffolding, humans for substance. Acceptable: using Claude, GPT-4o, or Gemini to generate outline drafts, summarize SERP results, and rewrite paragraphs for clarity. Unacceptable: copy-pasting a prompt output into a CMS. The Helpful Content system, AI Overviews ranker, and Originality.ai detector all penalize undifferentiated AI output (“AI slop”). The signal isn’t “this was written by AI”; it’s “this article contains nothing the AI didn’t already know.” Original data, expert quotes, and primary observations are the difference.

For AI surfaces specifically: GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, and Google-Extended all favor pages with concrete, citable claims. “According to a 2025 SparkToro study of 12,847 emails, subject lines under 41 characters had a 22% higher open rate” gets cited; “subject lines should be short” does not.

Visualizing it

flowchart LR
  R["Research<br/>40 percent of time"] --> S["Structure<br/>15 percent of time"]
  S --> W["Write<br/>30 percent of time"]
  W --> O["Optimize<br/>15 percent of time"]
  R --> R1["SERP top 10"]
  R --> R2["AI Overview text"]
  R --> R3["3+ primary sources"]
  S --> S1["H2 = query or entity"]
  S --> S2["Editor sign-off"]
  W --> W1["Prose quality"]
  W --> W2["Original claims"]
  O --> O1["Entity sweep"]
  O --> O2["Schema + links"]

Bad vs. expert

The bad approach

The amateur opens a blank document and starts writing.

# Best Email Subject Line Length

Email subject lines are really important. They're the first thing your subscribers see, and they can make or break your open rate. In this post, I'll talk about the best email subject line length and give you tips for writing great subject lines.

## Why Subject Lines Matter

Your subject line is the first impression. If it's bad, no one opens your email...

## Tips for Great Subject Lines

1. Keep it short
2. Use personalization
3. Create urgency
4. A/B test

The intro is filler. Each H2 is generic. There’s no original data, no entity coverage, no specific number, no quote, no link to a primary source. This article competes with 4,000 identical articles and a 200-word AI Overview that already answers the question.

The expert approach

The professional starts with a research dossier.

# Research dossier: best email subject line length

## SERP top 5 (2026-05-07, US, incognito)
1. mailchimp.com — 1,420 words, dated 2025-09 — claims 41-char target
2. campaignmonitor.com — 1,180 words, dated 2024-11 — claims 28-39 chars
3. litmus.com — 2,100 words, original 10k-email study, dated 2025-03 — 41-50 chars
4. hubspot.com — 1,500 words, dated 2025-07 — generic
5. reddit.com r/marketing — thread, 280 comments, anecdotal but cited often

## AI Overview (already present)
Synthesizes Litmus + Mailchimp data; 110 words; cites Litmus.

## Primary sources
- Litmus 2025 State of Email — original study, 10,084 emails
- MailChimp Benchmarks 2025 — 26B emails, segmented by industry
- Gmail mobile preview cuts at ~33-43 chars depending on device

## Entities required
open rate, preview text, Gmail clipping, mobile, A/B test, character count

## Original angle
We analyzed 47,512 emails from our own customers from Jan-Apr 2026. Median
length of top quartile by open rate: 38 chars. Median of bottom quartile:
67 chars. Mobile-clipped subjects had 31% lower open rate.

Then the outline.

# Outline (ratified by editor 2026-05-08)

H1: Best email subject line length: data from 47,512 emails (2026)
H2: The short answer (target: featured snippet paragraph, 40-60 words)
H2: What our 47,512-email analysis shows (original chart)
H2: Why 41 characters? Gmail and Apple Mail mobile clipping
H2: Subject line length by industry (table from MailChimp 2025)
H2: When to break the rule (long subject lines that work)
H2: How to test your own subject line length (link to /email/ab-testing/)
FAQ schema block: 4 PAA questions
Internal links: /email/preview-text/, /email/ab-testing/, /email/deliverability/

Then the draft, then the optimization sweep. The article ships with original data, schema markup, three internal links, a chart, and a featured-snippet-shaped paragraph in the second H2.

Phase	Bad	Expert
Research	Skim two competitors	SERP top 10, AI Overview, 3+ primary sources
Structure	Generic H2s	H2s mapped to queries, entities, SERP features
Write	Keyword stuffing	Prose quality + original claims
Optimize	”Add the keyword 5 times”	Entity sweep, readability check, schema, links

Do this today

Create a research dossier template in Notion or Google Docs with sections for SERP top 10, AI Overview text, PAA, primary sources, entities, original angle, and competitor weaknesses. Save it as a reusable template.
For your next article, run the target query in incognito Chrome with location and language set to your audience. Screenshot the AI Overview if present and paste the text into the dossier. This is non-negotiable.
Use Ahrefs Keywords Explorer > Matching terms > Questions to harvest 20+ user questions related to your target query. Pick the 4–6 you’ll answer in your article.
Read the top 3 ranking pages end-to-end (not skim). Note word count, dated last updated, original data they cite, and the H2 structure. Tools: SEOQuake browser extension shows word count instantly.
In Hemingway Editor (hemingwayapp.com), drop in your draft when finished. Target Grade 8 for consumer content, Grade 11 for technical. Rewrite any sentence flagged red.
Run your draft through Surfer SEO Content Editor or Frase for entity coverage scoring. Target 80%+ entity match against the top-10 SERP composite. Add missing entities only where they fit naturally — never as keyword stuffing.
Generate schema markup with the Schema App generator or hand-write Article + FAQPage schema. Validate at validator.schema.org then Rich Results Test at search.google.com/test/rich-results.
Add 3–5 contextual internal links from the new article to existing related pages, and identify 2–3 existing pages that should link to the new one. Update those existing pages.
If you used AI for any drafting, run the final text through Originality.ai. Anything above 60% AI-pattern requires a human pass for substance: add original claims, specific numbers, named sources, opinionated takes.
Set a 90-day calendar reminder for every published article to check Google Search Console > Performance > Page for that URL. If it hasn’t earned position 1–10 for the target query in 90 days, queue it for a refresh per Module 17.