# Blog Post Recovery Workflow Guide

**Last Updated:** 2026-01-14
**Purpose:** Systematic workflow for recovering lost blog improvements (FAQs, content expansions, internal links)

## Overview

This guide provides a step-by-step workflow for recovering blog post improvements that were lost during migration. The recovery process is prioritized by traffic and impact.

## Recovery Status

**Current State:**

- Total Posts: 99
- Posts with FAQs: 1 (1%) - `recap-webinar-sv-pruefung` restored
- Posts needing FAQ recovery: 38
- Posts needing content expansion: 72
- Total FAQs to restore: ~820+

## Recovery Workflow

### Phase 1: FAQ Recovery

#### Step 1: Identify Priority Posts

Use the gap audit script to identify posts needing FAQs:

```bash
php v2/scripts/blog/audit-improvement-gaps.php
```

Review `docs/content/blog/IMPROVEMENT_GAPS_AUDIT.md` for prioritized list.

#### Step 2: Collect FAQ Research Data

For each priority post, collect research data:

```bash
php v2/scripts/blog/collect-faq-research-data.php --post=slug --category=category
```

This generates:

- PAA questions from SISTRIX
- GSC top queries
- Keyword data

#### Step 3: Generate FAQ Questions

Generate FAQ questions based on research:

```bash
php v2/scripts/blog/generate-faq-questions.php --post=slug --category=category
```

Review and refine questions to match documented count.

#### Step 4: Write FAQ Answers

Write FAQ answers following best practices:

- **Length:** 40-80 words per answer
- **Tone:** Informal "du" (duzen)
- **Keywords:** Natural integration (50%+ FAQs should include primary keyword)
- **Internal Links:** Add 1-2 internal links per FAQ where relevant
- **Structure:** Direct answer → context → actionable info

#### Step 5: Add FAQs to Post

Create FAQs JSON file:

```json
{
  "faqs": [
    {
      "question": "Question text?",
      "answer": "<p>Answer text with HTML formatting.</p>"
    }
  ]
}
```

Add to post:

```bash
php v2/scripts/blog/add-faqs-to-post.php --post=slug --category=category --faqs=faqs.json
```

#### Step 6: Validate Schema

Validate FAQ schema:

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

#### Step 7: Update Progress

Update recovery progress:

```bash
php v2/scripts/blog/track-recovery-progress.php --update --dashboard
```

### Phase 2: Content Expansion Recovery

#### Step 1: Identify Expansion Gaps

Review `docs/content/blog/IMPROVEMENT_GAPS_AUDIT.md` for word count gaps.

#### Step 2: Restore Missing Content

For posts with documented expansions:

1. Compare documented word count vs current
2. Identify missing sections from documentation
3. Restore content following documented patterns
4. Ensure quality standards (du tone, Ordio mentions, internal links)

#### Step 3: Expand Content

For posts below word count targets:

1. Expand introduction (100-200 words)
2. Add detailed sections (300-500 words)
3. Add case studies/examples (200-300 words)
4. Enhance conclusion (100-150 words)

#### Step 4: Validate Word Count

Verify word count meets target:

- Ratgeber/Lexikon: 1,200+ words
- Inside Ordio: 500-800 words

### Phase 3: Internal Links Recovery

#### Step 1: Verify Documented Links

Check if documented internal links exist in current content.

#### Step 2: Restore Missing Links

Add missing links with proper anchor text:

- No stop words in anchor text
- Contextual placement
- Match documented targets

#### Step 3: Validate Links

Run link validation:

```bash
php v2/scripts/blog/audit-all-internal-links.php
```

### Phase 4: Schema and Meta Recovery

#### Step 1: Verify FAQPage Schema

For posts with FAQs, ensure FAQPage schema is present.

#### Step 2: Validate Schema

Run schema validation:

```bash
php v2/scripts/blog/validate-faq-schema.php --all
```

## Priority Order

### High Priority (Immediate)

1. **Top 10 Traffic Posts** with documented FAQs

   - `zuschlage-berechnen-rechner` (7,343 GSC clicks)
   - `arbeitsstunden-pro-monat` (623 traffic)
   - `dienstplan-gesetz` (578 traffic)
   - `recap-webinar-sv-pruefung` ✅ (10 FAQs restored)
   - `zeiterfassung-app` (13 FAQs documented)
   - And 5 more...

2. **High-Traffic Posts** with content expansions
   - `recap-webinar-sv-pruefung` (576 word gap)

### Medium Priority

3. **Remaining Ratgeber Posts** with documented FAQs (17 posts)
4. **Lexikon Posts** with documented FAQs (18 posts)
5. **Medium-Traffic Posts** with content expansions

### Low Priority

6. **Inside Ordio Posts** (lower SEO priority)
7. **Low-Traffic Posts** (can be deferred)

## Quality Checklist

Before marking a post as recovered:

- [ ] FAQs match documented count
- [ ] FAQ answers are 40-80 words each
- [ ] FAQ schema validates successfully
- [ ] Content word count meets target
- [ ] Internal links match documented additions
- [ ] Du tone maintained throughout
- [ ] Ordio mentioned naturally (once per major section)
- [ ] No competitor praise
- [ ] All validation scripts pass

## Tools and Scripts

### Audit Scripts

- `audit-faq-inventory.php` - Current FAQ inventory
- `audit-faq-quality.php` - FAQ quality assessment
- `audit-improvement-gaps.php` - Gap analysis
- `audit-all-internal-links.php` - Link validation

### Recovery Scripts

- `collect-faq-research-data.php` - Collect research data
- `generate-faq-questions.php` - Generate FAQ questions
- `add-faqs-to-post.php` - Add FAQs to post JSON
- `track-recovery-progress.php` - Track progress

### Validation Scripts

- `validate-faq-schema.php` - Validate FAQ schema
- `validate-link-quality.php` - Validate link quality
- `validate-blog-content.php` - Validate content structure

## Progress Tracking

View current progress:

```bash
php v2/scripts/blog/track-recovery-progress.php --dashboard
```

Dashboard saved to: `docs/content/blog/RECOVERY_PROGRESS_DASHBOARD.md`

## Estimated Timeline

- **High Priority (Top 20):** 2-3 weeks
- **Medium Priority (Next 30):** 3-4 weeks
- **Low Priority (Remaining):** 2-3 weeks
- **Total:** 7-10 weeks (can be done incrementally)

## Notes

- Focus on high-traffic posts first for maximum impact
- Use existing scripts to automate repetitive tasks
- Validate all changes before marking complete
- Update progress tracking regularly
- Document any deviations from documented improvements