# Data-driven synthesis: Product feature `feature-appstore` (`/appstore`)

**Auto-generated:** 2026-04-02 (UTC) · **Script:** `v2/scripts/product-pages/generate-feature-page-data-synthesis.php`

**Registry `docs_dir`:** `docs/content/pages/product-pages/appstore`. Add human notes in `KEYWORD_DECISION.md`, FAQ outlines, and post-deploy checks. **FAQ SSOT:** `misc-faqs` + `faq-answers-optimized.json` per [PRODUCT_PAGE_FAQ_GUIDE.md](../PRODUCT_PAGE_FAQ_GUIDE.md).

## 1. GSC page aggregate (`data/performance-gsc.json`)

- **Date range:** `2026-01-02`–`2026-04-02`
- **Clicks:** 131 · **Impressions:** 29688 · **Avg position:** 1.72

## 2. GSC queries (top 15 by impressions, `data/gsc-queries.json`)

| Query | Clicks | Impressions | Position |
|-------|--------|-------------|----------|
| ordio | 26 | 18947 | 1.28 |
| ordio login | 20 | 6082 | 1.05 |
| ordio app | 22 | 697 | 2.99 |
| ordio app download | 22 | 299 | 2.85 |
| ordio workspace | 0 | 265 | 1.15 |
| ordio gmbh | 0 | 213 | 2.37 |
| ordio anmelden | 1 | 163 | 1 |
| ordio log in | 1 | 104 | 1 |
| ordio.com | 0 | 72 | 1.08 |
| ordio zeiterfassung | 0 | 46 | 28.17 |
| ordio logo | 0 | 39 | 1.21 |
| ordio datev schnittstelle | 0 | 33 | 1.7 |
| arbeitsorganisation app | 0 | 31 | 19.61 |
| ordio terminal app | 1 | 29 | 9.03 |
| ordio schichtplanung | 0 | 24 | 3.08 |

## 3. SISTRIX (`data/keywords-sistrix.json`)

| Keyword | Notes |
|---------|-------|
| ordio app | volume≈30 |
| ordio integrationen | volume≈0 |
| ordio app store | volume≈0 |
| ordio schnittstellen | volume≈0 |
| datev schnittstelle ordio | volume≈0 |
| personalsoftware integrationen | volume≈0 |
| kassensystem ordio anbindung | volume≈0 |

## 4. SISTRIX SERP top 10 (`data/sistrix-keyword-serp.json`)

- **Collected:** `2026-04-02T14:55:56Z` · **Credits (this run):** 8
- **Source:** SISTRIX API keyword.seo (limit=10, full SERP incl. ordio.com) — v2/scripts/product-pages/collect-feature-page-keyword-serp.php

| Keyword | Ordio rank | #1 non-Ordio domain |
|---------|------------|---------------------|
| ordio integrationen | — |  |
| personalsoftware schnittstellen | — |  |
| hr software integrationen deutschland | — |  |
| kassensystem personal tool anbindung | — |  |
| workforce management api | — |  |
| datev schnittstelle zeiterfassung | — |  |
| pos integration schichtplanung | — |  |
| ordio app store | — |  |

Narrative and keyword picks: `data/KEYWORD_DECISION.md`.

## 5. SISTRIX domain-keyword SERP (VIP, `data/sistrix-domain-kw-serp.json`)

*Optional —* `keyword.domain.seo` + `kw` (~100 credits/keyword, cap 5): `php v2/scripts/marketing-pages/collect-marketing-page-domain-kw-serp.php --page=feature-appstore` or pipeline `--with-sistrix-domain-kw`. See [VIP_MARKETING_SEO_DATA_TIERS.md](../../marketing-pages/VIP_MARKETING_SEO_DATA_TIERS.md).

## 6. PAA / research (`data/faq-research.json`)

- **Source note:** Serper MCP google_search (gl=de, hl=de) — SERPER_API_KEY was not set in CLI; organic + related intents merged manually for FAQ stems.
- **Question stems / PAA:**
  - Wie integriere ich mein Kassensystem in Ordio? (Help-Center intent — Konfiguration über Einstellungen / Appstore)
  - Welche Integrationen bietet Ordio für Lohn und DATEV?
  - Wo finde ich API- und Partner-Dokumentation für Ordio?

## 7. Competitor FAQ scrape (`competitor-faq-analysis.json`)

- **Collected:** 2026-04-02 · Firecrawl MCP scrape (Personio marketplace, Deputy apps, Papershift homepage for FAQ-style topics) — topic extraction for FAQ intents; no competitor wording copied into Ordio FAQs. Registry `competitor_urls` uses Papershift marketplace for scripted re-runs.
- **:** 0 FAQ-like extractions
- **:** 0 FAQ-like extractions
- **:** 0 FAQ-like extractions

## 8. Editorial (manual)

- **Primary keyword:** `data/KEYWORD_DECISION.md`.
- **FAQ iteration:** [FEATURE_PAGE_IMPROVEMENT_WORKFLOW.md](../FEATURE_PAGE_IMPROVEMENT_WORKFLOW.md).
- **Post-deploy:** Re-check GSC/GA for `/appstore` after 4–8 weeks.

## 9. FAQ diff ideas (from data — human review)

- Map high-impression GSC queries (section 2) and PAA stems (section 6) to missing or weak FAQ H2s.
- Use SERP gaps (sections 4–5: Ordio weak/absent) and competitor headings (section 7) as **topic** hints; do not copy wording.
- After edits: `python3 v2/scripts/product-pages/validate-faq-answers.py --page=…` (registry `feature-*` or legacy key) and Rich Results Test.