# Keyword decision — Dokumentenmanagement (`feature-dokumentenmanagement`)

**Last Updated:** 2026-04-02

## Primary intent (final)

- **Chosen primary:** `Dokumentenmanagement Personal` — HR-scoped, matches SISTRIX seed traffic and avoids positioning Ordio as generic enterprise DMS.
- **Supporting head terms:** `HR Dokumentenmanagement` (SISTRIX ~10; Haufe #1 in SERP snapshot).
- **Commercial / long-tail secondaries:** `dokumente automatisch erstellen`, `dokumentenmanagement webbasiert`, `dokumentenmanagement app`, `dokumentenmanagement für gastronomie` — from **GSC** impressions (queries with no/low clicks but visible demand).
- **Rationale:** GSC (2026-01-02–2026-04-02): 14 clicks, 1079 impressions, avg position ~22.9 — prioritize FAQ and meta intents that match high-impression queries (automation, web/app, vertical). SISTRIX SERP for primary shows HR/personalakte vendors; Ordio not in top 10 — content should clarify **HR suite + Akte + Dokumente** story.

## Evidence

| Source | Path / note |
|--------|-------------|
| Target keywords (seed) | `data/target-keywords.json` |
| GSC queries | `data/gsc-queries.json` (68 rows) |
| GSC page slice | `data/performance-gsc.json` |
| Global GSC / GA4 | `docs/content/pages/product-pages-performance-gsc.json`, `product-pages-performance-ga4.json` |
| SISTRIX metrics + ideas | `data/keywords-sistrix.json` |
| SISTRIX SERP | `data/sistrix-keyword-serp.json` (26 cr, 2026-04-02) |
| PAA / stems | `data/faq-research.json` (GSC mining + editorial + **Serper MCP** spot searches 2026-04-02; CLI Serper skipped — no `SERPER_API_KEY`) |
| Competitor topics | `competitor-faq-analysis.json` (Firecrawl MCP: talentmagazin glossar; Personio `/dokumentenmanagement/` **404** — removed from registry) |
| Synthesis | `DATA_DRIVEN_SYNTHESIS.generated.md` |

## Serper / PAA cross-check (2026-04-02)

- **MCP queries:** „Dokumentenmanagement Personal HR“, „Mitarbeiterdokumente digital verwalten Software“, „Was ist Dokumentenmanagement im HR“ — organic set dominated by DMS/HR education URLs; aligns with **definition + HR context** FAQs.
- **People Also Ask:** not returned in API payload for these calls; stems in `faq-research.json` filled editorially from SERP titles/snippets and GSC.

## Differentiation vs `/digitale-personalakte`

- **Personalakte:** Mitarbeiterakte als Ganzes (Stammdaten, typische HR-Unterlagen).
- **Dokumentenmanagement:** Ablage, Abfragen, Fristen, Freigaben, Suche — **one dedicated FAQ** + link; keine doppelten Akten-FAQs.

## Do not chase

- **Pure brand:** `ordio`, `ordio app` alone — keine isolierte Login-FAQ.
- **Competitor brands** in FAQ-Text.
- **SISTRIX `related_keywords`** when polluted by unrelated „personalisiert“ retail terms — rely on seed metrics + GSC + SERP.

## Registry competitors

- `https://talentmagazin.de/glossar/dokumentenmanagement/`
- `https://activate-hr.de/allgemein/unterschied-digitale-personalakte-dokumentenmanagement/`

## VIP SISTRIX

- **`keyword.domain.seo` + `kw`:** not used — cheap SERP + GSC sufficient for this sprint.

## Open follow-ups

- 28-day GSC check post-deploy on `/dokumentenmanagement`.
- Set `SERPER_API_KEY` / `FIRECRAWL_API_KEY` locally to run CLI `serper-paa-research.py` / `scrape-competitor-faqs.py` for automated JSON refresh.