Actions29
- Backlink Actions
- SERP Actions
- Business Data Actions
- On Page Actions
- Keywords Data Actions
- Labs Actions
Overview
The "Get Historical Traffic Stats" operation in the Labs resource of this node retrieves historical traffic statistics for specified domains or subdomains. This data typically includes metrics about organic and paid search traffic over time, segmented by location, language, and types of search results.
This node is beneficial for SEO specialists, digital marketers, and analysts who want to track how website traffic has evolved historically, understand trends, and make data-driven decisions to improve online presence. For example, a user might input multiple target domains to compare their historical organic traffic performance in a specific country and language, helping to identify seasonal trends or the impact of marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Target Domains or Subdomains | One or more domains or subdomains for which to retrieve historical traffic stats. The domain should be specified without the https:// prefix and without www.. Multiple targets can be added. |
| Location | Full name of the geographic location to filter the traffic data. Supported locations are defined by the external API documentation. |
| Language | Full name of the language to filter the traffic data. Supported languages are defined by the external API documentation. |
| Item Types | Types of search results to include in the response. Options include: Organic, Paid, Featured Snippet, and Local Pack. Multiple types can be selected to customize the scope of traffic data returned. |
Output
The node outputs an array of JSON objects where each object corresponds to the historical traffic statistics for one of the specified target domains or subdomains. The structure typically contains detailed metrics such as traffic volume over time, broken down by the selected item types (organic, paid, etc.), location, and language.
If binary data were output, it would represent associated files or reports, but this operation focuses on JSON data representing traffic statistics.
Dependencies
- Requires an active connection to the DataForSEO API v3.
- Needs an API key credential configured in n8n for authentication.
- The node sends POST requests to
https://api.dataforseo.com/v3. - Users must refer to the DataForSEO documentation for valid location and language names to ensure correct filtering.
Troubleshooting
- Invalid Domain Format: Ensure that target domains are entered without
https://orwww.prefixes. Incorrect formatting may cause the API to reject the request. - Unsupported Location or Language: Using unsupported or misspelled location or language names will result in errors. Verify these values against the official supported list linked in the property hints.
- Empty or Missing Targets: The operation requires at least one target domain; omitting this will cause the node to fail.
- API Authentication Errors: If the API key is missing, invalid, or expired, the node will throw authentication errors. Check the credentials configuration.
- Rate Limits or Quotas: Exceeding API usage limits may cause temporary failures. Monitor usage and upgrade plans if necessary.
Links and References
- DataForSEO Labs Locations and Languages Documentation — Reference for valid location and language names.
- DataForSEO API Documentation — General API usage and endpoint details.