# content-writing Full Instructions

## Core Principles

### Human-First Content

- Write for humans first, optimize for search engines second
- Focus on providing genuine value to readers
- Answer real questions and solve real problems
- Use natural, conversational language
- Avoid keyword stuffing and unnatural language
- **Blog / insights HTML:** Do not paste outline or SEO-tooling language into reader-facing copy (no „PAA“, „SERP“, „SISTRIX“, „Suchanfragen“ as process commentary, or outline filenames). Research stays under `docs/`; see [READER_FACING_COPY_GUARDRAILS.md](../../docs/content/blog/READER_FACING_COPY_GUARDRAILS.md).

### Natural Language Writing

- Write naturally, as if speaking to a colleague or friend
- Use conversational tone appropriate to audience
- Vary sentence length and structure
- Include natural transitions
- Use contractions when appropriate
- Write in active voice (preferred)

### SEO-Optimized Natural Content

- Integrate keywords naturally, not forcefully
- Include primary keyword in title, H1, first paragraph
- Use secondary keywords naturally throughout content
- Include synonyms and related terms
- Focus on user intent, not just keywords
- Write comprehensive content that covers topics thoroughly

### E-E-A-T Implementation

**Experience:**

- Include first-hand experiences and case studies
- Share real-world examples and scenarios
- Use specific numbers and data points
- Reference actual use cases

**Expertise:**

- Demonstrate deep topic knowledge
- Cite authoritative sources
- Provide accurate, detailed information
- Show understanding of nuances

**Authoritativeness:**

- Build domain authority through quality content
- Earn backlinks from authoritative sites
- Establish topical authority in niche
- Maintain consistent quality

**Trustworthiness:**

- Be transparent about sources and methods
- Provide accurate, up-to-date information
- Include clear contact information
- Regular content updates

## AI Content Avoidance

### Common AI Tells to Avoid

- Overly formal language patterns
- Repetitive sentence structures
- Lack of personal voice/opinions
- Generic transitions ("Furthermore", "Moreover", "In conclusion")
- Overuse of certain phrases ("It's important to note", "In today's world")
- Lack of specific examples or anecdotes
- Perfect grammar without natural variations

### Natural Writing Techniques

- Vary sentence length and structure
- Include personal insights and opinions
- Use specific examples and anecdotes
- Natural transitions and flow
- Conversational tone with occasional contractions
- Imperfect but natural grammar patterns

**See:** `docs/content/AI_CONTENT_AVOIDANCE_GUIDE.md` for comprehensive guide

## Answer-First and AI Citation

- **Answer-first:** 40-60 word direct answer below question headings; first sentence = answer
- **Chunk size:** 40-120 words for AI extraction; 250-350 per section
- **Entity consistency:** Stable terminology (Probezeit, Kündigungsfrist, etc.) across sections

## Content Structure

### Header Hierarchy

- **H1:** Page/post title only (in header component, not in content)
- **H2:** Main sections (5-10 for most; 8-12 for main topics)
  - Each H2 should represent a distinct topic or section
  - Use descriptive, keyword-rich headings
  - Question format works well: "Was ist...?", "Wie berechnet man...?"
- **H3:** Subsections under H2 (optional, case-by-case)
  - Use when sections have distinct subtopics, steps, or comparisons **and each item has 2+ sentences**. H2+paragraphs valid.
  - **Thin H3s (1 sentence) → use list.** H3 per tip only when each tip has 2+ sentences. Otherwise use `<ul>` with bold lead-in per item.
  - **Bold inline + substantial answer (2+ sentences) → consider H3.** When bold text introduces a distinct subtopic with 2+ sentences of content, evaluate: Would an H3 improve TOC and scannability? Does it fit the section flow? Apply contextually—use when it improves structure, not as a rigid pattern.
  - **H3 per item when 3+ items and substantial:** Vorteile/Nachteile (each has list or 2+ paragraphs), Formen/Arten (each 2+ sentences), Rechtliche Grundlagen (merge brief items; H3 for substantial ones like Vertragliche Regelungen). For Tipps with 1-2 sentences each → list.
  - When H3s used: optional intro between H2 and first H3 for smoother flow. Content-driven; avoid cheesy transitions.
  - See `docs/content/blog/CONTENT_WRITING_GUIDELINES.md` and `docs/content/blog/CONTENT_DEPTH_GUIDELINES.md` for full pattern.
- **H4:** Subsections under H3 (use sparingly)
  - Only when H3 section is very long or complex
  - Most posts don't need H4 headings
- **H5-H6:** Avoid if possible
- Sequential hierarchy (no skipping levels: H2 → H3 → H4)
- No backwards hierarchy

