Google Trends

Fetch data from Google Trends API
Join our community

Actions3

Overview

This node fetches data from the Google Trends API, specifically focusing on related queries for given keywords. It allows users to input one or multiple keywords and retrieve related search queries that are trending in connection with those keywords. This is useful for market research, SEO analysis, content creation, and understanding user interest patterns around specific topics.

Use Case Examples

  1. A digital marketer wants to find related search queries for 'bitcoin' and 'ethereum' to optimize content strategy.
  2. An SEO specialist uses the node to discover trending related queries for 'cryptocurrency' to improve keyword targeting.

Properties

Name Meaning
Keyword(s) The keyword or keywords to get trends for. Multiple keywords should be separated by commas.
Start Time The start date for the trends data. If left empty, defaults to 5 years ago.
End Time The 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, here it will be 'relatedQueries'.
  • keywords - Array of keywords used for the query.
  • options
    • keyword - The keyword(s) parameter formatted for the API call.
    • startTime - Start time parameter used in the API call.
    • endTime - End time parameter used in the API call.
    • geo - Geographic location parameter used in the API call.
    • category - Category ID parameter used in the API call.
  • data - The JSON response data from the Google Trends API containing related queries information.

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, check the error message for details; it might be due to invalid parameters like incorrect date formats or unsupported geographic codes.
  • If the node is set to continue on fail, errors will be included in the output JSON under the 'error' property for each failed item.

Links

Discussion