# Personalkostenplanung — CREATION_NOTES

**Last Updated:** 2026-03-20

## Summary

Lexikon article **Personalkostenplanung** (`lexikon/personalkostenplanung`) delivered per scaffold + pipeline: SERP/outline, ~2330 words main copy, 12 FAQs, SEO meta (≤60 char title variant), pillars + cluster related posts, featured image (Gemini + WebP srcset), lead capture, `llms-full.txt` sync, TIER1 pillar mapping entry, lexikon inventory re-normalized (`ordio_covered: true`).

## Backup

- Manual snapshot: `docs/backups/blog-snapshots/2026-03-20-063019` (per workflow).

## Keywords

- See `KEYWORD_DECISION.md` and `data/target-keywords.json` (primary: Personalkostenplanung).

## Pipeline

- `run-new-post-pipeline.php --post=personalkostenplanung --category=lexikon` (SISTRIX/competitor data as generated; manual PAA where needed — see `data/paa-questions-manual.json`).

## Content apply

- Body HTML: `content.html` → applied with `php v2/scripts/blog/update-post-content.php` (no direct JSON body edits).

## Product / Ordio

- `v2/data/blog/blog-product-feature-mapping.json`: entry `personalkostenplanung` → `/payroll`, `/arbeitszeiterfassung`, `/schichtplan`, `/digitale-personalakte`.

## Related posts & carousels

- Curated list: `php v2/scripts/blog/set-personalkostenplanung-related-posts.php` (pillars + lexikon siblings).
- Bidirectional: `add-new-post-to-related-carousels.php --targets=personalplanung,personalcontrolling,personaleinsatzplanung,personalbedarfsplanung,personalkosten-gastronomie,lohnabrechnung`.

## SEO

- `v2/data/blog/seo-meta.json` key `lexikon/personalkostenplanung`; `docs/.../data/seo-meta.json` mirror.
- Title shortened for SERP: **Personalkostenplanung: Definition, Methoden & Kennzahlen** (display H1 in JSON aligned).

## Image

- `IMAGE_PROMPT.md` + `generate-blog-featured-image.py` → `/insights/bilder/personalkostenplanung-*w.webp`.

## Lead capture

- Benefit map: `personalkostenplanung` in `generate-lead-capture-copy.php` → `v2/data/lead_capture_copy.php`.

## LLM

- `php v2/scripts/llms/sync-blog-posts-to-llms.php --add`.

## Pillar validation

- `validate-pillar-links.php --post=personalkostenplanung --category=lexikon` — pass (HTML + `internal_links` + `related_posts`).

## Validators (2026-03-20)

- `validate-section-depth` — PASS  
- `validate-content-completeness` — COMPLETE  
- `validate-faq-quality` — EXCELLENT (96/100)  
- `validate-new-post.php --strict` — exit 0; remaining warnings optional (H3 suggestions, contextual tool link hints, events product suggestion).

## Inventory

- `python3 scripts/blog/lexikon-inventory/normalize-and-match-terms.py` — merged.json updated; **personalkostenplanung** → `ordio_covered: true`.

## Redirects

- None required (new canonical slug `personalkostenplanung`).

## Rules

- No change to `blog-new-post-creation.mdc` — standard lexikon workflow; this file documents specifics.

## Content review (2026-03-20)

- Expanded main copy (~2750+ Wörter): Planungsarten (Jahresbudget, Forecast, Projekt), Sonderfälle (Kurzarbeit, Leiharbeit, Buchungslogik), Governance/Versionierung, Datenqualität/Schnittstellen, Kapazitätsplanung-Verknüpfung, HR-Budget-Abgrenzung, zusätzliche Fehlerpunkte (Leiharbeit, SV-Pauschalen), Stand-Zeile 2026 + Rechtshinweis.
- Re-run: `update-post-content.php`, `validate-content-completeness`, `validate-section-depth`, `check-h2-faq-overlap`, `validate-new-post --strict`.

## Follow-up (post-publish polish, 2026-03-20)

- **Tool + product links:** Contextual links added in main copy: `/tools/brutto-netto-rechner`, `/tools/stundenlohnrechner`, `/tools/elterngeldrechner`; lexikon anchors for Mindestlohn/Elternzeit; `/events` via “Webinare und Veranstaltungen von Ordio”.
- **H3s:** Three H3s under “Methoden und Planungsansätze…” (Top-down/Bottom-up; Szenarien/Hybrid; Software/Vier-Schritte).
- **`validate-new-post.php --strict`:** OK — all checks passed (after rephrasing events sentence to avoid false-positive industry “Event” warning).

## Next steps (human)

- [ ] Preview `/insights/lexikon/personalkostenplanung/` on staging (http://localhost:8003).
- [ ] Optional: `make validate` / `make pre-deploy` before merge per team workflow.
- [ ] After deploy: spot-check Rich Results / indexation when live.

**2026-03-20 — Keyword/outline workflow:** `CONTENT_OUTLINE.md` updated with per-H2 **Evidence** + **Gap** (data-driven template); `validate-content-outline-quality.php` no longer warns on missing Evidence. See `KEYWORD_DECISION.md` → Next steps for GSC/SISTRIX refresh cadence.