SEO

XOVI

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The In-House SEO Lead v1.0 · The Agency Owner v1.0 · The Technical SEO v1.0 · The Content Strategist v1.0 · The Data Analyst v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 4 Oct 2026

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The In-House SEO Lead

Weighted verdict

Owns organic traffic for one large German site and reports on it monthly. Wants German-language keyword data that is not an afterthought, rankings she can defend when they disagree with Search Console, and audit findings specific enough to become a developer ticket.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The In-House SEO Lead

Crawling & technical audit

How this is scored

Site crawling at real scale: what the crawler finds, how deeply it checks, whether Core Web Vitals and indexation problems are diagnosed rather than merely listed.

0 — No site crawler; the product is keyword data only.

3 — A crawler with a low page cap that reports broken links and missing tags, with no prioritisation and no rendering of JavaScript.

5 — Scheduled crawls at a stated page limit, JavaScript rendering, issue categories with severity, and Core Web Vitals pulled per template.

8 — Log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, and issues prioritised by traffic impact rather than count.

10 — The audit is diagnostic rather than a list: crawl budget analysed, rendering differences surfaced, regressions detected between crawls with the deploy that caused them inferrable, and remediation guidance specific enough for a developer ticket.

Report an error

The In-House SEO Lead

The onpage crawler runs at stated per-domain limits of 50,000 to 500,000 subpages with JavaScript rendering, a prioritised advisor generating to-dos, and per-issue export of the affected URLs — that export is what turns a finding into a developer ticket on my side. I found no public information on scheduled crawl runs, Core Web Vitals per template, log-file or Search Console comparison for indexation and canonical diagnosis, structured-data validation, or regression detection between crawls, so this stays a well-prioritised list rather than a diagnosis. 2 5 9

Report an error

Keyword research & content guidance

How this is scored

Keyword discovery, intent classification, SERP feature analysis and on-page guidance — judged on the depth of the German-language data as much as the English.

0 — A keyword list with volumes from one source and no intent or difficulty signal.

3 — Volume and difficulty for major markets, with thin or stale German data and no SERP feature detail.

5 — Keyword research with volume, difficulty and intent across German and other EU markets, SERP feature presence, and basic on-page recommendations.

8 — Topic clustering, competitor gap analysis, SERP composition tracked over time, content briefs with entity coverage, and cannibalisation detection.

10 — Research and guidance close the loop: opportunity sized against realistic traffic, content scored against what currently ranks rather than against a keyword density heuristic, and recommendations that reference the specific pages in the customer's own site.

Report an error

The In-House SEO Lead

The German-language data is native rather than an afterthought: weekly crawl data for Germany, Austria, Switzerland, France, Italy and Spain, with search volume, CPC and competitor density, competitor keywords, user questions, filters for keywords just below page one and long-tail terms, and a SERP analysis comparing my content against the current top ten. I found no public information on intent classification, SERP composition tracked over time, entity-based content briefs or cannibalisation detection, and the text optimisation recommends term frequencies rather than scoring a page against what actually ranks. 2 5 6 7

Report an error

Rank tracking & index quality

How this is scored

The proprietary data: ranking accuracy and frequency, backlink index size and freshness. Scored on what the vendor documents about their own data, because nothing here can be verified from outside.

0 — Rankings and backlinks with no stated update frequency, no country or device granularity, and no documentation of how either is collected.

3 — Weekly rankings for one country and device, a backlink index with no stated refresh cadence or size.

5 — Daily rankings with country, language and device selection, local results, and a backlink index with a documented crawl frequency.

8 — Rankings at stated frequency across many locations including city-level, SERP feature attribution, backlink index size and refresh published, lost-and-found link detection, and historical data retained for the life of the account.

10 — The vendor is accountable for their own data: methodology documented, index size and freshness published and updated, historical rankings retained and exportable in full, and discrepancies against Search Console explained rather than hidden.

Report an error

The In-House SEO Lead

Daily or weekly rank queries are documented across 197 countries with organic, local, mobile and universal results, alongside a stated weekly crawl cadence for the eight index countries and the OVI visibility index — that is defensible monitoring. But the vendor documents little about its own index: I found no public information on backlink index size and refresh, lost-and-found link detection, how long historical rankings are retained, or how discrepancies against Search Console are explained, which is exactly what I need when the numbers disagree. 5 6 9 11

Report an error

Reporting, integrations & API

How this is scored

Getting the data out and in front of someone: dashboards, white-label reporting for agencies, Search Console and analytics integration, and an API a team can build on.

0 — On-screen views only; export is a manual CSV and there is no API.

3 — Scheduled PDF reports and CSV export, one analytics integration, no API worth building against.

5 — Customisable dashboards, scheduled reports, Search Console and analytics integration, and a documented API with stated limits.

8 — White-label reporting with client access, data-warehouse or BigQuery export, multi-site and multi-client management, and an API with credit costs published per endpoint.

10 — The tool is a data source rather than a destination: full historical export in open formats, a versioned API with a deprecation policy, integrations the vendor maintains, and reporting an agency can hand a client unedited.

Report an error

The In-House SEO Lead

