Actions49
- Amazon Actions
- App Store Actions
- Bing Actions
- Google Actions
- Get Bulk Traffic Estimation
- Get Categories For Domain
- Get Categories For Keywords
- Get Competitors Domain
- Get Domain Intersection
- Get Domain Metrics By Categories
- Get Domain Rank Overview
- Get Historical Bulk Traffic Estimation
- Get Historical Keyword Data
- Get Historical Rank Overview
- Get Historical SERPs
- Get Keyword Difficulty
- Get Keyword Ideas
- Get Keyword Overview
- Get Keyword Suggestions
- Get Keywords For Categories
- Get Keywords For Site
- Get Page Intersection
- Get Ranked Keywords
- Get Related Keywords
- Get Relevant Pages
- Get Search Intent
- Get SERP Competitors
- Get Subdomains
- Get Top Searches
- Google Play Actions
Google → Get Historical Bulk Traffic Estimation
AI-generatedSummary
Retrieves historical Google traffic estimates for up to 1,000 domains, subdomains, or webpages over a date range. Supply targets manually or as a JSON array, with optional location, language, synonym filtering, and search result item types.
Inputs
- Input Mode (required) — Choose Manual to enter targets individually or JSON to provide them as an array.
- Targets (required) — Up to 1,000 domains or subdomains without https:// or www., or webpages specified as absolute URLs including the scheme and www. Available in Manual mode.
- Targets JSON Array (required) — An array of up to 1,000 domains, subdomains, or webpages, using the same formatting rules as Manual mode. Available in JSON mode.
- Date From — Starting date of the historical time range.
- Date To — Ending date of the range; when omitted, the API uses today's date.
- Location — Full location name, such as United Kingdom.
- Language — Full language name, such as English.
- Ignore Synonyms — When enabled, excludes highly similar keywords and returns only core keywords.
- Item Types — Select search result types to include: Organic, Paid, Featured Snippet, or Local Pack.
Output shape
A response from the DataForSEO Labs Google historical bulk traffic estimation endpoint.
The supplied source pack contains function signatures but not implementation bodies, so it does not establish the exact response structure.