# VIP marketing pages — SISTRIX tiers, domain SERP, and data utilization

**Last Updated:** 2026-04-02

**Purpose:** Single reference for **when to spend more SISTRIX credits** on high-value marketing URLs (product features, Branchen, static Tier A including pricing and homepage) versus staying frugal on **scale-tier** surfaces (blog, bulk tools). Aligns with [SISTRIX API documentation](https://www.sistrix.com/api/) (credits per response, weekly allocation).

**Registry:** [`marketing-pages-registry.json`](../marketing-pages-registry.json) · **Credit log:** `v2/data/blog/sistrix-credits-log.json` · **Playbook:** [PAGE_IMPROVEMENT_DATA_PLAYBOOK.md](../../PAGE_IMPROVEMENT_DATA_PLAYBOOK.md)

---

## 1. Two tiers

| Tier | Surfaces | SISTRIX posture |
|------|----------|-----------------|
| **Scale** | Blog posts (lexikon/ratgeber), many `/tools/*` URLs, long-tail templates | Prefer **`keyword.seo`** (cheap SERP top 10), batch **`keyword.seo.metrics`**, **`marketplace.keyword.search.ideas`**. Avoid wide use of **`keyword.domain.seo` + `kw`** (~**100 credits per keyword** in typical configs — see [blog-data-collection.mdc](../../../.cursor/rules/blog-data-collection.mdc), [SISTRIX_ENDPOINTS_AND_REPORTS.md](../../blog/SISTRIX_ENDPOINTS_AND_REPORTS.md)). |
| **VIP** | Registry **`surface`: `product`** (`feature-*`), **`industry`** (Branchen hub + verticals), **`static`** Tier A (`homepage`, `preise`, `kunden`, `ueber-uns`, `partner`, `demo-vereinbaren`) | Run the **full baseline stack** (GSC queries, metrics, ideas, optional **`keyword.seo`** top 10 via feature script or equivalent research). **Selective** **`keyword.domain.seo` + `kw`** is **in policy** for **1–5 head terms per page per sprint** when GSC + cheap SERP are not enough to decide positioning, cannibalization, or FAQ/meta focus. |

**Still out of policy:** Firing **`keyword.domain.seo` + `kw`** for **every** keyword in `keywords-sistrix.json` or `related_keywords` without prioritization (credit burn, weak decisions).

---

## 2. Default stack (all VIP pages)

1. **GSC:** Page aggregate + **`collect-tool-gsc-queries.php`** → `{docs_dir}/data/gsc-queries.json` (optional fixed `--start`/`--end` + [compare](../../tools/GSC_QUERY_EXPORT_SCHEMA.md)).
2. **SISTRIX metrics + ideas:** `collect-page-keywords-sistrix.php --page=<registry_id>` → `data/keywords-sistrix.json`.
3. **Cheap SERP (product features):** `collect-feature-page-keyword-serp.php` + pipeline flag `--with-sistrix-serp` → `data/sistrix-keyword-serp.json` (**`keyword.seo`**, ~1 credit/keyword when not cached).
4. **Synthesis:** Surface-specific generator (e.g. `generate-feature-page-data-synthesis.php`, `generate-industry-data-synthesis.php`) or hand-maintained `DATA_DRIVEN_SYNTHESIS.md`.
5. **Editorial:** Update `data/KEYWORD_DECISION.md`; map insights to FAQ H2s, meta hypotheses, internal links.

---

## 3. Expensive stack: `keyword.domain.seo` + `kw` (VIP only)

**What it adds:** Domain-scoped SERP slice for a single keyword (cost **~100 credits per keyword** — confirm in API response `credits`; see [SISTRIX API](https://www.sistrix.com/api/)).

**When to use (any must be true):**

- Head term is **business-critical** and cheap SERP + GSC still leave **unclear** competitive set or Ordio visibility story.
- Stakeholder sprint on **pricing**, **homepage**, or a **flagship** feature/Branchen LP with approved budget.
- You will **consume** the output in synthesis + `KEYWORD_DECISION.md` + backlog within the same ticket (see §5).

**How to run (automated):**

```bash
php v2/scripts/marketing-pages/collect-marketing-page-domain-kw-serp.php --page=feature-schichtplan [--dry-run] [--limit=3]
```

- **Input keywords:** `data/target-keywords.json` — **primary** first, then **secondary** (deduped), hard cap **5** (override with `--limit=1..5`).
- **Surfaces allowed:** registry `product`, `industry`, or `static`.
- **Output:** `{docs_dir}/data/sistrix-domain-kw-serp.json` (committed when used for a sprint).
- **API caveat:** For many accounts, **`keyword.domain.seo` with only `kw`** returns SISTRIX `status: fail` (e.g. error 2000 *domain not found*). The collector then uses **`keyword.seo`** for the same keywords, reusing the **same disk cache** as `collect-feature-page-keyword-serp.php` (`feature_serp_full_*`). Rows include `data_source` (`keyword.domain.seo_kw` vs `keyword.seo_fallback`) and optional `domain_api_message` so synthesis and audits stay honest about credit use.

**Product feature pipeline:**

```bash
bash v2/scripts/product-pages/run-feature-page-research-pipeline.sh feature-schichtplan --with-sistrix-serp --with-sistrix-domain-kw
```

Run **`php v2/scripts/blog/test-api-access.php --all`** before batch calls. Check weekly remaining credits before a domain-kw batch.

---

## 4. Per-sprint credit budget template (copy into ticket / PR)

| Item | Planned | Credits (estimate) |
|------|---------|---------------------|
| Page / registry id | | |
| `collect-page-keywords-sistrix` | Y/N | (varies; cache) |
| `keyword.seo` SERP (`sistrix-keyword-serp.json`) | Y/N | ~1 × N keywords |
| `keyword.domain.seo` + `kw` (`sistrix-domain-kw-serp.json`) | Y/N | ~100 × K keywords (K ≤ 5) |
| Serper / Firecrawl | Y/N | per vendor |
| **Total estimate** | | |

**Artifact → consumer (required):**

| New / refreshed file | Must appear in |
|---------------------|----------------|
| Any `data/*.json` above | `DATA_DRIVEN_SYNTHESIS*.md` and/or `KEYWORD_DECISION.md` |
| Domain-kw JSON | Feature: `generate-feature-page-data-synthesis.php` section 5; industry/static: hand section in synthesis or notes |

---

## 5. Data utilization gate

Do **not** add recurring exports that nobody reads.

- After each refresh: regenerate or patch the surface **synthesis** doc and **at least one** of: `KEYWORD_DECISION.md`, FAQ outline, meta notes, or [PRODUCT_FEATURE_SEO_IMPROVEMENT_BACKLOG.md](../product-pages/PRODUCT_FEATURE_SEO_IMPROVEMENT_BACKLOG.md) (or static/industry backlog).
- If a file is **deprecated**, say so in `KEYWORD_DECISION.md` or delete in a dedicated PR.
- Checklist: [PAGE_IMPROVEMENT_ITERATION_CHECKLIST.md](../../PAGE_IMPROVEMENT_ITERATION_CHECKLIST.md) §3.

---

## 6. Related docs

- [DATA_COLLECTION_PRODUCT_FEATURES.md](../product-pages/DATA_COLLECTION_PRODUCT_FEATURES.md)
- [DATA_COLLECTION_BRANCHEN.md](../industry-pages/DATA_COLLECTION_BRANCHEN.md)
- [DATA_COLLECTION_STATIC_SITE.md](../static-pages/DATA_COLLECTION_STATIC_SITE.md)
- [FEATURE_PAGE_IMPROVEMENT_WORKFLOW.md](../product-pages/FEATURE_PAGE_IMPROVEMENT_WORKFLOW.md)
- [.cursor/rules/marketing-pages-seo-data.mdc](../../../.cursor/rules/marketing-pages-seo-data.mdc)