
Seo Writer
- 10 installs
- 30 repo stars
- Updated July 7, 2026
- jeffallan/writing-with-agents
Adds search-aware decisions across writing: search-intent analysis, keyword-to-heading mapping, featured-snippet targeting, E-E-A-T, and on-page validation.
About
Integrates SEO into the planning, drafting, and validation phases via intent classification, keyword-to-heading mapping, and snippet targeting. A writer uses it when content needs organic search visibility or an existing article underperforms.
- Cross-cutting SEO across Architect, Carpenter, and Judge phases
- Search-intent, keyword-heading mapping, featured-snippet and E-E-A-T guidance
Seo Writer by the numbers
- 10 all-time installs (skills.sh)
- +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #1,523 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jeffallan/writing-with-agents --skill seo-writerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 30 |
| Last updated | July 7, 2026 |
| Repository | jeffallan/writing-with-agents ↗ |
What it does
Adds search-aware decisions across writing: search-intent analysis, keyword-to-heading mapping, featured-snippet targeting, E-E-A-T, and on-page validation.
Files
Role Definition
The SEO Writer is the search optimization integration specialist. This is a cross-cutting skill that provides SEO guidance during the Architect (planning), Carpenter (execution), and Judge (validation) phases. It does not replace those phases -- it augments them with search-aware decisions.
Lead: AI analyzes search intent, maps keywords, and runs SEO validation. Support: Human confirms keyword targets, approves heading architecture, and decides trade-offs between readability and optimization.
The SEO Writer understands search intent classification, keyword-to-heading mapping, heading architecture for crawlability, featured snippet targeting patterns, and E-E-A-T signals. It applies these across the writing workflow rather than as an afterthought bolted onto a finished draft.
When to Use This Skill
- When the content goal includes organic search visibility
- When you need to analyze search intent before planning content structure
- When mapping keywords to headings during the Architect phase
- When targeting featured snippets or People Also Ask boxes
- When integrating keywords naturally during the Carpenter phase
- When writing or reviewing meta elements (title tags, meta descriptions, URL slugs)
- When running SEO validation during the Judge phase
- When auditing existing content for on-page SEO gaps
- When consolidating multiple thin pages into a single authoritative resource
- When a published article is underperforming in search and needs diagnostic analysis
- When planning internal linking strategy across a content cluster
Core Workflow
1. Analyze Search Intent and SERP Landscape -- Classify the target query as informational, navigational, commercial, or transactional. Run the SERP analysis checklist to understand what content format dominates, what subtopics are table stakes, and where opportunity gaps exist. See references/search-intent-analysis.md.
2. Architect Phase: Map Keywords to Structure -- During the Architect phase, map primary and secondary keywords to specific headings. Plan which headings target People Also Ask questions. Identify featured snippet opportunities and assign snippet formats (paragraph, list, table) to specific sections. See references/keyword-mapping.md.
3. Carpenter Phase: Integrate and Enrich -- During the Carpenter phase, integrate keywords naturally into prose. Write the primary keyword into the first 100 words, H1, and conclusion. Use semantic variations throughout to avoid repetition. Write meta elements (title tag, meta description, URL slug). Add content enrichment elements: comparison tables, definition paragraphs, numbered steps, and key takeaway callouts. See references/snippet-targeting.md.
4. Judge Phase: Validate SEO Elements -- During the Judge phase, run the full SEO validation checklist. Check on-page elements, keyword placement density, content quality signals, heading hierarchy, featured snippet optimization, and E-E-A-T signals. Flag issues by severity. See references/seo-validation-checklist.md.
5. Deliver SEO Report -- Produce a structured SEO report covering on-page element status, keyword placement audit, content enrichment inventory, featured snippet readiness, and optimization recommendations. Present to the human for review before finalizing.
Reference Guide
| Topic | Reference | Use When |
|---|---|---|
| Search Intent and SERP Analysis | references/search-intent-analysis.md | Classifying queries, analyzing SERP landscape, choosing content format |
| Keyword Mapping and Heading Architecture | references/keyword-mapping.md | Mapping keywords to headings, building SEO-aware outlines |
| Featured Snippet Targeting and Content Enrichment | references/snippet-targeting.md | Targeting snippets, writing meta elements, enriching content |
| SEO Validation Checklist | references/seo-validation-checklist.md | Running the full validation pass during Judge phase |
| Content Type Formats and Common Mistakes | references/seo-content-types.md | Choosing format by content type, avoiding SEO anti-patterns |
Constraints
MUST DO:
- Match content format to the dominant search intent for the target query.
- Integrate keywords naturally -- every keyword placement must read as if it belongs.
- Validate heading hierarchy (H1 > H2 > H3, no skipped levels).
- Run SERP analysis before making structural decisions.
- Write meta elements (title tag, meta description, URL slug) for every SEO piece.
- Check E-E-A-T signals: specificity, first-hand experience, credible sources.
- Include content enrichment elements (tables, definition paragraphs, key takeaway callouts) in every SEO piece.
MUST NOT DO:
- Force keywords into awkward or unnatural sentences.
- Stuff keywords -- if density feels noticeable to a reader, it is too high.
- Sacrifice readability for SEO. Write for the reader first, optimize second.
- Skip SERP analysis and assume a content format.
- Use vague headings like "Introduction" or "Conclusion" that waste heading real estate.
- Treat SEO as a post-draft checklist. Integrate it from the Architect phase forward.
- Optimize for keywords that do not match the content's actual subject matter.
- Duplicate meta descriptions or title tags across multiple articles in a content cluster.
- Ignore heading hierarchy violations -- H1 to H3 with no H2 confuses crawlers and screen readers.
- Optimize for search volume alone without considering keyword difficulty and domain authority match.
Output Templates
SEO Report
# SEO Report: [Article Title]
## Target Query
Primary keyword: [keyword]
Search intent: [informational / navigational / commercial / transactional]
## On-Page Elements
- Title tag (50-60 chars): [title]
- Meta description (150-160 chars): [description]
- URL slug: [slug]
- H1: [heading]
## Keyword Placement Audit
- [ ] Primary keyword in first 100 words
- [ ] Primary keyword in H1
- [ ] Secondary keywords mapped to H2 headings
- [ ] Semantic variations used throughout
- [ ] No keyword stuffing detected
## Featured Snippet Targets
[Section]: [snippet type] -- [status]
## Recommendations
[Prioritized list of optimization actions]Knowledge Reference
This skill applies search engine optimization principles as a cross-cutting concern across the Madman-Architect-Carpenter-Judge writing workflow. Rather than treating SEO as an afterthought, it integrates keyword research, heading architecture, and content enrichment decisions into the planning, writing, and validation phases where they have the most impact. Reference documents in the references/ directory provide detailed procedures for search intent analysis, keyword mapping, snippet targeting, validation checklists, and content type guidance.
Search intent classification is the foundation of every SEO decision in this skill. The four intent types -- informational, navigational, commercial, and transactional -- determine content format, heading structure, and enrichment strategy. Misclassifying intent produces content that ranks for the wrong queries or fails to match user expectations even when it ranks correctly. SERP analysis validates the classification by examining what content formats currently dominate the results page for the target query.
E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness) are integrated rather than bolted on. Specificity of examples demonstrates experience. Depth of technical explanation demonstrates expertise. Citation of credible sources demonstrates authoritativeness. Transparent methodology demonstrates trustworthiness. These signals emerge naturally from good writing practice when the Madman and Carpenter phases are executed well. The SEO Writer's role is to verify their presence, not to fabricate them.
Featured snippet targeting requires format-specific optimization. Paragraph snippets need a concise 40-60 word definition or answer directly following the target heading. List snippets need clean ordered or unordered lists with consistent formatting. Table snippets need structured comparison data with clear column headers. The snippet format must match the query type: "what is" queries pull paragraph snippets, "how to" queries pull list snippets, and comparison queries pull table snippets.
Heading architecture serves both readers and crawlers. Every H2 should map to a secondary keyword or a People Also Ask question. Headings that waste real estate on generic labels like "Introduction" or "Conclusion" miss the opportunity to signal topical relevance. The heading hierarchy must be strictly sequential (H1 to H2 to H3) with no skipped levels, which also benefits accessibility and screen reader navigation.
Keyword Mapping and Heading Architecture
Keyword Plan Template
Before writing or structuring content, complete the keyword plan. This plan maps directly to the Architect blueprint and informs every heading decision.
## Keyword Plan
### Primary Keyword
- Keyword: [exact phrase]
- Search volume: [monthly estimate or range]
- Search intent: [informational / navigational / commercial / transactional]
- Difficulty: [low / medium / high]
### Secondary Keywords
Map each secondary keyword to a specific heading.
| Secondary Keyword | Target Heading | Heading Level |
|---|---|---|
| [keyword phrase] | [planned heading text] | H2 |
| [keyword phrase] | [planned heading text] | H2 |
| [keyword phrase] | [planned heading text] | H2 |
| [keyword phrase] | [planned heading text] | H3 |
### Semantic / LSI Keywords
These are related terms and variations to weave throughout the body text.
They do not need dedicated headings -- they provide topical coverage.
- [semantic term 1]
- [semantic term 2]
- [semantic term 3]
- [semantic term 4]
- [semantic term 5]
### People Also Ask Targets
Questions to answer in the content, sourced from SERP analysis.
| PAA Question | Section Placement | Snippet Format |
|---|---|---|
| [question from SERP] | [heading or FAQ section] | [paragraph / list / table] |
| [question from SERP] | [heading or FAQ section] | [paragraph / list / table] |
| [question from SERP] | [heading or FAQ section] | [paragraph / list / table] |Heading Architecture Rules
Headings serve two audiences simultaneously: readers scanning for relevance and search engines parsing content structure. Every heading must work for both.
Rule 1: One H1 Per Page
The H1 is the page title. It contains the primary keyword. Keep it between 50 and 60 characters. There is exactly one H1 per page -- no exceptions.
The H1 should be specific enough that a reader knows exactly what the page covers without reading anything else.
Weak H1: "A Guide to Authentication" Strong H1: "OAuth 2.0 Authentication: How It Works and When to Use It"
Rule 2: H2 Sections Target Secondary Keywords or PAA Questions
Each H2 heading represents a major section of the content. Map secondary keywords to H2 headings so that each major section targets a distinct search sub-query.
When a People Also Ask question aligns with a section, use the question (or a close variation) as the H2. This directly targets featured snippet selection for that question.
Example mapping:
- H1: "OAuth 2.0 Authentication: How It Works and When to Use It"
- H2: "What Is OAuth 2.0?" (PAA question, informational secondary keyword)
- H2: "How OAuth 2.0 Authorization Flows Work" (secondary keyword: "OAuth 2.0 authorization flows")
- H2: "OAuth 2.0 vs API Keys: When to Choose Which" (secondary keyword: "OAuth 2.0 vs API keys")
Rule 3: H3 Subsections Only When Genuinely Needed
Use H3 headings only when an H2 section has distinct sub-parts that benefit from their own headings. Do not add H3 headings just to break up text or to hit a keyword -- that is keyword stuffing through structure.
A good test: if you removed the H3 and merged its content into the parent H2 section, would the section be harder to scan? If yes, keep the H3. If no, remove it.
Rule 4: Never Skip Heading Levels
The hierarchy must be sequential: H1 to H2 to H3. Never jump from H1 to H3 or from H2 to H4. Skipped levels break the document outline for both screen readers and search engines.
CORRECT:
H1: Main Title
H2: First Major Section
H3: Subsection
H2: Second Major Section
INCORRECT:
H1: Main Title
H3: Subsection (skipped H2)
H2: Section
H4: Sub-subsection (skipped H3)Rule 5: Headings Are Signposts, Not Vague Labels
Every heading should tell the reader what they will learn in that section. Vague headings waste the heading's dual role as a navigation aid and a keyword signal.
| Vague Heading | Specific Heading |
|---|---|
| Introduction | Why OAuth 2.0 Replaced OAuth 1.0 |
| Background | The Problem with Password-Based API Authentication |
| Details | How the Authorization Code Flow Works Step by Step |
| Conclusion | When to Choose OAuth 2.0 Over Simpler Alternatives |
Rule 6: Headings Tell a Story Read Top to Bottom
Read your headings in sequence without any body text. They should form a coherent outline that tells the story of the piece. If the headings read as a disconnected list of topics, the structure needs work.
Disconnected headings:
- What Is OAuth?
- Grant Types
- Security
- Implementation
Story-driven headings:
- What Is OAuth 2.0 and Why Does It Exist?
- The Four Grant Types and When to Use Each
- Security Risks You Must Handle in Production
- Implementing OAuth 2.0 in Your Application
Mapping Keywords to the Architect Blueprint
When working with the Architect skill, integrate the keyword plan directly into the blueprint. Each section in the blueprint should note:
1. Primary or secondary keyword assigned to the section heading 2. Semantic keywords to weave into the section body 3. PAA question the section answers (if applicable) 4. Snippet target and format (paragraph, list, or table)
This ensures the Carpenter phase has clear keyword guidance per section rather than a vague instruction to "include keywords throughout."
Search Intent Analysis
The Four Search Intents
Every search query falls into one of four intent categories. Matching your content format to the correct intent is the single most important SEO decision. A perfectly optimized page targeting the wrong intent will not rank.
| Intent | Searcher Wants | Content Format | Example Query |
|---|---|---|---|
| Informational | Learn or understand | Guide, explainer, tutorial | "what is OAuth 2.0" |
| Navigational | Find a specific page | Landing page, docs | "Stripe API documentation" |
| Commercial | Compare before deciding | Comparison, review, list | "best CI/CD tools 2026" |
| Transactional | Take action | Product page, CTA-driven | "buy SSL certificate" |
Identifying Intent from a Query
Informational signals: "what is," "how to," "why does," "guide to," "explained." The searcher wants to learn. They are not ready to buy or compare.
Navigational signals: Brand names, product names, specific page references. The searcher knows where they want to go and is using Google as a shortcut.
Commercial signals: "best," "vs," "review," "comparison," "top," "alternatives." The searcher is evaluating options. They want structured comparison, not a sales pitch.
Transactional signals: "buy," "pricing," "discount," "sign up," "download," "free trial." The searcher is ready to act. They want a clear path to conversion.
Mixed Intent Queries
Some queries blend intents. "best project management tool" is commercial (comparing options) with a transactional undertone (the searcher will eventually buy). In these cases, lead with the dominant intent and layer in the secondary.
SERP Analysis Checklist
Before writing or structuring any content, analyze the current search results for your target query. The SERP tells you what Google already considers a good answer.
1. Content Format Dominance
What format dominates the top 10 results? If 8 of 10 results are listicles, writing a narrative essay is fighting the format. Match the dominant format or have a compelling reason to deviate.
Formats to check for:
- Long-form guides (2,000+ words)
- Listicles ("10 best..." / "7 ways to...")
- Tutorials with steps
- Comparison tables
- Product pages
- Video results
- Tool/calculator pages
2. Average Word Count
Estimate the word count of the top 3-5 ranking pages. This gives you a floor, not a ceiling. Your content should be at least as comprehensive as what already ranks, but longer is not automatically better. Depth and usefulness beat length.
3. Table-Stakes Subtopics
Identify subtopics that appear in most top-ranking pages. These are table stakes -- your content must cover them to be considered comprehensive. If every top result covers "security considerations" and yours does not, you have a coverage gap.
4. Opportunity Gaps
Identify subtopics, angles, or depth levels that NO top-ranking page covers well. These are your differentiation opportunities. A gap might be:
- A subtopic mentioned but not explained
- An outdated section in competitor content
- A missing use case or audience segment
- An absence of original data, examples, or experience
5. Featured Snippet Analysis
Check if a featured snippet appears for the query. If it does:
- What format is it? (paragraph, list, table)
- Which page owns it?
- Can you provide a better answer in the same format?
If no featured snippet exists, there is an opportunity to claim one. Structure your content to trigger snippet selection.
6. People Also Ask (PAA)
Record the People Also Ask questions that appear. These are direct signals of related queries searchers care about. Each PAA question is a candidate for:
- An H2 heading in your content
- A FAQ section
- A standalone content piece if the topic is deep enough
7. Reading Level
Assess the reading level of top-ranking content. If competitors write at a 9th-grade level, writing at a graduate level may hurt engagement. Match or slightly simplify the reading level of successful content for your audience.
Using the Analysis
After completing the SERP analysis checklist, you should have clear answers to:
1. What format should this content take? (Matches dominant format or fills a gap) 2. How long should it be? (Meets the comprehensiveness floor) 3. What must it cover? (Table-stakes subtopics) 4. How will it differentiate? (Opportunity gaps) 5. Are there snippet opportunities? (Format and targeting plan) 6. What related questions should it answer? (PAA integration) 7. What reading level should it target? (Audience-appropriate complexity)
Feed these answers into the Architect phase. They inform heading structure, section planning, and content depth decisions.
SEO Content Types and Common Mistakes
Format Guidance by Content Type
Choose the content format based on search intent analysis and SERP format dominance. Each content type has structural patterns that search engines expect.
| Type | Length | Structure | Keyword Pattern |
|---|---|---|---|
| Pillar page | 2,500-5,000 words | Deep coverage, many H2/H3, heavy internal links | Broad head term |
| How-to / tutorial | 1,500-3,000 words | Numbered steps, prerequisites, troubleshooting | "how to [verb] [noun]" |
| Comparison | 1,500-2,500 words | Comparison table + analysis per option | "[X] vs [Y]", "best [category]" |
| FAQ / knowledge base | 1,000-2,000 words | Questions as headings, concise answers | "what is", "how does", "why" |
| Case study | 1,000-2,500 words | Situation-Challenge-Solution-Results | "[solution] case study" |
Pillar Page
A pillar page is the definitive resource for a broad topic. It covers every major subtopic at sufficient depth and links to more detailed pages on each subtopic.
Structure pattern:
- H1: Broad topic keyword
- H2: Each major subtopic (8-15 sections)
- H3: Sub-points within complex subtopics
- Internal links to cluster pages for each subtopic
- Table of contents at the top
Keyword strategy: Target a competitive head term (e.g., "OAuth 2.0") and use the pillar page to build topical authority. Secondary keywords go to cluster pages that link back.
How-To / Tutorial
A how-to page walks the reader through a process. It targets informational and transactional intent from searchers who need to accomplish a specific task.
Structure pattern:
- H1: "How to [Verb] [Noun]" with primary keyword
- Brief intro: What this tutorial covers and who it is for
- Prerequisites section (if applicable)
- Numbered steps as H2 headings or an ordered list
- Troubleshooting section for common problems
- Summary or next steps
Keyword strategy: Target long-tail "how to" phrases. These have clear intent and high conversion to engagement because the reader needs to complete a task.
Comparison
A comparison page helps the reader evaluate options. It targets commercial intent from searchers who are deciding between alternatives.
Structure pattern:
- H1: "[X] vs [Y]" or "Best [Category] in [Year]"
- Overview comparison table near the top
- H2: Dedicated section for each option
- H2: Direct comparison on key criteria
- H2: Recommendation by use case ("Choose X if... Choose Y if...")
Keyword strategy: Target "[X] vs [Y]" and "best [category]" queries. Include both option names in headings. The comparison table targets table snippets.
FAQ / Knowledge Base
FAQ content answers specific questions directly. It targets informational intent and is structured to win featured snippets and PAA boxes.
Structure pattern:
- H1: Topic overview keyword
- H2: Each question, phrased as searchers ask it
- Answer immediately follows each H2 (40-60 words for snippet targeting, then expanded detail)
- Questions ordered from most fundamental to most advanced
Keyword strategy: Target question-based queries ("what is," "how does," "why"). Use exact question phrasing in H2 headings to maximize snippet eligibility.
Case Study
A case study demonstrates results through a specific example. It targets commercial intent and builds E-E-A-T through demonstrated experience.
Structure pattern:
- H1: "[Solution] Case Study: [Result or Company]"
- H2: The Situation (context and starting conditions)
- H2: The Challenge (specific problem to solve)
- H2: The Solution (what was implemented and why)
- H2: The Results (quantified outcomes)
- H2: Key Takeaways
Keyword strategy: Target "[solution] case study" and "[solution] results" queries. Include specific numbers in headings when possible.
Common SEO Writing Mistakes
These mistakes are frequent in AI-assisted content and will hurt both rankings and reader trust.
| Mistake | Why It Hurts | Fix |
|---|---|---|
| "In today's digital landscape..." | Signals generic AI content to readers and reviewers. Google's helpful content system penalizes generic, mass-produced text. | Start with a specific claim, statistic, or concrete scenario that demonstrates expertise. |
| Keyword in every paragraph | Unnatural density triggers spam signals. Readers notice and lose trust. Search engines detect over-optimization. | Use semantic variations and related terms. The primary keyword should appear 3-5 times in a 2,000-word piece, not 20 times. |
| Headers like "Introduction" | Wastes heading real estate on a word with zero search value. Provides no navigation signal to readers or crawlers. | Make every heading specific and keyword-aware. Replace "Introduction" with a heading that states the section's actual topic. |
| Thin sections (1-2 sentences) | Signals incomplete coverage. Search engines interpret thin sections as a sign the content is not genuinely helpful. | Merge thin sections with related content or expand with evidence, examples, or practical detail. Minimum 3-4 sentences per section. |
| No original perspective | Provides no ranking advantage over existing content. Google's helpful content system rewards content with unique value. | Add first-hand experience, unique data, contrarian analysis, or practical examples that competitors do not have. |
| Writing for engines not readers | High bounce rate and low engagement signals. Users who arrive and immediately leave tell search engines the content did not satisfy intent. | Write for the reader first, then optimize for search. If a sentence feels awkward because of a keyword, rewrite it for readability. |
Additional Anti-Patterns to Avoid
Orphan content: Pages with no internal links pointing to them. Search engines discover and value pages partly through internal link structure. Every page should have at least 2-3 internal links from other pages.
Duplicate title tags: Multiple pages with the same title tag compete against each other. Every page needs a unique title tag targeting a distinct keyword.
Missing alt text on images: Images without alt text are invisible to search engines. Write alt text that describes the image content and includes a relevant keyword when natural.
Ignoring page speed: Content quality is irrelevant if the page loads slowly. Large uncompressed images, render-blocking scripts, and excessive third-party requests harm both rankings and user experience.
Neglecting mobile structure: Over 60% of searches happen on mobile devices. Content must be readable on small screens: short paragraphs, adequate font size, tappable links, and no horizontal scrolling.
SEO Validation Checklist
Run this checklist during the Judge phase after the Carpenter has delivered a complete draft. Every item is a pass/fail check. Flag failures by severity: must-fix (will hurt ranking) or review (optimization opportunity).
Full SEO Validation Report Template
# SEO Validation Report: [Article Title]
Date: [date]
Target keyword: [primary keyword]
Search intent: [informational / navigational / commercial / transactional]
Word count: [n]
## On-Page Elements
- [ ] Title tag present and 50-60 characters
- [ ] Title tag contains primary keyword near the front
- [ ] Title tag is unique (not duplicated on site)
- [ ] H1 present and matches or closely mirrors title tag
- [ ] H1 contains primary keyword
- [ ] Meta description present and 150-160 characters
- [ ] Meta description contains primary keyword naturally
- [ ] Meta description describes value, not just topic
- [ ] URL slug is short, hyphenated, and contains primary keyword
## Keyword Placement
- [ ] Primary keyword appears in the first 100 words
- [ ] Primary keyword appears in at least one H2 heading
- [ ] Primary keyword appears in the conclusion or final section
- [ ] Secondary keywords are mapped to specific H2 headings
- [ ] Semantic variations are used throughout the body text
- [ ] No keyword stuffing detected (keyword reads naturally in every instance)
- [ ] Keyword density does not exceed 1-2% for the primary keyword
## Content Quality Signals
- [ ] Content is comprehensive: covers all table-stakes subtopics from SERP analysis
- [ ] Content is differentiated: includes at least one angle competitors miss
- [ ] Content is accurate: claims are supported by evidence, data, or examples
- [ ] Content is current: no outdated information, references, or screenshots
- [ ] Content is actionable: reader can apply what they learned
- [ ] Content is original: includes unique perspective, data, or experience
## Structure and Readability
- [ ] Heading hierarchy is valid (H1 > H2 > H3, no skipped levels)
- [ ] Headings are specific and keyword-aware (no vague labels)
- [ ] Headings read as a coherent story top to bottom
- [ ] Paragraphs are 2-4 sentences (no walls of text)
- [ ] Reading level matches target audience (check against SERP analysis)
- [ ] Visual breaks present: tables, lists, code blocks, or callouts every 300-400 words
## Featured Snippet Optimization
- [ ] Definition paragraphs (40-60 words) follow relevant H2 headings
- [ ] How-to steps are formatted as numbered lists immediately after H2
- [ ] Comparison data is presented in tables immediately after H2
- [ ] FAQ-style questions are used as headings where appropriate
- [ ] Snippet-target content directly answers the heading question without preamble
## E-E-A-T Signals
- [ ] Expertise demonstrated through technical specificity (not generic advice)
- [ ] First-hand experience visible: real examples, case references, specific numbers
- [ ] Sources are credible: links to authoritative references, not thin content
- [ ] Practical knowledge evident: content solves a real problem, not just explains a concept
- [ ] No excessive hedging: "might," "could," "it depends" used only when genuinely warranted
- [ ] Author context present: bio, credentials, or relevant experience referenced (if applicable)
## Schema Markup Recommendation
Based on the content type, recommend the appropriate schema:
| Content Type | Recommended Schema |
|---|---|
| How-to / Tutorial | HowTo schema |
| FAQ content | FAQPage schema |
| Article / Guide | Article schema |
| Product review | Review schema |
| Comparison | Article schema with itemReviewed |
Recommended schema for this piece: [schema type]
Reason: [brief justification based on content type and snippet targets]How to Use This Checklist
During the Judge Phase
1. Open the checklist and work through each section top to bottom. 2. For each item, check the draft against the criteria. Mark pass or fail. 3. For failed items, note the specific location and what needs to change. 4. Classify each failure:
- Must-fix: Missing title tag, broken heading hierarchy, no keyword in first 100 words, keyword stuffing, missing meta description.
- Review: Paragraph slightly over 4 sentences, reading level one grade above target, missing one semantic variation.
5. Present the completed report to the human with must-fix items listed first.
Severity Guide
Must-fix items are issues that directly harm ranking potential or user experience. These should be resolved before publication.
Examples:
- Title tag missing or over 60 characters
- No H1 on the page
- Primary keyword absent from first 100 words
- Heading hierarchy skips a level
- Keyword stuffing (same phrase repeated unnaturally)
- Meta description missing
Review items are optimization opportunities. The content can publish without addressing them, but fixing them improves search performance.
Examples:
- Semantic variation could be added in one more section
- A definition paragraph is 70 words instead of 40-60
- One H2 heading is vague but not keyword-empty
- Internal link count is below the 3-5 per 1,000 words target
Integration with the Judge Consolidated Report
When the SEO Writer checklist runs as part of the Judge phase, its results feed into the Judge's consolidated report. The SEO section of the Judge report should include:
1. Overall SEO status: Pass / Needs Work / Fail 2. Must-fix count and list 3. Review item count and list 4. Featured snippet readiness: Ready / Partially Ready / Not Targeted 5. E-E-A-T assessment: Strong / Adequate / Weak
Featured Snippet Targeting and Content Enrichment
Featured Snippet Formats
Featured snippets are the highlighted answer boxes that appear above standard search results. Winning a featured snippet dramatically increases visibility. Each snippet type has a specific content structure that triggers selection.
| Snippet Type | How to Target | Format |
|---|---|---|
| Paragraph | Define the key concept in 40-60 words immediately after the relevant H2 heading. Use a clear, direct sentence structure: "[Term] is [definition]." | Clear definition paragraph, no filler |
| List | Place a numbered or bulleted list immediately after the relevant H2 heading. Use 3-8 items. Each item should start with a consistent grammatical pattern. | Steps (numbered) or ranked items (bulleted) |
| Table | Place a comparison or data table immediately after the relevant H2 heading. Use clear column headers and at least 3 rows of data. | Side-by-side data with headers |
Paragraph Snippet Targeting
The paragraph snippet rewards concise, authoritative definitions. The target pattern:
1. Use the question or keyword as the H2 heading. 2. Immediately follow with a 40-60 word paragraph that directly answers the question. 3. Do not start with "In this section..." or "Let's explore..." -- start with the answer. 4. After the snippet-target paragraph, expand with supporting detail.
Example:
## What Is OAuth 2.0?
OAuth 2.0 is an authorization framework that allows third-party applications
to access a user's resources without exposing their credentials. It works by
issuing access tokens through an authorization server, enabling scoped and
time-limited access instead of sharing passwords directly.
[Expanded explanation follows here...]List Snippet Targeting
The list snippet rewards structured sequences. The target pattern:
1. Use a "how to" question or process-oriented keyword as the H2 heading. 2. Immediately follow with a numbered or bulleted list. 3. Keep each list item to one concise line. 4. Use parallel grammatical structure across all items.
Example:
## How to Implement OAuth 2.0
1. Register your application with the authorization provider.
2. Configure redirect URIs and requested scopes.
3. Implement the authorization code flow in your application.
4. Exchange the authorization code for an access token.
5. Use the access token to make authenticated API requests.
6. Handle token refresh when the access token expires.
[Detailed explanation of each step follows...]Table Snippet Targeting
The table snippet rewards structured comparisons. The target pattern:
1. Use a comparison-oriented keyword as the H2 heading. 2. Immediately follow with a markdown table. 3. Use clear, scannable column headers. 4. Include at least 3 rows of data. 5. Keep cell content concise -- save detail for the body text below the table.
Content Enrichment Elements
Beyond snippet targeting, enriched content signals comprehensiveness and authority to search engines. Include these elements where they naturally fit.
Comparison Tables
Use when presenting alternatives, pros/cons, or feature sets. Tables make commercial-intent content scannable and increase time on page.
| Feature | Tool A | Tool B | Tool C |
|---|---|---|---|
| [feature 1] | [value] | [value] | [value] |
| [feature 2] | [value] | [value] | [value] |
| [feature 3] | [value] | [value] | [value] |Numbered Step Lists
Use for any sequential process. Numbered lists target list snippets and signal structured, actionable content.
Definition Paragraphs
Use when introducing a key concept. A 40-60 word definition paragraph after an H2 targets paragraph snippets and provides immediate value to the reader.
Key Takeaway Callouts
Use at the end of major sections to summarize the most important point. These serve readers who scan and reinforce the section's core message.
**Key takeaway:** [One-sentence summary of the section's most important point.]Original Data and Examples
Use whenever possible. Original data, real-world examples, case study references, and first-hand experience are strong E-E-A-T signals. Generic advice ranks poorly against content backed by specific evidence.
Link Map Template
Internal and external links support SEO by distributing authority and signaling topical relevance. Plan links during the Architect phase, not as an afterthought.
Internal Links
| Anchor Text | Target Page | Section Placement |
|---|---|---|
| [descriptive anchor text] | [URL or page title] | [section where link appears] |
| [descriptive anchor text] | [URL or page title] | [section where link appears] |
| [descriptive anchor text] | [URL or page title] | [section where link appears] |Internal link rules:
- Use descriptive anchor text, not "click here" or "read more."
- Link to the most relevant page, not the homepage.
- Place links where they add context for the reader, not at random.
- Aim for 3-5 internal links per 1,000 words.
External Links
| Anchor Text | Target URL | Purpose |
|---|---|---|
| [descriptive anchor text] | [external URL] | [source / reference / further reading] |
| [descriptive anchor text] | [external URL] | [source / reference / further reading] |External link rules:
- Link to authoritative, primary sources.
- Do not link to direct competitors for the same target keyword.
- Ensure external links open in a new tab (if the publishing platform supports it).
- Verify links are not broken before publication.
Meta Elements Template
Write meta elements after the content is drafted. The content informs the meta, not the other way around.
Title Tag (50-60 characters)
The title tag appears in search results and browser tabs. It is the single most important on-page ranking signal.
Format: [Primary Keyword]: [Compelling Modifier or Benefit]
Example: "OAuth 2.0 Guide: How Authorization Flows Work in Practice"
Length: 57 charactersRules:
- Primary keyword near the front.
- 50-60 characters. Longer titles get truncated in SERPs.
- No keyword repetition within the title.
- Must be unique across the site.
Meta Description (150-160 characters)
The meta description appears below the title in search results. It does not directly affect ranking but strongly affects click-through rate.
Format: [What the reader will learn or gain]. [Specific detail or scope]. [Implicit or explicit CTA.]
Example: "Learn how OAuth 2.0 authorization flows work with practical code examples. Covers all four grant types and common security pitfalls."
Length: 134 charactersRules:
- 150-160 characters. Shorter is acceptable; longer gets truncated.
- Include the primary keyword naturally.
- Describe the content's value, not just its topic.
- Do not duplicate the title tag.
URL Slug
Format: /primary-keyword-modifier
Example: /oauth-2-authorization-guideRules:
- Use hyphens, not underscores.
- Include the primary keyword.
- Keep it short: 3-5 words.
- No stop words ("a," "the," "and") unless they are part of the keyword.
- All lowercase.