**TOC Length Considerations:**

- **≤15 total items (H2+H3):** Flat TOC structure (all items visible)
- **>15 total items:** Grouped TOC structure (H3s collapsed under H2s)
- **>30 total items:** Consider content restructuring or H2-only TOC
- **Best practice:** Aim for 5-10 H2s (8-12 for main topics); H3s optional and case-by-case. Total items typically 10-30.

**When Restructuring is Needed:**

- TOC exceeds 30 items even with grouping
- Many H2s with only 1-2 H3s each (flatten structure)
- H2s are too granular (combine related H2s)
- Content feels disorganized

**See:** `docs/content/blog/TOC_BEST_PRACTICES.md` for complete TOC guidelines

### Paragraph Structure

- **Optimal:** 2-3 sentences per paragraph
- **Maximum:** 4 sentences per paragraph
- **Minimum:** 1 sentence (for emphasis)
- One main idea per paragraph
- Use white space effectively

### Lists

**Use Lists When:**

- Presenting multiple related items
- Breaking down steps or processes
- Highlighting key points
- Making content scannable

**Bulleted Lists:** For related items without order
**Numbered Lists:** For step-by-step instructions, sequential processes

### Quotes

**Use Quotes For:**

- Customer testimonials
- Expert opinions
- Important statements
- Emphasis

**See:** `docs/content/CONTENT_STRUCTURE_FORMATTING_GUIDE.md` for comprehensive guide

## Universal Copy Guidelines

### Du Tone (Informal "You")

- Use informal "du" pronouns, not formal "Sie"
- Conversational and friendly language
- Active voice, present tense
- Examples: "erfasst du Arbeitszeiten" not "erfassen Sie Arbeitszeiten"

### Ordio Mentions

- Mention Ordio naturally once per major section (hero, benefits, FAQ)
- Integrate into context (not forced "Mit Ordio kannst du..." every paragraph)
- Implicit in CTAs (no need to say "Ordio" in button text like "Jetzt starten")
- Let Ordio's value be demonstrated, not constantly stated

### Competitor Language

- Never praise competitors or alternative approaches
- Position Ordio as smarter choice with neutral/factual competitor descriptions
- Focus on Ordio's benefits, not competitor weaknesses
- Generic tools (Excel, Word) can be mentioned when positioning Ordio as better

### Copy Quality

- Keep paragraphs short (2-3 sentences max)
- Use active voice and present tense
- Lead with benefits, not features ("erfasst du Arbeitszeiten gesetzeskonform" not "Zeiterfassung-Feature")
- Avoid jargon; explain technical terms when necessary
- Be concise and direct (no marketing fluff or redundancy)

## Keyword Integration

### Natural Keyword Integration

- Include primary keyword in title, H1, first paragraph
- Use keywords naturally throughout content (not forced)
- Include synonyms and related terms
- Focus on user intent, not just keywords
- Aim for 1-2% keyword density (natural)

### Keyword Placement

- **Title:** Primary keyword near beginning
- **H1:** Include primary keyword
- **First Paragraph:** Include primary keyword naturally
- **H2 Headings:** Include primary keyword when appropriate
- **Body:** Use keywords naturally, not in every sentence

## Content Depth

### Word Count Targets

- **Informational Content:** 1,200+ words (optimal: 1,500-2,500)
- **News/Announcements:** 300-800 words
- **Comprehensive Guides:** 2,500+ words
- **Product Pages:** 500-1,000 words
- **Tools Pages:** 800-1,500 words
- **Template Pages:** 500-1,000 words

### Content Comprehensiveness

- Cover all important aspects of topic
- Include examples and use cases
- Provide step-by-step instructions when relevant
- Address common questions and concerns
- Include related topics and subtopics

## Meta Tags

### Title Tags

- **Length:** 50-60 characters
- **Format:** `{Primary Keyword} | {Category} - Ordio` (blog posts)
- Include primary keyword near beginning
- Unique for every page
- Compelling and click-worthy

### Meta Descriptions

- **Length:** 150-160 characters
- Benefit-driven, includes primary keyword
- Includes call-to-action when appropriate
- Unique for every page
- Compelling and action-oriented

**See:** `docs/content/META_TAGS_OPTIMIZATION_GUIDE.md` for comprehensive guide

## GEO/AEO Optimization

### AI Search Engine Requirements

- Comprehensive schema markup (Article, FAQPage, HowTo)
- Article body markup (`articleBody` field)
- Speakable schema for voice search
- Citation-ready content format
- Natural language patterns (avoid AI content tells)

### AEO/GEO Meta Tags

