# SISTRIX: URL, domain, and keyword workflow for tools pages

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

**API reference:** [SISTRIX API documentation](https://www.sistrix.com/api/)

This doc explains how **blog** and **tools** pipelines use SISTRIX differently and when to add **domain-** or **URL-level** insight for a Rechner without burning credits.

## What the tools pipeline already does

- **`keyword.seo.metrics`** — per candidate keyword: volume, competition, CPC (`collect-tool-keywords-sistrix.php` → `data/keywords-sistrix.json`).
- **`keyword.questions`** — PAA-style questions (`collect-tool-paa-questions.php`).
- **`keyword.seo`** — top ranking URLs for a keyword, used for competitor scraping (`collect-tool-competitor-analysis.php`).

That is enough for **market size**, **FAQ ideas**, and **skyscraper competitor lists**.

## When to add domain / URL insight

Use extra endpoints only when a sprint needs:

1. **“Does ordio.com rank for keyword X?”** alongside competitors — blog scripts use patterns around `keyword.domain.seo` and related helpers under `v2/scripts/blog/` (see [SISTRIX_ENDPOINTS_AND_REPORTS.md](../blog/SISTRIX_ENDPOINTS_AND_REPORTS.md)). For a **single tool**, prefer:
   - **GSC query export** for that URL (ground truth for *your* clicks/impressions).
   - SISTRIX **`keyword.seo`** for *who* ranks in top 10 (already in competitor JSON).

2. **Expensive calls:** Full SERP pull per keyword via some `keyword.domain.seo` variants can cost **~100 credits per keyword** in some configurations — see blog rule [blog-data-collection.mdc](../../.cursor/rules/blog-data-collection.mdc). **Do not** batch these for all tools by default. (Registry **VIP marketing** pages—features, Branchen, static Tier A—use a **selective** policy instead: [VIP_MARKETING_SEO_DATA_TIERS.md](../pages/marketing-pages/VIP_MARKETING_SEO_DATA_TIERS.md).)

## Practical rule for tools sprints

| Question | Source first |
|----------|----------------|
| Which queries drive our URL? | GSC `collect-tool-gsc-queries.php` |
| Market size / CPC / competition | `keyword.seo.metrics` (existing) |
| Who ranks top 10? | `keyword.seo` in competitor analysis |
| Visibility / domain portfolio | Domain-level scripts in `v2/scripts/blog/` (shared domain, not per-tool) |

## Optional future automation

A dedicated `collect-tool-sistrix-domain-positions.php` would only be justified if product asks for **routine** Ordio-vs-SERP alignment beyond GSC — and must log credits via `v2/helpers/sistrix-credit-log.php`. Until then, use blog diagnostics **ad hoc** or manual SISTRIX UI.

## Related

- [DATA_COLLECTION_TOOLS.md](DATA_COLLECTION_TOOLS.md)
- [PAGE_IMPROVEMENT_ITERATION_CHECKLIST.md](../PAGE_IMPROVEMENT_ITERATION_CHECKLIST.md)