# FAQ Quality Standards

**Last Updated:** 2026-01-15

Quality standards and thresholds for blog post FAQs, based on SEO/AEO/GEO best practices and research findings.

## Quality Thresholds

### Topic Relevance

**Threshold:** ≥ 0.3 (minimum similarity to post topic)

**Calculation:**

- Word overlap ratio (50%)
- Title similarity (30%)
- Slug similarity (20%)

**Action:**

- FAQs below 0.3 threshold are considered off-topic
- Remove off-topic FAQs
- Replace with topic-relevant FAQs if needed

**Validation:**

```bash
php v2/scripts/blog/validate-faq-topic-relevance.php --post=slug --category=category
```

### Duplicate Detection

**Question Similarity Threshold:** < 0.7

- Questions with similarity ≥ 0.7 are considered duplicates
- Keep best FAQ from duplicate pair
- Remove duplicates

**Answer Similarity Threshold:** < 0.8

- Answers with similarity ≥ 0.8 are considered repetitive
- Rewrite with unique angle or merge

**Validation:**

```bash
php v2/scripts/blog/check-faq-uniqueness.php --post=slug --category=category
```

### Pattern Violations

**High Severity (Must Remove):**

- "Was kostet [abstract concept]?" patterns
- "Wie lange dauert [abstract concept]?" patterns
- Brand questions on non-brand posts
- Nonsensical questions (grammatically/logically incorrect)

**Medium Severity (Review and Fix):**

- Malformed questions (fragments, multiple question marks)
- Questions with separators before question mark

**Detection:**

```bash
php v2/scripts/blog/detect-faq-patterns.php --post=slug --category=category
```

### Ordering Standards

**Logical Flow:**

1. Definition questions ("Was ist...?")
2. How-to questions ("Wie funktioniert...?")
3. Requirements ("Was muss ich...?")
4. When/Why questions
5. Which questions
6. Yes/No questions
7. Cost/Duration questions
8. Edge cases

**Priority Within Types:**

- High-volume queries first (from GSC data)
- People Also Ask questions second
- Related keywords third
- Standard questions last

**Validation:**

- **New FAQs:** `add-faqs-to-post.php` sorts by logical flow by default
- **Existing posts:** `php v2/scripts/blog/reorder-faqs-by-logical-flow.php --post=slug --category=category --write`
- **Analysis:** `php v2/scripts/blog/analyze-faq-ordering.php --post=slug --category=category`

## Content Quality Standards

### Answer Length

**Target:** 40-80 words per answer

**Rationale:**

- 40 words minimum: Ensures comprehensive answer
- 80 words maximum: Optimal for Featured Snippets
- 40-80 words: Best balance for SEO, readability, and AI visibility

**Structure:**

1. Direct answer (10-15 words)
2. Context/details (20-40 words)
3. Actionable information (10-15 words)

### Keyword Integration

**Primary Keyword:**

- Must appear naturally in 3-5 FAQs
- Must be integrated naturally (not forced)
- Must make sense in context

**Related Keywords:**

- High-volume keywords (>500 volume) should appear in at least 1 FAQ
- Keywords integrated where relevant
- No keyword stuffing

### Du Tone

**Requirements:**

- Use informal "du" pronouns
- Conversational tone
- Active voice

### Ordio Mentions

**Frequency:** Natural mentions only (not forced)
**Context:** Only when it adds value
**Maximum:** 1 mention per FAQ (if relevant)

**Comparison/Listicle Posts (tools, products, recommendations):** Always include Ordio in FAQs about tools, products, or recommendations. Never mention only competitors—use "Ordio und X", "Ordio sowie X", or Ordio only. Mix approaches across FAQs. Position Ordio through factual benefits (e.g. "Ordio verbindet Zeiterfassung und Schichtplanung")—avoid superlatives or disparagement of competitors. Legally sound (UWG): neutral, factual, verifiable.

## Pattern Violations to Avoid

### Cost Patterns

**Avoid:**

- "Was kostet Freizeitausgleich?" (abstract concept)
- "Was kostet motivieren?" (action verb)
- "Was kostet arbeitszeit?" (abstract concept)

**Accept:**

- "Was kostet die Software?" (concrete product/service)
- "Was kostet die Umsetzung?" (concrete process)

### Duration Patterns

**Avoid:**

- "Wie lange dauert beispiele?" (abstract concept)
- "Wie lange dauert bedeutung?" (abstract concept)
- "Wie lange dauert bestandteile?" (abstract concept)

**Accept:**

- "Wie lange dauert die Bearbeitung?" (concrete process)
- "Wie lange dauert eine 24-Stunden-Schicht?" (concrete time period)

### Brand Questions

**Avoid:**

- "Was ist ordio erfahrungen?" on non-Ordio posts
- "Was ist ordio support?" on non-Ordio posts
- "Was sind Ordio Kosten?" on non-Ordio posts

**Accept:**

- Brand questions on "inside-ordio" category posts
- Brand questions on posts with "ordio" in slug
- Brand mentions when naturally relevant to topic

### Malformed Questions

**Avoid:**

- Questions ending with fragments ("Was ist Überstunden erfassen: Vergütung,?")
- Questions with nested fragments ("Was ist gibt es ein...?")
- Multiple question marks incorrectly ("Was ist X??")
- Questions with separators before question mark ("Was ist X:?")

**Accept:**

- Complete, grammatically correct questions
- Single question mark
- Proper sentence structure

