DataForSEO — Dataforseo Labs / Google / Bulk Traffic Estimation / Live

Retrieve labs Google Bulk Traffic Estimation Live with the DataForSEO API. Review the selected endpoint’s request fields before calling. Use it for search visibility research or technical SEO.

Selected price
$0.012 base + $0.00012 / result Published pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* array
body[0]* object | null
targets* array
target domains, subdomains, and webpages required field you can specify domains, subdomains, and webpages in this field; domains and subdomains should be specified without https:// and www.; pages should be specified with absolute URL, including https:// and www.; you can set up to 1000 domains, subdomains or webpages
Optional parameters (7)
ignore highly similar keywords optional field if set to_ true, only core keywords will be returned, all highly similar keywords will be excluded; default value: false
item_types array | null
display results by item type optional field indicates the type of search results included in the response Note: if the item_types array contains item types that are different from organic, the results will be ordered by the first item type in the array possible values: ["organic", "paid", "featured_snippet", "local_pack"] default value: ["organic", "paid"]
language code if you use this field, you don’t need to specify language_name you can receive the list of available languages with their language_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available languages example: en
full name of the language if you use this field, you don’t need to specify language_code you can receive the list of available languages with their language_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available languages example: English
location code if you use this field, you don't have to specify location_name you can receive the list of available locations with their location_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available locations example: 2840
full name of the location if you use this field, you don't have to specify location_code you can receive the list of available locations with their location_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available locations example: United Kingdom
user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response
‌ This endpoint will provide you with estimated monthly traffic volumes for up to 1,000 domains, subdomains, or webpages. Along with organic search traffic estimations, you will also get separate values for paid search, featured snippet, and local pack results.

Sample response

{
  "cost": 0.0103,
  "status_code": 20000,
  "status_message": "Ok.",
  "tasks": [
    {
      "cost": 0.0103,
      "data": {
        "api": "dataforseo_labs",
        "function": "bulk_traffic_estimation",
        "item_types": [
          "organic",
          "paid"
        ],
        "language_code": "en",
        "location_code": 2840,
        "se_type": "google",
        "targets": [
          "dataforseo.com",
          "cnn.com",
          "forbes.com"
        ]
      },
      "id": "11261921-1535-0365-0000-33f1d9943d3e",
      "path": [
        "v3",
        "dataforseo_labs",
        "google",
        "bulk_traffic_estimation",
        "live"
      ],
      "result": [
        {
          "items": [
            {
              "metrics": {
                "featured_snippet": null,
                "local_pack": null,
                "organic": {
                  "count": 11786473,
                  "etv": 217332878.18734226
                },
                "paid": {
                  "count": 0,
                  "etv": 0
                }
              },
              "se_type": "google",
              "target": "cnn.com"
            },
            {
              "metrics": {
                "featured_snippet": null,
                "local_pack": null,
                "organic": {
                  "count": 16242380,
                  "etv": 187885962.6140026
                },
                "paid": {
                  "count": 499,
                  "etv": 7245.073922678828
                }
              },
              "se_type": "google",
              "target": "forbes.com"
            },
            {
              "metrics": {
                "featured_snippet": null,
                "local_pack": null,
                "organic": {
                  "count": 1708,
                  "etv": 3511.982047529891
                },
                "paid": {
                  "count": 6,
                  "etv": 6.360000163316727
                }
              },
              "se_type": "google",
              "target": "dataforseo.com"
            }
          ],
          "items_count": 3,
          "language_code": "en",
          "location_code": 2840,
          "se_type": "google",
          "total_count": 3
        }
      ],
      "result_count": 1,
      "status_code": 20000,
      "status_message": "Ok.",
      "time": "0.2426 sec."
    }
  ],
  "tasks_count": 1,
  "tasks_error": 0,
  "time": "0.2930 sec.",
  "version": "0.1.20210917"
}

Response result

Response structure

Inferred from examples
  • costnumber
  • status_codeinteger
  • status_messagestring
  • tasksobject[]
    • costnumber
    • dataobject
      • apistring
      • functionstring
      • item_typesstring[]
      • language_codestring
      • location_codeinteger
      • se_typestring
      • targetsstring[]
    • idstring
    • pathstring[]
    • resultobject[]
      • itemsobject[]
        • metricsobject
          • featured_snippetnull
          • local_packnull
          • organicobject
            • countinteger
            • etvnumber
          • paidobject
            • countinteger
            • etvnumber
        • se_typestring
        • targetstring
      • items_countinteger
      • language_codestring
      • location_codeinteger
      • se_typestring
      • total_countinteger
    • result_countinteger
    • status_codeinteger
    • status_messagestring
    • timestring
  • tasks_countinteger
  • tasks_errorinteger
  • timestring
  • versionstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use DataForSEO — Dataforseo Labs / Google / Bulk Traffic Estimation / Live with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.