> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the Sistrix data source in Adriel.

## Introduction

Sistrix is a European SEO and SERP analytics platform best known for its Visibility Index (Sichtbarkeitsindex) — a position- and search-volume-weighted score that summarizes a domain's organic visibility for a given country and device. Beyond visibility, Sistrix covers keyword rankings, competitor analysis, ranking distribution, opportunity keywords, and on-page audit data through its Optimizer projects.

The connector reads from the Sistrix REST API and exposes domain-, keyword-, and project-level reports. Country and device are selected per query; the Visibility Index family produces daily time-series data, while most other surfaces return current snapshots. Each data source asset targets a single Sistrix report endpoint, and the metrics and breakdowns available are scoped to that endpoint.

As an SEO connector, visibility, ranking, and keyword data are standardized so widgets can present them alongside other sources. To connect this data source, see [How to connect Sistrix to Adriel](/data-sources/o-z/sistrix/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers the Sistrix account, an optional connected Optimizer project, and the catalog of report endpoints (domain overview, Visibility Index, keyword counts, ranking distribution, competitors, opportunities, ideas, keyword traffic, Optimizer ranking, and Optimizer on-page). The available field set is derived from the selected endpoint.

### Reports data

Reports data is delivered through a daily cache. On first connection, the last 90 days of daily reports are backfilled. Thereafter, the latest 10 days are refreshed twice per day, at 12:00 AM UTC and 2:00 PM UTC. Dates older than the rolling 10-day window remain frozen at their originally stored values.

The connector uses two cache paths depending on the endpoint. Endpoints that support daily granularity — the Visibility Index family — populate a daily time-series cache. All remaining endpoints (domain overview, competitors, ranking distribution, opportunities, ideas, keyword traffic, and most Optimizer surfaces) are served from a file-based snapshot cache that reflects the most recent crawl Sistrix has published and carries no date breakdown.

## Architecture levels

Account → Domain or Optimizer project → Country / Device → Keyword

A data source is scoped to a Sistrix account and a target (domain, host, path, or URL) or an Optimizer project. Country and device select the SERP corpus; keyword-level rows are returned by keyword and Optimizer ranking reports.

## Metrics

<Note>
  **How to read the columns**

  Code style like `value` is the literal Sistrix API field name. *Italic text* describes how a value is produced when it doesn't map cleanly to a single Sistrix field or when it's computed by Adriel. In the field picker, every field carries a `sistrix:` prefix (for example `sistrix:value`); the raw field name is shown here.

  Because each asset targets a single report endpoint, the available metrics depend on which endpoint the data source is configured for — several endpoints reuse the generic `value` field for their headline metric.

  **Data type vocabulary**: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.
</Note>

### Visibility & rankings

| Metric                            | Description                                                                                              | Data type | API Key                                                                                  |
| --------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------- |
| Visibility Index                  | Sistrix's signature organic visibility score for the domain, per country and device (daily time-series). | Number    | `value`                                                                                  |
| Visibility Index (period minimum) | Lowest Visibility Index value in the requested period.                                                   | Number    | `minValue`                                                                               |
| Visibility Index (period maximum) | Highest Visibility Index value in the requested period.                                                  | Number    | `maxValue`                                                                               |
| Visibility Index minimum date     | Date on which the period minimum occurred.                                                               | Date      | `minDate`                                                                                |
| Visibility Index maximum date     | Date on which the period maximum occurred.                                                               | Date      | `maxDate`                                                                                |
| Days in period                    | Number of days covered by the Visibility Index overview.                                                 | Number    | `days`                                                                                   |
| Optimizer project visibility      | Visibility value for a connected Optimizer project (daily).                                              | Number    | `value`                                                                                  |
| SERP position                     | Ranking position of a keyword or URL in the SERP.                                                        | Number    | `position`                                                                               |
| Top-10 rankings                   | Number of a URL's keywords ranking in the top 10.                                                        | Number    | `top10`                                                                                  |
| Top-100 rankings                  | Number of a URL's keywords ranking in the top 100.                                                       | Number    | `top100`                                                                                 |
| Ranking distribution (pages 1–9)  | Count of ranking keywords on each SERP page.                                                             | Number    | `page01`, `page02`, `page03`, `page04`, `page05`, `page06`, `page07`, `page08`, `page09` |
| Ranking count                     | Number of ranking keywords in an Optimizer ranking report.                                               | Number    | `count`                                                                                  |

### Keywords

| Metric                   | Description                                                                                                            | Data type  | API Key                                                          |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------- | ---------- | ---------------------------------------------------------------- |
| SEO keyword count        | Total organic keywords ranking in the top 100 (from the SEO keyword-count report).                                     | Number     | `value`                                                          |
| Top-10 SEO keyword count | Organic keywords ranking in the top 10 (from the top-10 keyword-count report).                                         | Number     | `value`                                                          |
| SEM keyword count        | Paid keywords tracked, returned by the domain overview.                                                                | Number     | `kwcount.sem`                                                    |
| Estimated traffic        | Estimated monthly organic traffic for a keyword or domain keyword.                                                     | Number     | `traffic`                                                        |
| Estimated clicks         | Estimated clicks for a keyword.                                                                                        | Number     | `clicks`                                                         |
| Keyword competition      | Competitiveness score for a keyword.                                                                                   | Number     | `competition`                                                    |
| Opportunity gain         | Estimated traffic gain from acting on an opportunity keyword.                                                          | Number     | `gain`                                                           |
| Search intent: website   | Share of "website" search intent for a keyword.                                                                        | Percentage | `intent_website`                                                 |
| Search intent: know      | Share of informational ("know") search intent.                                                                         | Percentage | `intent_know`                                                    |
| Search intent: visit     | Share of "visit" (local) search intent.                                                                                | Percentage | `intent_visit`                                                   |
| Search intent: do        | Share of transactional ("do") search intent.                                                                           | Percentage | `intent_do`                                                      |
| SERP feature presence    | Presence or count of SERP features for a keyword (best results, organic, related questions, related searches, images). | Number     | `BRES`, `ORGANIC`, `RELATED_QUESTION`, `RELATED_SEARCH`, `IMAGE` |

### Competitors

| Metric            | Description                                                    | Data type | API Key |
| ----------------- | -------------------------------------------------------------- | --------- | ------- |
| Competitive match | Degree of keyword overlap between the domain and a competitor. | Number    | `match` |

### Domain & page

| Metric              | Description                                                                   | Data type | API Key     |
| ------------------- | ----------------------------------------------------------------------------- | --------- | ----------- |
| Domain age          | Age of the domain. *Deprecated upstream; may return `-` instead of a number.* | Number    | `age`       |
| Pages crawled       | Number of pages crawled in the Optimizer project.                             | Number    | `pages`     |
| Crawl errors        | On-page audit error count.                                                    | Number    | `error`     |
| Crawl warnings      | On-page audit warning count.                                                  | Number    | `warnings`  |
| Crawl notices       | On-page audit notice count.                                                   | Number    | `notice`    |
| On-page issue count | Count of a given on-page issue type in the crawl breakdown.                   | Number    | `count`     |
| URL score           | Per-URL on-page score from the Optimizer crawl.                               | Number    | `url_score` |
| Internal links      | Number of internal links found on a crawled URL.                              | Number    | `links_int` |
| External links      | Number of external links found on a crawled URL.                              | Number    | `links_ext` |

## Breakdowns

<Note>
  **How to read the columns**

  Code style like `keyword` is the literal Sistrix API field name. *Italic text* describes how a value is produced when it doesn't map cleanly to a single Sistrix field. Only one breakdown can be applied per query, and the available breakdowns depend on the endpoint the data source targets.
</Note>

### Keyword

| Breakdown | Description                               | API Key         |
| --------- | ----------------------------------------- | --------------- |
| Keyword   | Keyword phrase.                           | `keyword`, `kw` |
| Tags      | Tags applied to the keyword in Optimizer. | `tags`          |

### Page & URL

| Breakdown        | Description                                  | API Key            |
| ---------------- | -------------------------------------------- | ------------------ |
| URL              | Ranking or crawled URL.                      | `url`              |
| Page title       | Page title captured in the Optimizer crawl.  | `title`            |
| HTTP status code | HTTP status observed for the URL.            | `http_code`        |
| Crawl level      | Depth of the URL in the crawl.               | `level`            |
| Meta description | Meta description captured in the crawl.      | `meta_description` |
| Headings         | H1 / H2 / H3 headings captured in the crawl. | `h1`, `h2`, `h3`   |

### Competitor

| Breakdown         | Description                                                              | API Key  |
| ----------------- | ------------------------------------------------------------------------ | -------- |
| Competitor domain | Competing domain returned by the SEO/SEM or Optimizer competitor report. | `domain` |

### Geography & device

| Breakdown     | Description                               | API Key        |
| ------------- | ----------------------------------------- | -------------- |
| Country       | Sistrix country code for the SERP corpus. | `country`      |
| Device        | Desktop or mobile SERP.                   | `device`       |
| Search engine | Optimizer search-engine identifier.       | `searchengine` |

### Time

| Breakdown | Description                                                | API Key |
| --------- | ---------------------------------------------------------- | ------- |
| Date      | Reporting date (Visibility Index and other daily reports). | `date`  |

### Time & date grouping

<Note>
  Adriel groups Sistrix's daily-granularity results into these standard views for reporting alongside other connectors.
</Note>

| Breakdown           | Description                                                  |
| ------------------- | ------------------------------------------------------------ |
| Auto Time Breakdown | Automatically picks the best granularity for the date range. |
| Daily               | Split reports by day.                                        |
| Weekly              | Split reports by week.                                       |
| Monthly             | Split reports by calendar month.                             |

## Limitations

Based on the current connector, Sistrix has:

* **Endpoint-scoped fields** — each data source asset targets a single Sistrix report endpoint, and the available metrics and breakdowns are limited to that endpoint's field set with no overlap guarantee across endpoints.
* **One breakdown per query** — requesting more than one breakdown at a time is rejected.
* **Country and device required for most reports** — most domain and keyword reports require a country and device; changing either returns a different result set because the underlying SERP corpus changes.
* **Daily time-series only for the Visibility Index family** — Visibility Index endpoints produce daily time-series; domain overview, competitors, ranking distribution, opportunities, ideas, keyword traffic, and most Optimizer endpoints return a current snapshot with no date breakdown.
* **90-day initial history, 10-day refresh window** — first connection backfills 90 days of daily data; only the latest 10 days are refreshed thereafter, and older dates remain frozen at their stored values.
* **Credit-based consumption** — Sistrix bills API usage by credits ([Sistrix API documentation](https://www.sistrix.com/api/)); when credits are exhausted a `QUOTA_EXCEEDED` error is raised and the connector does not auto-retry. The standalone SEM keyword-count report was removed to limit credit use (SEM keyword count remains available through the domain overview).
* **Deprecated domain age** — the domain-age report is deprecated upstream and may return `-` instead of a numeric value.
* **Social endpoints unavailable** — Sistrix's `domain.social.*` surfaces are not provisioned by the connector.
* **Generic data source** — Sistrix data is presented in a generic table and cannot be natively combined with other connector types unless they share identical breakdowns; cross-connector analysis requires data-blending settings.

## API references

* [Sistrix API documentation](https://www.sistrix.com/api/)
* Sistrix API base URL: `https://api.sistrix.com/`

## See also

* [How to connect Sistrix](/data-sources/o-z/sistrix/how-to-connect) (paired how-to)
* [Semrush data reference](/data-sources/o-z/semrush/data-reference) — for an alternative SEO platform
* [SE Ranking data reference](/data-sources/o-z/se-ranking/data-reference) — for an alternative SEO rank tracker
* [Google Search Console data reference](/data-sources/g-n/google-search-console/data-reference) — for organic search performance