# Keyword decision — Über uns (`/ueber-uns`)

**Last Updated:** 2026-04-08

## Primary intent

- **Chosen primary:** Über Ordio.
- **Rationale:** Strong brand and entity queries land on this URL (GSC: `ordio`, `ordio gmbh`, `was ist ordio`); page supports E-E-A-T and mission narrative per [`company-pages-documentation.md`](../../company-pages-documentation.md).

## Evidence (2026-01-08 – 2026-04-08)

| Source | Path | Notes |
|--------|------|--------|
| GSC page aggregate | `data/performance-gsc.json` | ~165 clicks, ~37k impressions, avg position ~1.35 |
| GSC queries | `data/gsc-queries.json` | Top clicks: ordio, ordio support, ordio gmbh, ordio login, ordio jobs, ordio köln. High impressions, low/zero clicks: was ist ordio, ordio workspace, ordio schichtplanung |
| SISTRIX ideas | `data/keywords-sistrix.json` | Brand + secondary seeds; low reported volume for head terms (expected for `/ueber-uns`) |
| SERP snapshot | `data/sistrix-keyword-serp.json` | 8 keywords, 8 credits (2026-04-08) |
| PAA / questions | `data/faq-research.json` | GSC-derived + editorial stems; **Serper not run** (no `SERPER_API_KEY`) |
| Synthesis | [`DATA_DRIVEN_SYNTHESIS.generated.md`](../DATA_DRIVEN_SYNTHESIS.generated.md) | Auto merge of above |

## FAQ intents mapped to data

| FAQ theme | GSC / research signal |
|-----------|------------------------|
| Was ist Ordio? | `was ist ordio` (impressions), `ordio software`, `firma ordio` |
| Mission / Herkunft | On-page hero; origin story (Sushi Ninja) |
| Für wen? | `ordio schichtplanung`, `ordio app`; link to `/branchen` |
| Standort | `ordio köln`, `ordio gmbh`; legal detail → `/impressum` |
| Karriere | `ordio jobs` |
| Support / Login | `ordio support`, `ordio login`, `ordio workspace` — clarify scope; not primary content of Über uns |

## Cannibalization

- **Product features** (`/schichtplan`, Zeiterfassung, etc.): About-FAQs only **bridge** with one link each; no long feature copy.
- **Preise / Demo:** Commercial CTAs point to `/preise` and `/demo-vereinbaren` only (no `/kostenlos-testen`).

## VIP domain SERP (`keyword.domain.seo`)

- **Not run** for this sprint: cheap SERP + GSC already clarify intent; no positioning conflict requiring ~100 cr/keyword. Revisit if a specific head term shows cannibalization with another URL.

## Next data refresh

- Re-run `bash v2/scripts/marketing-pages/run-page-research-pipeline.sh ueber-uns --with-gsc-queries --with-sistrix-serp --with-synthesis` monthly/quarterly; add `--with-competitor-faq-scrape` when `FIRECRAWL_API_KEY` is set; add Serper when `SERPER_API_KEY` is set.