about
About this site
Who runs SEO Data Bench, who pays for it, and how the relationship to Treg is handled on every page.
SEO Data Bench measures what SEO data APIs actually return on a fixed workload: keyword volumes, Google result pages and backlink counts for a declared cohort of queries and domains, sent through every route we can reach on the same day. It is written for people who buy SEO data by the call, for an agent or an internal tool, and want to know how the providers differ before they pick one.
Who writes here
Benchmarks are run and written by Shirley Lou, who runs research at Treg. There are no pseudonymous authors on this site.
Relationship to Treg {#relationship}
This site is published by the team behind Treg, a pay-per-call API that routes data requests across providers. Treg’s routed SEO endpoints appear in these benchmarks as one route among the direct providers, and we earn money when readers use Treg.
We handle that in three ways:
- Every page that includes a Treg route carries a disclosure block directly under the answer, not only in this footer.
- Every number on the site is a call we made, with the raw response downloadable from the evidence page. Treg routes are measured with the same cohort, on the same day, as the direct providers.
- When a Treg route is served by a provider that is also measured directly, the page says so. Two routes to the same provider’s data are not two independent datasets.
None of that makes this an independent benchmark site, and we do not claim it is. It makes the numbers checkable.
What is not on this site
- No “best SEO API” rankings. Each benchmark reports one measurable property and says what it cannot show.
- No accuracy claims about search volume. No provider’s volume is ground truth; Google’s own Keyword Planner is used as the comparison point because it is the number advertisers buy against, not because it is correct.
- No affiliate links.
Corrections
If a number or method on this site is wrong, email corrections@seodatabench.com with the page and a source. Changes are logged on the corrections page.