DataForSEO icon

DataForSEO

DataForSEO

Overview

The "Get Google Search Volume" operation of the Keywords Data resource allows users to retrieve search volume and related metrics for a list of keywords on Google. This node is useful for SEO specialists, digital marketers, and content creators who want to analyze keyword popularity, competition, and trends over time to optimize their campaigns or content strategies.

Typical use cases include:

  • Estimating monthly search volumes for targeted keywords.
  • Comparing keyword competitiveness and bid prices for paid advertising.
  • Filtering keywords by location and language to tailor regional campaigns.
  • Tracking historical search volume trends within a specified date range.

For example, a user can input up to 1000 keywords and specify a location like "London,England,United Kingdom" and language "English" to get localized search volume data, helping them prioritize keywords for a UK-based campaign.

Properties

Name Meaning
Keywords A collection of keywords (up to 1000) to query. Each keyword can be up to 80 characters and contain up to 10 words. Keywords are converted to lowercase automatically.
Location Full name of the geographic location to filter results by (e.g., "London,England,United Kingdom"). Supported locations are documented externally.
Language Full name of the language to filter results by (e.g., "English"). Supported languages are documented externally.
Include Google Search Partners? Boolean flag indicating whether to include search volume data from Google's owned, operated, and syndicated partner sites in addition to Google search itself. Defaults to false (only Google search).
Include keywords associated with adult content? Boolean flag to include adult-related keywords in the response if set to true. Defaults to false.
Date From Starting date of the time range for which to retrieve search volume data. Minimum allowed is 4 years before the current date. If not specified, defaults to the past 12 months.
Date To Ending date of the time range. Cannot be later than the previous month (Google Ads does not provide current month data). Defaults to yesterday's date if not specified.
Sort By Option to sort the returned keywords by one of: Relevance, Search Volume, Competition Index, Low Top Of Page Bid, High Top Of Page Bid, or leave empty for no sorting.

Output

The node outputs an array of JSON objects, each representing keyword data with fields such as:

  • Keyword text (lowercase)
  • Search volume metrics (e.g., average monthly searches)
  • Competition index
  • Top of page bid estimates (low and high)
  • Possibly additional metadata depending on the API response

The output structure directly reflects the data returned by the external API for the requested keywords and parameters.

This node does not output binary data.

Dependencies

  • Requires an active API key credential for the DataForSEO service configured in n8n.
  • The node makes POST requests to the DataForSEO API endpoint at https://api.dataforseo.com/v3.
  • Users must ensure that the specified locations and languages are supported by consulting the DataForSEO documentation.
  • Internet connectivity is required for API communication.

Troubleshooting

  • Common issues:

    • Exceeding the maximum number of keywords (1000) or keyword length/word count limits may cause errors.
    • Specifying unsupported location or language names will result in API errors.
    • Providing invalid date ranges (e.g., dates too far in the past or future) may cause the API to reject the request.
    • Network or authentication failures due to missing or incorrect API credentials.
  • Error messages:

    • "Something went wrong": Generic error thrown if the operation handler is not found; usually indicates misconfiguration.
    • API errors related to invalid parameters will typically include descriptive messages from the DataForSEO service.
  • Resolutions:

    • Validate all input properties against documented constraints.
    • Verify API credentials and network access.
    • Consult DataForSEO documentation for supported values and limits.

Links and References

Discussion