Labs Competitor Research (Capability)

The DataForSEO Labs competitor endpoints map who ranks for what: SERP competitors, ranked keywords, domain and page intersections, rank overviews, traffic estimates, and the Amazon / Google Play / App Store equivalents, all from a pre-indexed database. Sits under DataForSEO Brain Concepts.

Overview

Where the keyword-research family expands a seed, the competitor family analyzes domains, pages, ASINs, and apps. It answers “who else ranks for my keywords”, “what does this domain rank for”, “which keywords do two domains share”, and “how much traffic does this domain or app get”. Like all of Labs, the data is pre-indexed (not a live SERP scrape), updated periodically, with historical series available from October 2020 onward. All endpoints are Live POST calls under /v3/dataforseo_labs/{engine}/{function}/live.

What it covers

  • /v3/dataforseo_labs/google/serp_competitors/live - domains ranking for a set of keywords (up to 200) with their SERP positions and visibility.
  • /v3/dataforseo_labs/google/competitors_domain/live - competitor domains that share SERPs with a target, with organic and paid metrics.
  • /v3/dataforseo_labs/google/ranked_keywords/live - every keyword a domain or page ranks for, with its SERP element and volume.
  • /v3/dataforseo_labs/google/domain_intersection/live and /v3/dataforseo_labs/google/page_intersection/live - keywords two or more targets both rank for (link/keyword gap analysis).
  • /v3/dataforseo_labs/google/relevant_pages/live - a domain’s pages with ranking distribution and estimated traffic.
  • /v3/dataforseo_labs/google/domain_rank_overview/live and /v3/dataforseo_labs/google/subdomains/live - ranking distribution and traffic for a domain or its subdomains.
  • /v3/dataforseo_labs/google/historical_rank_overview/live and /v3/dataforseo_labs/google/historical_serps/live - weekly historical ranking distribution and SERP snapshots.
  • /v3/dataforseo_labs/google/bulk_traffic_estimation/live and /v3/dataforseo_labs/google/historical_bulk_traffic_estimation/live - estimated monthly traffic for up to 1000 domains/pages.
  • Amazon: product_competitors, ranked_keywords, product_keyword_intersections, product_rank_overview. Apps: apple/app_competitors, apple/app_intersection, apple/bulk_app_metrics, and the google/app_* equivalents (up to 1000 apps in bulk).

Key parameters / inputs

fieldnotes
target / targetssingle domain or array of domains/pages; bulk_traffic_estimation takes up to 1000 targets
keywords / keywordcompetitor discovery seeds (serp_competitors max 200)
asin / asins, app_id / app_idsAmazon ASINs and app ids; intersection endpoints cap at 20, bulk at 1000
location_code / language_coderequired location and language identifiers
intersectionstoggles keyword-intersection filtering
include_clickstream_datadoubles cost; default false
filters / order_by / limitmax 8 filters, max 3 sort rules, limit up to 1000

Response / what you get back

Domain metrics arrive under metrics.organic.* and metrics.paid.*, including metrics.organic.count, metrics.organic.etv (estimated traffic volume), and the position brackets metrics.organic.pos_1 through pos_91_100. full_domain_metrics covers all of a domain’s keywords. Per-keyword ranking detail comes through ranked_serp_element and avg_position. Intersection endpoints return intersections (count of shared keywords) and intersection_result (per-target SERP data), each keyword carrying keyword_data.keyword_info and search_volume.

Cost & method notes

  • All endpoints are Live; per-request billing. The cost log shows serp_competitors, competitors_domain, ranked_keywords, domain_intersection, relevant_pages, subdomains, and keywords_for_site at 0.0101; the competitor historical endpoints (historical_rank_overview, historical_serps, historical_bulk_traffic_estimation) bill at the same per-request Labs tier.
  • etv is computed as the product of click-through rate and search volume; clickstream_etv is the clickstream-based alternative.
  • include_clickstream_data: true doubles the cost. See cap-queue-priority-cost-model and dec-labs-vs-live-apis.

When to use / how it fits

This is the spine of play-competitor-gap-analysis (domain intersection + ranked keywords + backlinks intersection + technologies) and supports play-content-strategy-brief and play-ecommerce-product-research. Pair domain intersection here with cap-backlinks-api intersection for a full gap picture, and route jobs via dec-which-api-for-which-job.

Gotchas / limits

  • 2000 API calls/min, max 30 simultaneous requests.
  • Historical rank/traffic series start October 1, 2020; clickstream data from May 2024; historical_serps covers a 12-month window with keyword up to 700 chars.
  • Amazon endpoints are limited to a handful of marketplaces; App Store and Google Play endpoints are US/English only.
  • Traffic and rank figures are estimates from a pre-indexed database, not measured analytics; treat them as directional, not exact.

Sources