Search-overlap competitors
dataforseo · runnable · billing paged
| Fact | Value |
|---|---|
| Provider | dataforseo |
| Module | base |
| Runnable today | Yes — a quantity-bound adapter exists |
| API path | /v3/dataforseo_labs/google/competitors_domain/live |
| Billing kind | paged |
| Price status | Known — a published or measured rate is recorded |
| Availability | Executable in selected plans; target and quantity bounds required |
| Query contract | Enforced — the collector reads these parameters from the contract |
| Catalogue research date | 2026-09-07 |
Billing formula
What the provider charges for one request of this item. Provider cost is not the customer price and is not an account balance movement; the three are different numbers and this is the first of them.
sum_request((0.012 + 0.00012*returned_items_request)*clickstream_multiplier_request)
Rates
| Component | Value |
|---|---|
task_usd | 0.012 |
returned_item_usd | 0.00012 |
clickstream_multiplier_off | 1 |
clickstream_multiplier_on | 2 |
Minimum charge: {"active_task_base_usd":"0.012"}
Provider limits: {"items_per_request":1000}
Rate verification: verified_published.
Caveat: Each offset/cursor request repeats the task fee; group by endpoint, target, location and language. include_clickstream_data=true doubles the applicable request cost.
Runtime limits
| Limit | Value |
|---|---|
quantity | 1000 |
groups | 1 |
Frozen acquisition parameters
Search overlap is a discovery read over domains that share results with the target. The target itself is always excluded, and overlap is counted only where a rival actually ranks, using the same fixed ceiling as the other rival-facing calls.
| Parameter | Value |
|---|---|
| Fixed parameters | {"item_types":["organic"],"include_clickstream_data":false,"ignore_synonyms":false,"exclude_top_domains":true,"max_rank_group":20} |
| Server-side filters | None |
| Order by | None |
| Page window | 1000 |
| Varies by target | target, exclude_domains |
Changed in contract v1 (ACQ-3): exclude_top_domains removes the provider's published wikipedia/reddit/amazon-class list. It would NOT have removed this product's observed offenders (sec.gov, glassdoor, pitchbook are not on that list), so that part is a cheap improvement, not a fix for the noise actually seen. max_rank_group is this endpoint's OWN documented lever for the same question the other two rival-facing calls answer with a filter, and leaving it at the default 100 counted overlap on results nobody sees.
Evidence: VERIFIED 2026-09-14 by direct fetch of https://docs.dataforseo.com/v3/dataforseo_labs/google/competitors_domain/live/, not only by the Phase 2 worker's report. The page documents max_rank_group as 'maximum rank up to which competitors will be considered ... default value: 100', so leaving it unset counted overlap across the whole top 100. Quoted with the document hash in docs/plans/brand-studio-roadmap/query-contract-doc-verification-20260914.json.
Included in levels: Snapshot, Market, Deep.
Dated sources
https://dataforseo.com/pricing/dataforseo-labs/dataforseo-google-api(read 2026-09-07)https://docs.dataforseo.com/v3/dataforseo_labs/google/ranked_keywords/live/(read 2026-09-07)
Notes from the catalogue
- Each offset/cursor request repeats the task fee; group by endpoint, target, location and language. include_clickstream_data=true doubles the applicable request cost.