# Content Depth Report

**Post:** lexikon/active-sourcing
**Generated:** 2026-02-22 13:52:00

## Competitor Word Counts

| Position | Domain | Word Count |
|----------|--------|------------|
| #1 | haufe.de | 3,215 |
| #2 | personio.de | 0 |
| #3 | active-sourcing.com | 0 |
| #4 | kooku.de | 2,800 |
| #5 | universal-search-box.com | 0 |
| #6 | indeed.com | 0 |
| #7 | haufe-akademie.de | 1,983 |
| #8 | kienbaum.com | 3,949 |
| #9 | absolventa.de | 0 |
| #10 | hays.de | 1,642 |

**Average:** 1,359 words

## Competitive Depth Target

- **Recommended Target:** 3,400 words
- **Minimum:** 1,500 words

## Outline vs Target

No target in CONTENT_OUTLINE.md. Set from data/competitive-depth-analysis.md.

## Current Post Gap

- **Current word count:** 0 words
- **Gap to recommended target:** 3,400 words

## Missing Topics (from competitive-depth)

- Active sourcing
- Themensuche
- Recruitingmessen
- Active sourcing definition: was ist active sourcing?
- Active-sourcing-kanäle: die kandidaten an der richtigen stelle abholen
- Active sourcing ist kein synonym für social-media-recruiting
- Active sourcing methoden helfen bei der personalgewinnung
- Active sourcing: bedeutung, beispiele und die besten methoden für eine schnelle stellenbesetzung
- Was ist active sourcing? bedeutung und definition
- Wann ist active sourcing sinnvoll?    

## Unique Value Reminder

Before writing, ensure CONTENT_OUTLINE.md Unique Value section has ≥1 item checked (original data, expert insights, better format, freshness, use case). See SKYSCRAPER_TECHNIQUE_2026.md.

## Suggested Next Steps

1. Review data/competitive-depth-analysis.md for full recommendations
2. Set CONTENT_OUTLINE.md target from competitive-depth (minimum 80% of recommended)
3. Add H2 sections to cover missing topics
4. Complete SERP_ANALYSIS.md manual sections (30 min browser review)
5. Run `php v2/scripts/blog/check-outline-h2-overlap.php --post=active-sourcing --category=lexikon` to avoid duplicate H2s
6. Run `php v2/scripts/blog/validate-content-outline-quality.php --post=active-sourcing --category=lexikon` before content creation