# Content Creation Workflow 2026

**Last Updated:** 2026-02-17  
**Purpose:** Complete workflow for creating new content from research to final review, applying all best practices

## Overview

This workflow guides content creators through the complete process of creating new content, ensuring all best practices are applied from research through publication.

## Phase 1: Research & Planning

### 1.1 Keyword Research

**SISTRIX Data:**

- Review competition levels for target keywords
- Analyze search intent classification
- Review PAA questions
- Check SERP features
- Identify domain opportunities

**Tools:**

- SISTRIX API (via collection scripts)
- `v2/scripts/content/integrate-sistrix-insights.php` - Generate content suggestions from SISTRIX data
- Google Keyword Planner
- Google Trends
- People Also Ask

**Step 1: Collect SISTRIX Data (if not already collected):**

**Option A: Use Content Writing Assistant (Recommended)**

```bash
# Full workflow: Collect all data + generate brief + suggestions
php v2/scripts/content/content-writing-assistant.php --post=slug --category=category --mode=full
```

**Option B: Individual Scripts**

```bash
# Collect keyword data (includes related keywords and historical trends)
php v2/scripts/blog/collect-post-keywords-sistrix.php --post=slug --category=category

# Collect search intent data
php v2/scripts/blog/collect-post-search-intent.php --post=slug --category=category

# Collect SERP features data
php v2/scripts/blog/collect-post-serp-features.php --post=slug --category=category

# Collect PAA questions (actual questions, not just counts)
php v2/scripts/blog/collect-post-paa-questions.php --post=slug --category=category

# Collect competitor analysis (content structure, headings, FAQs)
# Uses Firecrawl API fallback when cURL returns sparse content (JS-heavy sites)
php v2/scripts/blog/collect-post-competitor-analysis.php --post=slug --category=category --top=10
```

**Step 2: Generate Content Brief:**

```bash
# Generate comprehensive content brief
php v2/scripts/content/generate-content-brief-from-sistrix.php --post=slug --category=category --output=content-brief.md
```

**Step 3: Generate Optimization Suggestions:**

```bash
# Generate specific, actionable optimization suggestions
php v2/scripts/content/integrate-sistrix-insights.php --post=slug --category=category --output=suggestions.md
```

**Output:**

- Primary keyword with metrics and historical trends
- Secondary keywords
- Related keywords and semantic variations (10+ keywords)
- Search intent classification
- Competition level with trend direction
- Specific PAA questions (not just detection)
- Competitor content analysis (word count, headings, FAQs)
- Recommended content structure from competitors
- Content depth recommendations based on competitor analysis
- Specific actionable recommendations (exact headings, FAQs, word counts)

**MCP enhancement (recommended when sparse):** If competitor-analysis.json has sparse FAQs, empty headings, or word_count < 100 for key competitors, use **Firecrawl MCP** to scrape those URLs. Use Serper for real PAA; Fetch for schema validation. See [SERP_MCP_IMPROVEMENT_GUIDE.md](blog/SERP_MCP_IMPROVEMENT_GUIDE.md).

### 1.2 Content Planning

**Based on Research:**

- Determine content depth (based on competitor analysis - specific word count targets)
- Plan content structure (based on competitor headings and search intent)
- Identify FAQ opportunities (from specific PAA questions)
- Plan featured snippet targets (from PAA questions)
- Identify internal linking opportunities (from related keywords)
- Map keyword clusters (from topical authority analysis)

**Content Structure:**

- Introduction (100-200 words)
- Main sections (H2 headings)
- Subsections (H3 headings)
- FAQ section (5-10 FAQs)
- Conclusion (50-100 words)

**Output:**

- Content outline
- Keyword placement plan
- FAQ list
- Internal linking plan

## Phase 2: Content Writing

### 2.1 Write Introduction

**Requirements:**

- 100-200 words
- Context and background
- Value proposition
- What readers will learn
- Hook to keep reading
- Include primary keyword naturally

**Pattern interrupt (2026):** First 5 seconds matter. Avoid dictionary definitions, long backstories, generic SEO intros. Use: bold claim, surprising statistic, direct challenge, or provocative question. Stops scrolling; earns attention.

**Best Practices:**

- Natural, conversational tone
- Specific examples
- Personal insights when appropriate
- Varied sentence lengths

### 2.2 Write Main Content

**Requirements:**

- Comprehensive coverage of topic
- Multiple H2 sections (5-10 for most; 8-12 for main topics)
- H3 subsections as needed
- Examples and use cases
- Step-by-step instructions when relevant

**Best Practices:**

- Natural language (avoid AI content tells)
- Varied sentence structures
- Short paragraphs (2-3 sentences)
- Active voice preferred
- Specific examples and data points

### 2.3 Write FAQ Section

**Requirements:**

