SEO
Serpstat
Provenance unknown Report an error0–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 panel's verdict
Serpstat Inc.'s SEO platform is best evidenced for keyword work and API access, thinnest in technical audit and sovereignty. Keyword and content scored 6-7: clustering is documented in real depth — soft and hard modes, connection strength and homogeneity scores from 0-100, a metatop of competitor pages, automatic assignment of your own page, and Text Analysis recommendations. Reporting and API produced the widest spread, 6-8: higher scores credit a documented JSON-RPC 2.0 API with published metering — one credit per row, five per summary call, 200,000 monthly calls on Team, 2,000,000 on Agency — while lower scores weigh the absence of public information on Search Console, analytics or warehouse export. Rank and index data sat at 6 with no variation, pairing daily location, language and device tracking with plainly published index sizes (529B backlinks, 1.50B domains, 2.21B Google SERPs) but no public information on refresh cadence or methodology. Technical audit scored 3-4 as an issue list; data portability 4-5, exports real but credit-metered; sovereignty 1-2; pricing transparency 1-2, with no currency price for any tier. Persona-weighted verdicts ranged 5.0-5.8.
Speaks for it
- Keyword clustering documented in depth — soft and hard modes, connection strength and homogeneity scores from 0-100, a metatop of competitor pages, automatic assignment of your most relevant page, and Text Analysis recommendations — scored 6-7.
- A documented JSON-RPC 2.0 API with published costs: one credit per returned row, five credits per summary call, and monthly caps of 200,000 calls on Team and 2,000,000 on Agency.
- Daily rank tracking with search engine, country, optional region and city, language and device selection, plus Positions History, SERP History and URL-level tracking.
- Index sizes published plainly — 529B backlinks, 1.50B domains, 5.6B keyword suggestions, 2.21B Google SERPs.
- White label scales from a logo in PDF reports on the Individual plan to a CNAME-backed custom domain clients log into on the Agency plan.
Held against it
- Technical audit scored 3-4 — issues presented as lists, and we found no public information on crawl limits, scheduling, JavaScript rendering or severity prioritisation.
- Sovereignty scored 1-2: no sovereignty attributes are on record, and the only named third party in the captured pages is Intercom, which runs the knowledge base.
- We found no public information on backlink refresh cadence, ranking methodology or how long historical data is retained behind the published index sizes.
- Bulk export costs one credit per API row under monthly request caps, and we found no public information on retention after cancellation.
- No price in currency appears in the captured pages, so an annual invoice cannot be computed from public information.
Best for
- You brief content from keyword research and want clusters tied to what ranks — connection strength and homogeneity scores, a metatop of ranking competitor pages, automatic page assignment, and Text Analysis recommendations against the assigned page.
- Your team builds its own data pipelines — a documented JSON-RPC 2.0 API with per-call credit costs, a dedicated positions export endpoint, and maintained Google Sheets, Looker Studio, Python, R and MCP routes.
- You run an agency needing branded client reporting — white label from a logo in PDFs on the Individual plan to a full custom domain with client login on the Agency plan.
- You track rankings daily across countries, regions, cities, languages and devices and want URL-level positions with positions and SERP history modules.
Avoid if
- You need crawl findings you can hand to developers — technical audit scored 3-4 and we found no public information on crawl limits, scheduling, JavaScript rendering or severity prioritisation.
- Your procurement must pre-clear hosting location, subprocessors or a data processing agreement — ask the vendor: the public pages we read do not show it
- You need API access from the entry-level plan — the Individual plan carries no API access.
- You expect an unmetered historical archive — export costs one credit per row under monthly request caps, and we found no public information on retention after cancellation.
The scores
Crawling & technical audit
Show reasoningHide reasoning
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.
The In-House SEO Lead
The captured pages show a site audit with a summary, an all-issues view, a custom overview and a per-page audit, and Core Web Vitals are named as a focus alongside crawling performance. We found no public information on crawl limits, scheduling, JavaScript rendering, issue prioritisation or any comparison of what the crawler sees against what Google fetched, so I cannot tell whether findings would translate into a developer ticket. 3 6 1
The Agency Owner
A site audit exists with an audit summary, an issue list, a custom overview and page-level audit, and Core Web Vitals are named as an outcome, but I found no public information on crawl page limits, scheduling, JavaScript rendering or how issues are prioritised. For forty client sites I cannot even tell from these pages how deep the crawler goes or whether anything is scheduled. 1 3 6
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
The Content Strategist
A site audit exists with an Audit Summary, an All-issues view, custom overview and a page-level audit, and Core Web Vitals is named in its stated purpose — but that is where the evidence stops. We found no public information on crawl page limits, scheduled crawls, JavaScript rendering, severity prioritisation, or anything comparing what the crawler sees against what Google fetched. 1 3 6
The Data Analyst
A crawler exists — Audit Summary, an issue list, and per-page audit, with Core Web Vitals named as a target — but we found no public information on crawl scheduling, page limits, JavaScript rendering, or issue prioritisation by severity or traffic impact. That reads as issue listing rather than diagnosis. 3 6 1
The Skeptic
A site audit is confirmed with an Audit Summary, an All issues list, a custom overview and per-page audit, and core web vitals named among the targets. We found no public information on the crawl page limit, scheduling, JavaScript rendering, severity prioritisation or traffic-impact ranking, so the evidence shows an issue list rather than a diagnosis. 3 6
Keyword research & content guidance
Show reasoningHide reasoning
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.
The In-House SEO Lead
Clustering is genuinely deep — soft and hard cluster modes with configurable connection strength from weak to strong, homogeneity scoring, a Metatop of the competitor pages appearing in the SERP, automatic assignment of my own pages to clusters, and per-page content recommendations through Text Analysis. We found no public information on intent classification, SERP feature detail, cannibalisation detection, or how deep the German-language database goes, which is what my monthly content planning would hang on. 5 1 6
The Agency Owner
Clustering is genuinely deep — soft and hard modes, a connection-strength score, a metatop of competitor pages in the SERP, and text analysis run against the customer's own auto-assigned page. I found no public information on German-language data depth, intent classification or cannibalisation detection, which holds it below the top band. 1 5 6
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
The Content Strategist
Clustering is the strongest-documented capability in the whole sheet: soft and hard modes with URL-strength thresholds, Connection Strength and Homogeneity scores, a Metatop of the competitor pages that actually rank for the cluster, auto-assignment of the customer's own most relevant page, and Text Analysis recommendations launched against that assigned page — briefs tied to what ranks, which is what I commission against. Held below the top because we found no public information on cannibalisation detection, SERP feature composition, entity coverage in briefs, or the depth of German-language data. 1 5 6
The Data Analyst
Clustering is documented in real depth — soft and hard modes with stated URL thresholds, connection strength and homogeneity scores, a metatop of competitor pages, automatic page assignment, and Text Analysis recommendations for the assigned page — alongside competitor keyword opportunities and a SERP History module. We found no public information on intent classification, cannibalisation detection, or the depth of the German-language data, which is what the top band asks for. 5 1 7 6
The Skeptic
Keyword clustering is documented in genuine depth — soft and hard modes with stated URL thresholds, connection strength and homogeneity scores, metatop competitor pages, automatic page assignment, and content recommendations through the text analysis link — with difficulty, volume, trends and batch tooling alongside. We found no public information on intent classification, SERP feature composition, or the depth of the German-language data, which holds it short of the top band. 1 5 6
Rank tracking & index quality
Show reasoningHide reasoning
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.
The In-House SEO Lead
Daily rank tracking with country, language and device selection plus region and city granularity, positions history and SERP history modules, and index sizes are published plainly — 529 billion backlinks, 1.5 billion domains, 2.21 billion Google SERPs, 5.6 billion keyword suggestions. We found no public information on how the data is collected, the index refresh cadence, or how discrepancies against Search Console are explained, which is exactly what I need before I can defend these numbers to my stakeholders. 1 6 7 5
The Agency Owner
Daily tracking with location, language and device selection, URL-level positions and separate positions and SERP history modules are documented, and index sizes are published (529B backlinks, 1.50B domains, 2.21B Google SERPs). I found no public information on the backlink index refresh cadence, SERP feature attribution or data methodology, so the vendor's own accountability for its data is not evidenced. 1 6 7
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
The Content Strategist
Daily rank monitoring with country, language and device selection is documented alongside Positions History, SERP History and URL-level tracking, and the index sizes are published — 529B backlinks, 1.5B domains, 2.21B Google SERPs — which is more self-disclosure than most vendors manage. But we found no public information on backlink refresh cadence, crawl methodology, SERP feature attribution, lost-and-found link detection, or how long historical data is retained. 1 6 7
The Data Analyst
Daily rank tracking with country, region and city selection plus language and device granularity is documented, and index size is published — 529B backlinks, 1.50B domains, 5.6B keyword suggestions. What I cannot verify is freshness and accountability: we found no public information on backlink refresh cadence, data collection methodology, lost-and-found link detection, or how long historical rankings are retained. 1 6 7 5
The Skeptic
Daily rank tracking with country, language, device and region-or-city selection is documented, with positions history, SERP history and URL-level tracking, and index sizes are published (529 billion backlinks, 1.5 billion domains, 2.21 billion Google SERPs). We found no public information on the backlink refresh cadence, the ranking methodology, or how long history is retained, so freshness and durability rest on large numbers no buyer can check. 1 6 7
Reporting, integrations & API
Show reasoningHide reasoning
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.
The In-House SEO Lead
There is a documented API with published monthly request caps per plan, per-row credit costs and a 60,000-row limit, plus Google Sheets, Looker Studio, R and MCP integrations, and white-label reporting that reaches a branded client domain on the Agency plan. We found no public information on Search Console or analytics integration, data-warehouse or BigQuery export, or scheduled reports — the pieces my monthly reporting actually runs on. 11 8 9 6
The Agency Owner
This is the part I care about most and it holds up: branded PDF and Custom Reports from the Individual plan, a full white-label interface on my own subdomain with client access on the Agency plan, and a documented API whose credit costs are published per row and per call. I found no public information on Search Console or analytics integration, data-warehouse export, or multi-client management, which keeps it short of the top band. 8 9 11
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
The Content Strategist
White label scales sensibly from a logo in PDF reports on the lowest plan up to a CNAME-backed custom domain clients log into on the Agency plan, and the API publishes its metering — one credit per row, five credits per summary call, 60,000 rows per request, 200,000 monthly calls on Team and 2,000,000 on Agency — with vendor-maintained Google Sheets, Looker Studio, R and MCP integrations. Below the top anchors because we found no public information on data-warehouse export or an API versioning and deprecation policy. 6 8 9 11
The Data Analyst
This is the strong suit: a documented API over JSON-RPC 2.0 with per-plan request limits (200,000/month on Team, 2,000,000/month on Agency, none on Individual) and credit costs published per call — one credit per returned row, five for the Summary report — plus Google Sheets, Looker Studio, Python and R routes and white-label client access on the Agency plan's custom domain. We found no public information on Search Console or analytics integration, scheduled reports, or data-warehouse export, which is the difference between a data source and a well-documented destination. 11 8 9 6
The Skeptic
The credit costs are on the page, which is rare: one credit per returned API row, five credits for the summary call, a 60,000-row cap per request, and monthly API request caps stated per plan, with white label tiered clearly from logo-in-PDFs on Individual to a full custom domain on Agency. We found no public information on API versioning or a deprecation policy, and there is no sandbox — one token per account — but a team can build against this knowing what each call costs. 8 9 11
Data portability & exit
Show reasoningHide reasoning
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.
The In-House SEO Lead
A dedicated API endpoint exports domain positions as CSV, larger volumes have a stated data-export route beyond the 60,000-row request cap, and XLSX/CSV export exists, so bulk access to rankings and audit results looks real. We found no public information on exporting full ranking history, any retention period after cancellation, or how credit metering prices a large historical pull. 10 11 5
The Agency Owner
Exports exist — XLSX and CSV, a positions export endpoint, and API data export for volumes beyond the 60,000-row request cap — but exports run through plan-limited API calls and per-row credits. I found no public information on retention after cancellation or any grace period during which the ranking and crawl history remains retrievable. 5 10 11
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
The Content Strategist
Bulk export exists in XLSX and CSV, there is a dedicated API method for exporting a domain's positions for its keywords, and a data-export path is offered for volumes above the 60,000-row request cap — that clears the bulk-export bar for rankings and keywords. But export is credit-metered, API access begins only at the Team plan, and we found no public information on bulk export of crawl history or on any retention period after cancellation. 5 10 11
The Data Analyst
Export paths exist — an API method for exporting domain positions, results capped at 60,000 rows per request with data export for larger volumes, and clustering output in XLSX or CSV — but every API row costs a credit, so pulling years of history out is metered. We found no public information on retention after cancellation or any grace period, so whether the archive leaves with the customer or ends with the subscription is not evidenced. 11 10 5
The Skeptic
Export is real rather than decorative: XLSX and CSV from the interface, an API method to export a domain's positions as CSV, a data-export path for volumes above 60,000 rows, and API access that covers site audit results. We found no public information on a retention period after cancellation or whether historical export is metered by credits, and the monthly API request caps mean a multi-year archive takes deliberate planning to pull. 5 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
The In-House SEO Lead
We found no public information on where account and crawl data are hosted, the contracting entity's jurisdiction, subprocessors, certifications, or a data processing agreement — neither on the vendor's own pages nor in the API documentation. For a tool that mostly holds our site strategy rather than customer identities I can live with asking, but nothing here can be pre-cleared for procurement. 1 11
The Agency Owner
No sovereignty attributes are on record: I found no public information on where accounts and crawl data are hosted, the contracting entity's jurisdiction, subprocessors, or a data-processing agreement covering what the tool ingests. With nothing published on any of it, I cannot score this above the floor for the criterion. 1 11
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
The Content Strategist
No sovereignty attributes are on record for this vendor. We found no public information on hosting location, the contracting entity's domicile, or any subprocessor list; hosting unstated and subprocessors unnamed sits at the bottom of the anchors, and nothing in the captured pages lifts it. 1
The Data Analyst
No sovereignty attributes are on record: we found no public information on hosting location, the contracting entity's jurisdiction, a subprocessor list, or a data processing agreement, and the knowledge base is stated to run on Intercom. A tool holding the customer's own strategy rather than their customers' identities makes this less critical than elsewhere, but nothing here is evidenced. 1 3
The Skeptic
We found no public information on where account and crawl data are hosted, where the contracting entity sits, which subprocessors touch customer data, or any data processing agreement; the only named third party in the captured pages is Intercom, which runs the knowledge base. Nothing on record evidences an EU safeguard, and the weight here is limited because an SEO tool mostly holds the customer's own strategy rather than their customers' identities. 3
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
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.
The In-House SEO Lead
Credit mechanics are documented — 5 credits per clustered keyword, one credit per returned API row, 5 credits for the summary report, monthly request caps by plan, and which features unlock at which tier — but we found no public price figures for any tier, per-seat costs or overage rates. Without a stated plan price, the annual invoice cannot be computed from the captured pages. 5 11 1
The Agency Owner
I can read how many credits a clustering keyword consumes (5 credits per keyword), that credits are shared with Text Analysis and the batch tools, and how many API calls the Team and Agency plans allow — but I found no public information on plan prices, per-seat costs, VAT treatment, minimum term or overage rates. The annual invoice for a growing team is unknowable from public pages, and that is a margin problem before I ever sign. 1 5 11
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
The Content Strategist
Plan mechanics are public and genuinely useful — clustering charges each keyword at 5 credits with free setting-only changes, API access is available from the Team plan with Individual excluded, white label starts on the Individual plan, and a 7-day trial is stated. But we found no public information on any currency price for any tier, additional seat costs, or VAT treatment, so a real annual invoice cannot be computed from the captured pages. 1 5 11
The Data Analyst
Unit mechanics are public — clustering is quoted as "Each keyword costs 5 credits", an API row costs one credit, the Summary report five, and monthly API volumes per plan are stated — but we found no public information on any tier's price, keyword or crawl limits, extra seats, overage rates, minimum term, or VAT treatment. Without a single currency figure in the captured pages, the annual invoice is not computable from public information. 5 11 1 8
The Skeptic
No price in currency appears in the captured pages — no tier cost, no seat cost, no VAT treatment — so an annual invoice cannot be computed from public information alone. The credit mechanics are documented well (each keyword costs 5 credits, each API row costs one credit, monthly API request caps stated per plan), but credits are not money, and we found no public information on what a credit costs or the rank-tracking and crawl limits each plan carries. 5 11
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- We found no public information on compliance on the pages we read (serpstat.com, serpstat.com/tutorial/site-audit, help.serpstat.com/en/collections/19180093-site-audit, serpstat.com/keyword-research, serpstat.com/tutorial/keyword-clustering, serpstat.com/tutorial/rank-tracker and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 2 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
- 2 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
- 1 integrations 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
- 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
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page serpstat.com Checked 22 Sep 2026 Details →
- 2 Crawling & technical audit — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
- 3 Crawling & technical audit — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →
- 4 Keyword research & content guidance — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
- 5 Keyword research & content guidance — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
- 6 Rank tracking & index quality — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
- 7 Rank tracking & index quality — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →
- 8 Reporting, integrations & API — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
- 9 Reporting, integrations & API — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →
- 10 Data portability & exit — found from sitemap serpstat.com Checked 1 Oct 2026 Details →
- 11 Data portability & exit — found from sitemap help.serpstat.com Checked 1 Oct 2026 Details →