DataForSEO: Dataforseo Labs Google Historical Bulk Traffic Estimation Live

Historical monthly Google search traffic estimates for up to 1,000 domains over a date range.

Tool ID: dataforseo_dataforseo_labs_google_historical_bulk_traffic_estimation_live

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'dataforseo_dataforseo_labs_google_historical_bulk_traffic_estimation_live',
  {
    "targets": [
      {}
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute dataforseo_dataforseo_labs_google_historical_bulk_traffic_estimation_live --input '{
  "targets": [
    {}
  ]
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "version": "example",
  "status_code": 123,
  "status_message": "example",
  "time": "example",
  "tasks_count": 123,
  "tasks_error": 123,
  "tasks": [
    {}
  ]
}

Use deepline describe dataforseo_dataforseo_labs_google_historical_bulk_traffic_estimation_live --json for the latest machine-readable contract.

Input reference

This endpoint will provide you with historical monthly traffic volumes for up to 1,000 domains collected within the specified time range through October 2020. If you do not specify the range, data will be returned for the previous 12 months. Along with organic search traffic estimations, you will also get separate values for paid search, featured snippet, and local pack results.

Name	Type	Required	Default	Details
`payload.targets`	`array`	Yes	—	target domains and subdomains required field you can specify domains and subdomains in this field. domains and subdomains should be specified without https:// and www. . You can set up to 1000 domains or subdomains
`payload.location_name`	`string`	No	—	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
`payload.location_code`	`integer`	No	—	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
`payload.language_name`	`string`	No	—	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
`payload.language_code`	`string`	No	—	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
`payload.date_from`	`string`	No	—	starting date of the time range optional field if you don’t specify this field, the data will be provided for the previous 12 months minimal possible value: 2020-10-01 date format: “yyyy-mm-dd”
`payload.date_to`	`string`	No	—	ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default. date format: “yyyy-mm-dd” example: “2021-04-01”
`payload.ignore_synonyms`	`boolean`	No	—	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
`payload.item_types`	`array`	No	—	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”]
`payload.tag`	`string`	No	—	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

Output reference

Top-level response envelope for dataforseo_dataforseo_labs_google_historical_bulk_traffic_estimation_live.

Name	Type	Required	Default	Details
`result.version`	`string`	Yes	—	the current version of the API
`result.status_code`	`integer`	Yes	—	general status code you can find the full list of the response codes here Note: we strongly recommend designing a necessary system for handling related exceptional or error conditions
`result.status_message`	`string`	Yes	—	general informational message you can find the full list of general informational messages here
`result.time`	`string`	Yes	—	execution time, seconds
`result.tasks_count`	`integer`	Yes	—	the number of tasks in the tasks array
`result.tasks_error`	`integer`	Yes	—	the number of tasks in the tasks array returned with an error
`result.tasks`	`array`	Yes	—	array of tasks

Deepline cost

Pricing model: provider_usage (provider usage).
Estimated Deepline credits: 0.02 per pricing unit.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation