whats-best.ai
Search Sign in

SEO

Serpstat

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Serpstat Inc. · serpstat.com

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 Technical SEO

Weighted verdict

Lives in crawl data and log files. Wants JavaScript rendering, crawl budget analysed, indexation diagnosed rather than listed, and regressions caught between crawls. Treats an issue list sorted by count rather than by traffic impact as busywork.

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

Scored by The Technical SEO

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 Technical SEO

Site Audit exists as a proper module with an audit summary, an all-issues view and a per-page audit, and Core Web Vitals are named in the positioning. But we found no public information on crawl page limits, JavaScript rendering, crawl scheduling, or any Search Console and log-file comparison against what Google actually fetched — issues are presented as sections of a list, with no evidence of prioritisation by traffic impact. 1 3 6

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 Technical SEO

Clustering is genuinely deep — soft and hard linkage, a per-keyword connection strength score, cluster homogeneity, metatop competitor pages, automatic assignment of clusters to the most relevant page of your own site, and text analysis with recommendations for that assigned page. We found no public information on intent classification, SERP feature data in research, cannibalisation detection, or the depth of the German-language data, which keeps this below the top band. 1 5 6

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 Technical SEO

Daily tracking with search engine, country, optional region and city selection plus device types and URL-level positions is granular, and index sizes are stated plainly — 529 billion backlinks, 1.5 billion domains, 2.21 billion Google SERPs. But the vendor publishes the size of their data and not its freshness: we found no public information on backlink refresh cadence, SERP feature attribution, lost-and-found link detection, methodology, or how long Positions History is retained. 1 5 7

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 Technical SEO

The API is real and priced: a documented JSON-RPC reference with one credit per returned row, five credits per summary call, 60,000 rows per request, and monthly call quotas published per plan — individual has no API access, team 200,000 and agency 2,000,000. White label climbs from a logo in PDFs on the individual plan to a full custom-domain platform clients log into on the agency plan, with maintained Google Sheets, Looker Studio, R, Python and MCP integrations. We found no public information on Search Console or analytics integration, warehouse or BigQuery export, or an API deprecation policy. 6 8 9 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 Technical SEO

Rankings, backlinks, domain metrics and site audit results are all reachable through the API, there is a positions CSV export endpoint, XLSX and CSV export in the interface, and a dedicated export route for volumes above the 60,000-row request cap. But pulling bulk history through the API is metered at a credit per row, and we found no public information on how long historical data remains retrievable after cancellation. 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 Technical SEO

We found no public information on where accounts and crawl data are hosted, the jurisdiction of the contracting entity, or the subprocessor list — the only named third party anywhere is Intercom running the knowledge base. With hosting unstated and the data chain unevidenced, there is effectively nothing here to assess. 1 3 6

Report an error

Pricing transparency not rated — the vendor publishes no price

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 Technical SEO

Credit mechanics are documented down to the credit — five credits per clustered keyword, a shared pool across text and batch analysis, free of charge for changing strength or cluster type — and API quotas and credit costs are published per plan. But we found no public information on any plan price in currency, additional seat costs, crawl limits, minimum term or VAT treatment, so a buyer cannot compute the annual invoice from these pages. 1 5 11

Report an error

Where this could be wrong

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.

Sources (11)

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

  1. 1 Vendor page serpstat.com Checked 22 Sep 2026 Details →
  2. 2 Crawling & technical audit — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
  3. 3 Crawling & technical audit — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →
  4. 4 Keyword research & content guidance — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
  5. 5 Keyword research & content guidance — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
  6. 6 Rank tracking & index quality — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
  7. 7 Rank tracking & index quality — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →
  8. 8 Reporting, integrations & API — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
  9. 9 Reporting, integrations & API — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →
  10. 10 Data portability & exit — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
  11. 11 Data portability & exit — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →