# Data-driven synthesis: kurzarbeitergeld-rechner

**Auto-generated:** 2026-04-01 (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-01T18:00:00+00:00`

| Keyword | Volume | Competition | CPC (€) |
|---------|--------|-------------|---------|
| kurzarbeitergeld rechner | 4850 | 42 | 0.4 |
| rechner kurzarbeitergeld | 5250 | 42 | 0.4 |
| kurzarbeitergeld berechnen | 2350 | 43 | 1.5 |
| kurzarbeitergeld-rechner | 1000 | 40 | 0.35 |
| kurzarbeitergeld tabelle | 1650 | 38 | 0.2 |
| kurzarbeitergeld höhe | 150 | 31 | 0 |
| kurzarbeitergeld rechner 2026 | 0 | 0 | 0 |
| kurzarbeitergeld rechner 2025 | 250 | 35 | 0.3 |
| kurzarbeitergeld rechner 2024 | 250 | 35 | 0.3 |
| kurzarbeit netto berechnen | 0 | 0 | 0 |
| kurzarbeitergeld-rechner stunden | 150 | 45 | 0.25 |
| kurzarbeitergeld tabelle 2024 | 300 | 36 | 0.15 |
| kug rechner | 0 | 0 | 0 |
| kurzarbeitergeld agentur für arbeit | 80 | 50 | 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-01`–`2026-04-01`
- **URL:** `/tools/kurzarbeitergeld-rechner` — *page row not found in aggregate GSC JSON (re-run collector).*
- **GA4 export:** `docs/content/tools/tools-performance-ga4.json` · range `2026-01-01`–`2026-04-01`
- *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-01` · range `2026-01-01`–`2026-04-01` · **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.