# Dienstplan Pillar — Keyword & FAQ decisions

**URL:** https://www.ordio.com/insights/dienstplan  
**Last updated:** 2026-04-10 (FAQ refresh sprint)

## 1. Seed keywords (pre–data collection)

Derived from page meta, TOC/H2s on `v2/pages/pillar_dienstplan.php`, and cluster hub [`docs/content/blog/TIER1_PILLAR_MAPPING.md`](../../blog/TIER1_PILLAR_MAPPING.md).

| Cluster | Examples (deduped seeds) |
|--------|---------------------------|
| Head | dienstplan, schichtplan, dienstplanung |
| How-to | dienstplan erstellen, schichtplan erstellen, dienstplan online |
| Tool / channel | dienstplan software, dienstplan app, dienstplan excel, dienstplan tool |
| Legal / ops | dienstplan gesetz, dienstplan pflicht, dienstplan frist, dienstplan rechtlich bindend |
| Industry | dienstplan pflege, schichtplan pflege |
| Automation | dienstplan ki, automatische dienstplanung |

**Merge rules (near-duplicates):** *Schichtplan* vs *Dienstplan* → one terminology FAQ; *Software* / *App* / *Programm* → one selection FAQ; *KI* / *Generator* / *automatisch* → one automation FAQ.

## 2. Data artifacts (SSOT paths)

| Source | File |
|--------|------|
| GSC queries | `data/gsc-queries.json` |
| SISTRIX metrics | `data/keywords-sistrix.json` |
| SISTRIX SERP (cheap) | `data/sistrix-keyword-serp.json` |
| GA4 | `data/ga4-landing.json` — `php v2/scripts/seo/collect-page-performance-ga4.php --path=/insights/dienstplan --output=...` |
| Serper notes | `data/faq-research-serper.json` |
| PAA / SERP narrative | `SERP_ANALYSIS.md`, `COMPETITIVE_ANALYSIS.md` |

## 3. Post-research decisions (2026-04-10)

- **Primary GSC demand:** Head **dienstplan** (very high impressions), clusters **dienstplanung**, **software/programm/app/tool**, **automatisch/automatisiert** (strong mid-funnel software intent), **dienstplan erstellen** (how-to).
- **VIP SISTRIX (`keyword.domain.seo` + kw):** **Not run** — cheap `keyword.seo` SERP + GSC already show competitor sets; no orphan expensive exports (per `VIP_MARKETING_SEO_DATA_TIERS.md`).
- **Serper PAA:** API returned empty `peopleAlsoAsk` for tested DE queries; intents inferred from **GSC query list** + organic titles (see `faq-research-serper.json`).
- **Meta tweak:** Description + OG description now include **Schichtplan** synonym to align with terminology FAQ and head-term coverage (`pillar_dienstplan.php`).

## 4. Intent → FAQ slot mapping (12 FAQs)

| # | Intent covered | GSC / research notes |
|---|----------------|------------------------|
| 1 | Definition | “was ist”, head term |
| 2 | Dienstplan vs Schichtplan | terminology / SERP differentiation |
| 3 | How-to process | dienstplan erstellen, wie erstelle ich… |
| 4 | Inhalt / Struktur | was muss drauf / aussehen (merged) |
| 5 | Frist / Verbindlichkeit | wann fertig, Änderungen |
| 6 | Gesetzliche Pflicht | ist Pflicht, ArbZG/Tarif |
| 7 | Verantwortung | wer erstellt |
| 8 | Excel vs Software | excel, tool, digital |
| 9 | Software/App/Programm-Wahl | software dienstplan, programm, app |
| 10 | Pflege / Schichtbetrieb | pflege, sozialarbeit (vertical) |
| 11 | KI / Automatisierung / Generator | KI, automatisch, Generator intents |
| 12 | Zeiterfassung ↔ Plan | cluster bridge, Zeiterfassung pillar |

**Count:** **12** — down from 17 by merging duplicate how-to, KI+ChatGPT, “beste” Erstellung, rechtliche Split-Redundanz, and two “Aussehen”-Fragen.

**Body overlap:** FAQs use **micro-intents** (Checklisten, Toolwahl, Pflege-Kurzfokus) vs. H2-Abschnitte Einführung/Modelle/Gesetz/Erstellung/Tool/KI/Vorlagen/Branchen — keine 1:1-Spiegelung der Überschriften.

## 5. Meta alignment

- **Description:** Updated to mention **Schichtplan** alongside Dienstplan (keyword alignment + user language).
- **Title:** Unchanged (“Definition, Erstellung & Software”) — still matches primary intents.