- 5-10 FAQs
- Answers 40-60 words each
- Use PAA questions when possible
- Natural keyword integration
- Comprehensive answers

**Best Practices:**

- Direct, helpful answers
- Conversational tone
- Specific scenarios
- Natural language

### 2.4 Write Conclusion

**Requirements:**

- 50-100 words
- Key takeaways
- Next steps
- Related resources
- Call-to-action when appropriate

**Best Practices:**

- Summarize main points
- Provide clear next steps
- Link to related content
- Natural, helpful tone

## Phase 3: Content Optimization

### 3.1 AI Content Check

**Checklist:**

- [ ] Varied sentence lengths and structures
- [ ] Personal insights or experiences included
- [ ] Specific examples and anecdotes present
- [ ] Natural, varied transitions
- [ ] Conversational tone appropriate
- [ ] Context and background provided
- [ ] Varied vocabulary
- [ ] Natural grammar variations

**Tools:**

- Manual review
- AI content detection tools (for reference)
- Read content aloud

### 3.2 SEO Optimization

**Meta Tags:**

- [ ] Title tag optimized (50-60 chars)
- [ ] Meta description optimized (150-160 chars)
- [ ] Primary keyword in title and description
- [ ] Unique for every page
- [ ] Compelling and click-worthy

**Keywords:**

- [ ] Primary keyword in title, H1, first paragraph
- [ ] Secondary keywords naturally integrated
- [ ] Synonyms and related terms included
- [ ] Keyword density 1-2% (natural)

**Internal Linking:**

- [ ] 10+ internal links
- [ ] Descriptive anchor text
- [ ] Contextual placement
- [ ] Link diversity (blog, tools, templates, pillar pages)

### 3.3 Structure Optimization

**Header Hierarchy:**

- [ ] H1 is page/post title (in header)
- [ ] First content heading is H2
- [ ] Sequential hierarchy (no skipping)
- [ ] No backwards hierarchy
- [ ] Logical content flow

**Formatting:**

- [ ] Short paragraphs (2-3 sentences)
- [ ] Lists used appropriately
- [ ] Quotes used for emphasis/testimonials
- [ ] Proper white space
- [ ] Images have alt text

### 3.4 Schema Markup

**Required Schema:**

- [ ] Article schema (for blog posts)
- [ ] FAQ schema (if FAQs present)
- [ ] BreadcrumbList schema
- [ ] Speakable schema (for voice search)
- [ ] ArticleBody field (for AI engines)

**Validation:**

- [ ] Validate with Google Rich Results Test
- [ ] Check JSON-LD syntax
- [ ] Verify all required fields present
- [ ] Check URLs are absolute

## Phase 4: Quality Assurance

### 4.1 Content Flow Review

**CRITICAL:** Ensure logical content flow and proper definition placement.

**Validation:**
```bash
php v2/scripts/blog/validate-content-flow.php --post=slug --category=category
```

**Checklist:**
- [ ] Core definition appears within first 20% of content
- [ ] Logical flow: Intro → Definition → Explanation → Examples → Advanced
- [ ] No FAQ sections in `content.html` (FAQs only in `faqs` array)
- [ ] Non-text elements preserved (calculators, embeds, videos)
- [ ] Proper heading hierarchy (H2 → H3)
- [ ] Smooth transitions between sections

**Tools:**
- `v2/scripts/blog/analyze-content-flow.php` - Detailed analysis
- `v2/scripts/blog/validate-content-flow.php` - Pre-commit validation

**Documentation:**
- `docs/content/blog/CONTENT_FLOW_GUIDELINES.md` - Complete guidelines
- `.cursor/rules/blog-content-flow.mdc` - Cursor rules

### 4.2 Content Quality Check

**Content:**

- [ ] Provides genuine value to readers
- [ ] Natural, conversational language
- [ ] Keywords integrated naturally
- [ ] Personal insights included
- [ ] Specific examples present
- [ ] Word count meets target
- [ ] **Redundancy check:** Definition appears once; key facts not repeated verbatim; Fazit summarizes without copying intro. See [CONTENT_DEPTH_GUIDELINES.md](blog/CONTENT_DEPTH_GUIDELINES.md) Cross-Section Redundancy Check.

**Language:**

- [ ] Du tone consistent
- [ ] Active voice preferred
- [ ] No jargon (or explained)
- [ ] Concise and direct

**Ordio Mentions:**

- [ ] Mentioned naturally once per major section
- [ ] Not forced into every paragraph
- [ ] Contextually appropriate

### 4.2 Technical Check

**Meta Tags:**

- [ ] Title tag length (50-60 chars)
- [ ] Meta description length (150-160 chars)
- [ ] OG tags complete
- [ ] Twitter Card tags complete
- [ ] AEO/GEO meta tags present

**Schema:**

