Google Trends

Fetch data from Google Trends API
Join our community

Actions3

Overview

This node fetches data from the Google Trends API, specifically providing insights into the popularity of search keywords over time. It is useful for analyzing trends in search interest, identifying related queries, and discovering related topics for given keywords. Practical applications include market research, SEO analysis, and monitoring public interest in specific topics or products.

Use Case Examples

  1. Tracking the interest over time for cryptocurrencies like Bitcoin and Ethereum to understand market trends.
  2. Finding related queries to a keyword to optimize content for SEO.
  3. Discovering related topics to a keyword to expand content strategy or research areas.

Properties

Name Meaning
Keyword(s) Keyword(s) to get trends for. Multiple keywords can be separated by commas.
Start Time Start date for the trends data. If left empty, defaults to 5 years ago.
End Time End date for the trends data. If left empty, defaults to the current time.
Geography Geographic location specified by ISO 3166-1 alpha-2 country code. Leave empty for worldwide data.
Category Category ID for trends data. 0 means all categories.

Output

JSON

  • operation - The operation performed, e.g., interestOverTime.
  • keywords - Array of keywords used for the trends query.
  • options
    • keyword - Keywords parameter sent to the Google Trends API.
    • startTime - Start time parameter for the trends query.
    • endTime - End time parameter for the trends query.
    • geo - Geographic location parameter for the trends query.
    • category - Category ID parameter for the trends query.
  • data - Parsed JSON response from the Google Trends API containing the trends data.

Dependencies

  • google-trends-api npm package

Troubleshooting

  • Ensure the 'Keyword(s)' field is not empty; the node throws an error if keywords are missing.
  • If the Google Trends API returns an error, the node will throw an error unless 'Continue On Fail' is enabled, in which case it outputs the error message in the JSON output.
  • Date fields must be valid date-time strings if provided; invalid dates may cause API errors.

Links

Discussion