# Organigramm Post - Next Steps

**Last Updated:** 2026-04-04  
**Status:** Traffic-recovery sprint applied (skyscraper + validators); monitor 4–8 weeks

## Completed Work Summary

### SEO/AEO/GEO recovery sprint (2026-04-04)

- ✅ Refreshed GSC/GA4/SISTRIX artifacts; GSC query period compare in `data/gsc-queries-*.json` and `data/gsc-queries-diff.md`
- ✅ `SERP_ANALYSIS.md`, `CONTENT_OUTLINE.md`, section briefs; `make blog-outline-gate` and `validate-improvement-readiness.php` passed before HTML apply
- ✅ Body refresh via `content-draft.html` → `update-post-content.php` / `make blog-apply-validate-strict` (~3.0k words): klassische Formen, Office, Fazit, Englisch/Gender, de-duplicated intro, contextual cluster links (e.g. Gastronomie-Branche where relevant)
- ✅ **Heading hygiene (2026-04-04):** H3 count reduced (~52 → **27** under 14 H2) per `blog-restructuring.mdc`—merged micro-H3s in Arten, „Was gehört“, Grenzen, Schritt-für-Schritt, Office, Tools, Best Practices, Beispiele; **PAA 89/89**, section depth, completeness, FAQ validators still **PASS** after re-apply
- ✅ **Listen statt H3 (2026-04-04):** „Wofür dient“, „Grenzen“, „Office“ und zuvor „Best Practices“ ohne Unterüberschriften, mit `<ul>`; **H3 = 20**, Wörter ~3.35k, `blog-apply-validate-strict` **PASS**
- ✅ Meta/title/excerpt/keywords aligned to primary `**organigramm erstellen`** (restored after pipeline drift)
- ✅ FAQ set replaced and validated (FAQ quality, H2 overlap, schema); `validate-faq-schema.php` OK
- ✅ `images[]` cleaned to featured-only; meaningful alts aligned to post title
- ✅ `lead_capture_copy` `blog_organigramm` updated (Schichtplan/Personaleinsatz angle; no `/kostenlos-testen`)
- ✅ `analyze-post-content.php`, `analyze-post-links.php`, `generate-post-documentation.php`, `generate-automated-reports.php` run so docs match live JSON

### Earlier major expansion (2026-01-18, historical)

- Expanded from thin draft to full lexikon depth; tables, Schritt-für-Schritt, Tools, Best Practices, Beispiele

### Performance baseline after refresh (exports `data/performance-*.json`, 90 days)

- **GSC:** 46 clicks, ~19.6k impressions, CTR ~0.23%, average position ~16.5
- **GA4:** 99 page views, 89 sessions, bounce ~23.6%, avg engagement ~160 s
- **Baseline for this sprint:** 2026-04-04

### Documentation

- ✅ `MONITORING_CHECKLIST.md` — updated with 2026-04-04 baseline
- ✅ `IMPROVEMENT_PLAN.md` — regenerated from current data

## Monitoring Schedule

**First check:** 2026-04-11 (week 1 after deploy)

- GSC: clicks/position/CTR for top queries (`organigramm erstellen`, `organigramm`, head variants)
- Rich Results Test on live URL for FAQPage
- Spot-check mobile article layout

**Regular:** Weekly for 4 weeks, then biweekly through week 8

- Compare to `data/gsc-queries-diff.md` narrative; watch impression-heavy / low-CTR queries for title/description tests

**Review gate:** 2026-06-01 — decide if secondary template/tool links are worth adding (validator warnings only)

## Related Posts Status

### Already Improved

- ✅ `ratgeber/wareneinsatz` - Completed 2026-01-18
- ✅ `ratgeber/mitarbeiter-motivieren` - Completed 2026-01-18
- ✅ `ratgeber/schichtplan-erstellen` - Completed 2026-01-18
- ✅ `ratgeber/zeiterfassung-app` - Completed previously
- ✅ `ratgeber/urlaubsanspruch-von-minijobbern` - Completed previously
- ✅ `lexikon/24-stunden-schicht` - Completed previously

### Related posts (cluster, 2026-04-04)

- `**lexikon/arbeitsorganisation`** — deep (~2.9k words); linked from organigramm. Monitor unless GSC shows regression.
- `**lexikon/personaleinsatzplanung**` — deep (~3.6k words in live JSON); linked from organigramm. Treat as **performance/monitoring** play (position/CTR), not a word-count gap.
- `**lexikon/personalabteilung`** — still **thin** (~557 words): best next **lexikon expansion** if you want more HR-structure coverage tied to this cluster.

**Other follow-ups:** `lexikon/arbeitsplan` (review + links as needed).

## Recommended next action

1. **This post:** keep the 2026-06-01 review (collectors + GSC) for organigramm after deploy.
2. **Cluster expansion (optional):** run an improvement sprint on `**lexikon/personalabteilung`** (data → SERP/outline → draft) using `docs/content/blog/PAGE_IMPROVEMENT_DATA_PLAYBOOK.md` and `BLOG_AGENT_PHASE_RUNBOOK.md`.

## Content Cluster Strategy

**Organizational Structure Cluster:**

1. ✅ `lexikon/organigramm` — Recovery sprint 2026-04-04 (~3.1k words); monitor GSC 4–8 weeks
2. ✅ `lexikon/arbeitsorganisation` — Substantive pass 2026-01-18 (~2.9k words); monitor unless data flags regression
3. ✅ `lexikon/personaleinsatzplanung` — Deep content (~3.6k words); focus on rankings/CTR, not length
4. ⏳ `lexikon/personalabteilung` — **Next optional lexikon expansion** (~557 words today)

**Benefits of Cluster Approach:**

- Strengthens topical authority
- Improves internal linking opportunities
- Creates comprehensive coverage of organizational topics
- Better user experience (related content discovery)

## Notes

- **2026-04-04:** Google Rich Results Test (smartphone UA) on live URL reported **FAQ: 1 valid item** plus Articles, Breadcrumbs, Organization, Review snippets (some non-critical flags on Articles/Organization). Live `<title>` may lag repo until deploy.
- GSC **URL inspection** still manual in Search Console after deploy.
- Next optional cluster-related expand: `**lexikon/personalabteilung`** (thin lexikon entry vs organigramm / Personaleinsatz).