- [ ] Schema validates
- [ ] All required fields present
- [ ] URLs are absolute
- [ ] Dates are ISO 8601 format

**Links:**

- [ ] All links work correctly
- [ ] Internal links present (10+)
- [ ] Anchor text descriptive
- [ ] No broken links

### 4.3 Accessibility Check

**Images:**

- [ ] All images have alt text
- [ ] Alt text descriptive and specific
- [ ] Images optimized (WebP format)

**Structure:**

- [ ] Proper heading hierarchy
- [ ] Logical content flow
- [ ] Keyboard navigation works

**Content:**

- [ ] Readable font sizes
- [ ] Sufficient color contrast
- [ ] Clear focus states

## Phase 5: Final Review

### 5.1 Pre-Publication Review

**Content:**

- [ ] Read content aloud for natural flow
- [ ] Check for typos and grammar errors
- [ ] Verify all facts and data
- [ ] Ensure content is up-to-date

**SEO:**

- [ ] Meta tags optimized
- [ ] Schema markup validated
- [ ] Internal linking complete
- [ ] Keywords integrated naturally
- [ ] **OG image** – Custom OG image created for new pages (tools, templates, downloads, comparison, etc.). See `docs/systems/og-images/OG_IMAGE_GUIDE.md` → "Publishing New Pages".

**Technical:**

- [ ] All links work
- [ ] Images load properly
- [ ] Mobile responsive
- [ ] Page speed acceptable

### 5.2 Post-Publication Validation

**Schema:**

- [ ] Validate with Google Rich Results Test
- [ ] Check for errors
- [ ] Verify all fields present

**Social Media:**

- [ ] Test Facebook preview
- [ ] Test Twitter Card preview
- [ ] Verify OG tags render correctly

**Performance:**

- [ ] Monitor page speed
- [ ] Check mobile usability
- [ ] Verify indexing status

## Workflow Checklist

### Research & Planning

- [ ] Keyword research completed
- [ ] Search intent identified
- [ ] Competition level analyzed
- [ ] PAA questions collected
- [ ] Content outline created
- [ ] FAQ list prepared

### Content Writing

- [ ] Introduction written
- [ ] Main content written
- [ ] FAQ section written
- [ ] Conclusion written
- [ ] Word count meets target

### Content Optimization

- [ ] AI content check completed
- [ ] SEO optimization completed
- [ ] Structure optimization completed
- [ ] Schema markup added

### Quality Assurance

- [ ] Content quality check completed
- [ ] Technical check completed
- [ ] Accessibility check completed

### Final Review

- [ ] Pre-publication review completed
- [ ] Post-publication validation completed
- [ ] Performance monitoring set up

## Content Type-Specific Workflows

### Blog Posts

**Research:**

- SISTRIX data for target keywords
- PAA questions for FAQs
- SERP features analysis

**Writing:**

- 1,200+ words (informational)
- 300-800 words (news)
- Conversational, informative tone
- Personal insights when appropriate

**Optimization:**

- Article schema
- FAQ schema (if FAQs present)
- Internal linking (10+ links)
- Meta tags with category

### Product Pages

**Research:**

- Product keywords
- User intent (transactional)
- Competitor analysis

**Writing:**

- 500-1,000 words
- Benefit-focused tone
- Use cases and examples
- Clear CTAs

**Optimization:**

- Product schema
- Benefit-focused meta tags
- Conversion-optimized content
- Clear CTAs

### Tools Pages

**Research:**

- Tool keywords
- User intent (informational/transactional)
- Functionality keywords

**Writing:**

- 800-1,500 words
- Clear, instructional tone
- Step-by-step instructions
- Examples and use cases

**Optimization:**

- HowTo schema (if applicable)
- FAQ schema
- Functionality-focused meta tags
- Clear usage instructions

### Template Pages

**Research:**

- Template keywords
- User intent (transactional)
- Download keywords

**Writing:**

- 500-1,000 words
- Practical, helpful tone
- Usage instructions
- Examples

**Optimization:**

- Download-focused meta tags
- Clear download CTAs
- Usage guide schema
- Template examples

## Related Documentation

- `docs/content/CONTENT_WRITING_BEST_PRACTICES_2026.md` - Content writing best practices
- `docs/content/AI_CONTENT_AVOIDANCE_GUIDE.md` - AI content avoidance guide
- `docs/content/SISTRIX_CONTENT_INTEGRATION_GUIDE.md` - SISTRIX integration guide
- `docs/content/META_TAGS_OPTIMIZATION_GUIDE.md` - Meta tags optimization guide
- `docs/content/CONTENT_STRUCTURE_FORMATTING_GUIDE.md` - Content structure guide
- `.cursor/rules/content-writing.mdc` - Content writing Cursor rules

## References

- Content creation best practices (2026)
- SEO optimization workflows
- Quality assurance procedures
- Content validation checklists