# Data-driven synthesis: krankengeld-rechner

**Auto-generated:** 2026-04-08 (UTC) · **Script:** `v2/scripts/tools/generate-tool-data-synthesis.php`

This file is the **single editorial anchor** for metrics-backed decisions: meta, H2s, FAQs, and the next iteration. Regenerate after refreshing exports (see [DATA_COLLECTION_TOOLS.md](../../DATA_COLLECTION_TOOLS.md) § *Per-tool synthesis*).

## 1. SISTRIX (market / keyword demand)

- **Source:** `data/keywords-sistrix.json` · generated `2026-04-08T20:29:38+00:00`

| Keyword | Volume | Competition | CPC (€) |
|---------|--------|-------------|---------|
| krankengeld rechner | 19000 | 47 | 0.2 |
| krankengeldrechner | 16000 | 57 | 0.3 |
| krankengeld berechnen | 10000 | 50 | 0.2 |
| krankengeld online berechnen | 10 | 0 | 0 |
| krankengeld höhe | 10300 | 50 | 0.4 |
| krankengeld 70 prozent | 10 | 11 | 0 |
| krankengeld 90 prozent netto | 0 | 0 | 0 |
| entgeltfortzahlung 6 wochen | 40 | 16 | 0 |
| krankengeld dauer 78 wochen | 0 | 0 | 0 |
| krankengeld sgb v | 60 | 18 | 0 |
| einkommenslücke krankengeld | 0 | 0 | 0 |
| gesetzliche krankenkasse krankengeld | 10 | 0 | 0 |

**Use:** Prioritise copy and H2 wording where **volume** aligns with GSC queries (see §3). High **competition** implies stronger SERP rivals — skyscraper depth and differentiated snippets (modes, exports).

## 2. Google Search Console & GA4 (our site, same date windows as JSON)

- **GSC page export:** `docs/content/tools/tools-performance-gsc.json` · range `2026-01-08`–`2026-04-08`
- **URL:** `/tools/krankengeld-rechner` — *page row not found in aggregate GSC JSON (re-run collector).*
- **GA4 export:** `docs/content/tools/tools-performance-ga4.json` · range `2026-01-08`–`2026-04-08`
- *Path not found in GA4 JSON — re-run `collect-tools-performance-ga4.php`.*

**Interpretation:** GSC clicks vs GA4 sessions will not match 1:1 (channel mix, consent, sampling). Use both: GSC for **search** diagnosis; GA4 for **on-site** engagement after click.

## 3. GSC queries (query dimension, page = exact URL)

- **Source:** `data/gsc-queries.json` · exported `2026-04-08` · range `2026-01-08`–`2026-04-08` · **0** query rows

### Top 15 by impressions

| # | Query | Clicks | Impressions | CTR | Pos. |
|---|-------|--------|-------------|-----|------|

### Top 15 by clicks

| # | Query | Clicks | Impressions | CTR | Pos. |
|---|-------|--------|-------------|-----|------|

**Note:** Sum of clicks in this export (**0**) is usually **lower** than GSC page-level clicks — not all queries are shown (privacy thresholds, “other”), and dimensions differ. Trust **page-level** totals in §2 for overall CTR; use §3 for **which queries** to target in copy.

## 4. How this feeds the content loop

1. **Outline / H2s:** Map top impressions + high-CTR gaps to sections (already reflected in [`CONTENT_OUTLINE.md`](./CONTENT_OUTLINE.md)).
2. **Meta title & description:** Must include the head term and modifiers seen in §3 (e.g. „prozent rechner“, „€“).
3. **FAQs:** Align questions with query phrasing + filtered PAA (`data/paa-questions.json`).
4. **Next iteration (e.g. +8 weeks):** Re-run collectors → regenerate this file → compare §2–§3 to previous commit (diff in git) → update outline and backlog.

## Post-deploy QA (manual)

Nach Livegang für `https://www.ordio.com/tools/krankengeld-rechner`:

1. **Rich Results Test** (Google): Canonical-URL prüfen; `WebPage`, `SoftwareApplication`, `HowTo`, `FAQPage` (aus FAQ-JSON) und `BreadcrumbList` ohne Fehler.
2. **Search Console:** URL-Prüfung / Indexierung; nach 1–2 Wochen Performance (Klicks, CTR, Position) mit diesem Export und `tools-performance-gsc.json` abgleichen.
3. **Optional:** PAA-Collector erneut ausführen, wenn Netzwerk/API wieder stabil ist, und `paa-questions.json` committen.