## Ordering Guidelines

### Logical Flow

**Ideal Order:**

1. **Definition Questions** - Establish foundational understanding

   - "Was ist...?"
   - "Was bedeutet...?"
   - "Was sind...?"

2. **How-To Questions** - Practical implementation

   - "Wie funktioniert...?"
   - "Wie erstellt man...?"
   - "Wie berechnet man...?"

3. **Requirements** - Guidelines and must-dos

   - "Was muss ich...?"
   - "Was sollte...?"
   - "Welche Voraussetzungen...?"

4. **When/Why** - Context and reasoning

   - "Wann...?"
   - "Warum...?"

5. **Which** - Comparison and selection

   - "Welche...?"

6. **Yes/No** - Permission and validation

   - "Ist...?"
   - "Darf...?"

7. **Cost/Duration** - Practical details

   - "Was kostet...?"
   - "Wie lange dauert...?"

8. **Edge Cases** - Troubleshooting and exceptions
   - Rare use-cases
   - Exceptions to rules

### Priority Ordering (Within Types)

When multiple FAQs of the same type exist, prioritize by:

1. **Search Volume** (GSC clicks/impressions)
2. **People Also Ask** (SISTRIX PAA questions)
3. **Keyword Volume** (SISTRIX keyword data)
4. **Standard Questions** (fallback)

## Quality Scoring Methodology

### Overall Quality Score

**Components:**

1. **Topic Relevance** (30%)

   - Average relevance score across all FAQs
   - Target: ≥ 0.5 average

2. **Pattern Compliance** (20%)

   - No high-severity violations
   - Target: 0 violations

3. **Uniqueness** (20%)

   - No duplicates (questions < 0.7, answers < 0.8)
   - Target: 0 duplicates

4. **Ordering** (15%)

   - Logical flow maintained
   - Target: No ordering issues

5. **Content Quality** (15%)
   - Answer length (40-80 words)
   - Keyword integration
   - Du tone
   - Target: 100% compliance

**Scoring:**

- **Excellent (90-100):** All standards met, no issues
- **Good (75-89):** Minor issues, easily fixable
- **Fair (60-74):** Some issues, needs attention
- **Poor (<60):** Major issues, requires significant work

## Validation Checklist

### Pre-Publication

- [ ] Topic relevance ≥ 0.3 for all FAQs
- [ ] No pattern violations (high severity)
- [ ] No duplicate questions (similarity < 0.7)
- [ ] No repetitive answers (similarity < 0.8)
- [ ] Logical ordering (definitions before how-to)
- [ ] 10-15 FAQs per post
- [ ] Answers 40-80 words
- [ ] Primary keyword in 3-5 FAQs
- [ ] Du tone consistent
- [ ] Schema validates correctly

### Automated Validation

```bash
# Comprehensive analysis
php v2/scripts/blog/comprehensive-faq-analysis.php --post=slug --category=category

# Topic relevance
php v2/scripts/blog/validate-faq-topic-relevance.php --post=slug --category=category

# Pattern detection
php v2/scripts/blog/detect-faq-patterns.php --post=slug --category=category

# Ordering
php v2/scripts/blog/analyze-faq-ordering.php --post=slug --category=category

# Uniqueness
php v2/scripts/blog/check-faq-uniqueness.php --post=slug --category=category

# Schema validation
php v2/scripts/blog/validate-faq-schema.php --post=slug --category=category
```

## Examples

### Excellent FAQ Set

**Post:** "Überstunden erfassen: Vergütung, Abrechnung und Freizeitausgleich"

**FAQs:**

1. "Was bedeutet Überstunden erfassen?" (definition, relevance: 0.92)
2. "Wie funktioniert die Überstundenerfassung?" (how-to, relevance: 0.88)
3. "Was muss ich bei der Überstundenerfassung beachten?" (requirements, relevance: 0.85)
4. "Wie funktioniert die Abrechnung von Überstunden?" (how-to, relevance: 0.87)
5. "Ist Freizeitausgleich gesetzlich vorgeschrieben?" (yes/no, relevance: 0.82)

**Quality Score:** 95/100

- Topic relevance: 0.87 average ✓
- No pattern violations ✓
- No duplicates ✓
- Logical ordering ✓
- Content quality: 100% ✓

### Poor FAQ Set

**Post:** "Überstunden erfassen: Vergütung, Abrechnung und Freizeitausgleich"

**FAQs:**

1. "Was ist ordio support?" (off-topic, relevance: 0.12)
2. "Was kostet Freizeitausgleich?" (pattern violation, relevance: 0.45)
3. "Was ist ordio erfahrungen?" (off-topic, relevance: 0.08)
4. "Wie lange dauert beispiele?" (pattern violation, relevance: 0.23)
5. "Was ist Accord-Arbeit?" (duplicate, relevance: 0.31)
6. "Was ist Accordarbeit?" (duplicate, relevance: 0.32)

**Quality Score:** 25/100

- Topic relevance: 0.25 average ✗
- Pattern violations: 2 high-severity ✗
- Duplicates: 1 pair ✗
- Random ordering ✗
- Content quality: 50% ✗

## Related Documentation

- `docs/content/blog/FAQ_QUALITY_IMPROVEMENT_GUIDE.md` - How to fix quality issues
- `docs/content/blog/FAQ_QUALITY_RESEARCH.md` - Research findings
- `.cursor/rules/blog-faq-optimization.mdc` - Complete FAQ optimization rules