# Schichtplan FAQ — pilot diff ideas (from data, 2026-04-02)

**Context:** `run-feature-page-research-pipeline.sh feature-schichtplan` + global GSC/GA + `split-product-gsc-to-registry-pages.php` + refreshed `gsc-queries.json` / `faq-research.json` / `DATA_DRIVEN_SYNTHESIS.generated.md` (window 2026-01-02–2026-04-02). **Not applied copy** — human review + [PRODUCT_PAGE_FAQ_GUIDE.md](../../PRODUCT_PAGE_FAQ_GUIDE.md) before changing live `misc-faqs/product_shiftplan.json` or `schichtplan-neu`.

## Observations

- **Branded navigational cluster** (`ordio login`, `ordio`, `ordio anmelden`) dominates impressions; FAQ should stay focused on **Schichtplan/Dienstplan** intent, not login support (handle in help/docs if needed).
- **Generic head term** `schichtplanung` appears with high impressions and mid tail position — first FAQ already contrasts Dienstplan/Schichtplan and product positioning; optional future tweak: one short clause naming „Schichtplanung“ as Oberbegriff if CTR for that query stays weak.
- **Product-qualified** queries (`ordio schichtplanung`) — ensure one FAQ bridges product value without keyword stuffing titles.

## Suggested checks (not prescriptive rewrites)

1. Compare top 15 **non-brand** queries in `gsc-queries.json` against current FAQ question list in `faq-answers-optimized.json` / `misc-faqs/product_shiftplan.json`.
2. After Serper run (`serper-paa-research.py --page=feature-schichtplan`), merge net-new PAA strings that match gaps; drop near-duplicates.
3. Keep **parity** between live Schichtplan and `schichtplan-neu` draft JSON per FAQ guide before any URL swap.

## Competitor scrape

- Run `python3 v2/scripts/product-pages/scrape-competitor-faqs.py --page=feature-schichtplan` when `FIRECRAWL_API_KEY` is set; registry supplies `competitor_urls`. Use output only for **coverage gaps**, not phrasing.