White-label reports with customer branding and unlimited count, automated weekly or monthly PDF delivery, and Search Console, Google Analytics and Matomo wired directly into the reporting are all documented, and the API is real with JSON or XML output, pagination and a credit system. I found no public information on data-warehouse or BigQuery export or on credit costs per endpoint, so the true price of building on the API stays unknowable. 9 10 11

Report an error

Data portability & exit

How this is scored

Whether the ranking and crawl history — the only thing a multi-year subscription actually accumulates — remains the customer's when they leave.

0 — No bulk export; history is visible in the interface and nowhere else, and ends with the subscription.

3 — CSV export of current views only, with historical data capped or unavailable in bulk.

5 — Bulk export of rankings, keywords and crawl results including history, via interface or API.

8 — Complete historical export in open formats without credit metering that prices it out of reach, plus a documented retention period after cancellation.

10 — Exit is designed for: the full account exportable including every historical data point, API access sufficient to mirror the data continuously, and a stated grace period during which the archive remains retrievable.

Report an error

The In-House SEO Lead

What is evidenced is narrow: export of the affected URL list per audit message, and an API that paginates keyword data and returns generated reports as PDF, JSON or XML. I found no public information on bulk export of ranking or crawl history, retention after cancellation, or any grace period — and because API calls are credit-metered, the multi-year history a subscription actually accumulates has no evidenced way out. 5 10 11

Report an error

European sovereignty

How this is scored

Where the account and crawl data live and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted lower here than in categories holding personal data, because an SEO tool mostly holds the customer's own strategy rather than their customers' identities.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and site or user data of unclear scope leaving the EU.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published, and any analytics or Search Console data handling described with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a DPA that covers the crawl and analytics data the tool ingests.

Report an error

The In-House SEO Lead

The operating entity is German — WebPros Germany GmbH in Cologne with a Köln register entry — and non-EU group transfers to the US, Switzerland, Japan, the UK, New Zealand, Canada and India are documented with standard contractual clauses, adequacy decisions and Data Privacy Framework certification, plus a published group subprocessor list. I found no public information on where the account and crawl data is hosted, so EU storage as standard cannot be confirmed, and central handling of data-subject rights sits with the Swiss group entity. 3 4

Report an error

Pricing transparency

How this is scored

The category where the headline price is least often the invoice. Whether a buyer can compute the real annual cost including keyword limits, crawl credits, API units, extra users and client seats — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A monthly headline exists, but keyword limits, crawl credits or the cost of an additional user are unstated — the invoice is unknowable.

5 — Tier prices public with the main limits given, but at least one commonly needed piece (extra seats, API credits, historical data) is unpriced or metered opaquely.

8 — Every tier priced publicly with keyword, crawl and API limits, overage rates, per-seat costs, minimum term and VAT treatment stated.

10 — Complete price computability: annual invoice derivable for a given keyword count, crawl volume, API usage and team size, with overage and every credit cost published.

Report an error

The In-House SEO Lead

All three tiers are public — XOVI Pro at 99€/Monat, Business at 149,00 €/Monat, Enterprise at 499 €/Monat — with per-tier crawl limits of 50,000 to 500,000 subpages, priced crawl add-ons up to 500,000 Unterseiten at 299,90€ mtl.*, parallel-processing and AI add-ons, and VAT stated on top at 19 percent. The gaps keep the annual invoice from being computable: I found no public information on the keyword quota per tier, the price of an additional user account, or what an API credit costs. 2 5 6

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Incorporated in DE ⚠ unverified	3/3 pts	3 Report an error
Ownership	Not determined ⚠ unverified	—	uncited Report an error
Data residency	Not determined	—	uncited Report an error
Subprocessors	Not determined ⚠ unverified	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 2 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Ownership, Subprocessors. Not confirmed on the vendor’s own pages as captured.
Weak sourcing — Legal entity. The imprint names no country word, so DE is derived from the German commercial register entry (Registergericht Köln, HRB) and the Köln address; the operating legal entity is WebPros Germany GmbH, not XOVI GmbH itself.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

15 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
10 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
8 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us

Do you know more about XOVI? Tell us Report an error on this page

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage www.xovi.de Checked 16 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
2 Pricing www.xovi.de Checked 16 Sep 2026 Details →
3 Imprint www.xovi.de Checked 16 Sep 2026 Details →
4 Privacy policy www.xovi.de Checked 16 Sep 2026 +1 earlier capture: 2 Sep 2026 Details →
5 Crawling & technical audit — found from sitemap www.xovi.de Checked 1 Oct 2026 Details →
6 Keyword research & content guidance — found from sitemap www.xovi.de Checked 1 Oct 2026 Details →
7 Keyword research & content guidance — found from sitemap www.xovi.de Checked 1 Oct 2026 Details →
8 Rank tracking & index quality — found from sitemap www.xovi.de Checked 1 Oct 2026 Details →
9 Reporting, integrations & API — found from sitemap www.xovi.de Checked 1 Oct 2026 Details →
10 Data portability & exit — found from sitemap developers.xovi.net Checked 1 Oct 2026 Details →
11 Data portability & exit — found from sitemap developers.xovi.net Checked 1 Oct 2026 Details →