- `AI-ready: true`
- `Citation-format:` Structured citation format
- `Content-type:` Article type specification
- `Content-purpose:` Purpose description
- `Target-audience:` Audience segments
- `Primary-keywords:` Comma-separated keywords
- `Geographic-coverage:` Geographic relevance

**See:** `docs/content/blog/guides/SEO_OPTIMIZATION_GUIDE.md` for comprehensive GEO/AEO guide

## Content Quality Checklist

**Before applying blog content:** Run [CONTENT_QUALITY_PRE_PUBLISH_CHECKLIST.md](docs/content/blog/CONTENT_QUALITY_PRE_PUBLISH_CHECKLIST.md) – AI avoidance, anti-fluff, copy quality, redundancy. Fix failures before `update-post-content.php`.

### Pre-Publication Checklist

- [ ] Content provides genuine value to readers
- [ ] Natural, conversational language used
- [ ] Keywords integrated naturally (not forced)
- [ ] Personal insights or experiences included
- [ ] Specific examples and anecdotes present
- [ ] Varied sentence lengths and structures
- [ ] Proper header hierarchy (H1-H6)
- [ ] Short paragraphs (2-3 sentences max)
- [ ] Active voice preferred
- [ ] Du tone consistent
- [ ] Ordio mentions appropriate (once per major section)
- [ ] Word count meets target
- [ ] FAQ section present (if applicable)
- [ ] Internal links present (10+)
- [ ] Meta tags optimized
- [ ] Schema markup present
- [ ] Images optimized
- [ ] Content reviewed for accuracy
- [ ] Grammar and spelling checked

### AI Content Avoidance Checklist

- [ ] Sentence variety (short and long mixed)
- [ ] Personal insights or experiences included
- [ ] Specific examples with numbers or scenarios
- [ ] Natural, varied transitions
- [ ] Conversational tone appropriate to audience
- [ ] Context and background provided
- [ ] Varied vocabulary
- [ ] Natural grammar variations

## Content Type-Specific Guidelines

### Blog Posts

- **Tone:** Conversational, informative, helpful
- **Structure:** Introduction → Main Content → FAQ → Conclusion
- **Word Count:** 1,200+ words (informational), 300-800 words (news)
- **Keywords:** Natural integration, focus on user intent
- **Examples:** Real-world scenarios, specific numbers
- **Voice:** Personal insights when appropriate

### Product Pages

- **Tone:** Benefit-focused, clear, persuasive
- **Structure:** Hero → Benefits → Features → Use Cases → CTA
- **Word Count:** 500-1,000 words
- **Keywords:** Product name, benefits, use cases
- **Examples:** Use cases, specific benefits
- **Voice:** Confident, helpful

### Tools Pages

- **Tone:** Clear, instructional, helpful
- **Structure:** Introduction → How It Works → Examples → FAQ
- **Word Count:** 800-1,500 words
- **Keywords:** Tool name, functionality, use cases
- **Examples:** Step-by-step scenarios, specific calculations
- **Voice:** Expert but approachable

### Template Pages

- **Tone:** Helpful, practical, clear
- **Structure:** Introduction → Features → Download → Usage Guide
- **Word Count:** 500-1,000 words
- **Keywords:** Template name, use cases, benefits
- **Examples:** Usage scenarios, specific examples
- **Voice:** Practical, helpful

### FAQ Sections

- **Tone:** Direct, helpful, conversational
- **Structure:** Question → Answer (40-60 words)
- **Word Count:** 40-60 words per answer
- **Keywords:** Natural integration in questions and answers
- **Examples:** Specific scenarios, concrete answers
- **Voice:** Helpful, knowledgeable

## Related Documentation

- `docs/content/CONTENT_WRITING_BEST_PRACTICES_2026.md` - Comprehensive content writing guide
- `docs/content/AI_CONTENT_AVOIDANCE_GUIDE.md` - AI content avoidance guide
- `docs/content/CONTENT_STRUCTURE_FORMATTING_GUIDE.md` - Content structure and formatting guide
- `docs/content/META_TAGS_OPTIMIZATION_GUIDE.md` - Meta tags optimization guide
- `docs/content/SISTRIX_CONTENT_INTEGRATION_GUIDE.md` - SISTRIX content integration guide
- `docs/content/blog/guides/SEO_OPTIMIZATION_GUIDE.md` - SEO/GEO/AEO optimization guide
- `.cursor/rules/shared-patterns.mdc` - Universal copy guidelines

## References

- Industry best practices for content writing (2026)
- E-E-A-T principles (Google Search Quality Rater Guidelines)
- Human-first content principles
- SEO-optimized natural content strategies
- GEO/AEO optimization best practices
