npm google-trends-api Alternative

The unofficial npm package google-trends-api is a Node layer over Google Trends. npm lists 4.9.2, last published December 2020. Weekly downloads stay high. The readme's call shape is googleTrends.apiMethod(optionsObject, [callback]). Options include keyword, startTime, endTime, geo, hl, category, and property (images, news, youtube, froogle). Methods include interestOverTime, interestByRegion, relatedQueries, relatedTopics, dailyTrends, realTimeTrends, and autoComplete. That is Explore in JavaScript. Trends API is fetch, not require. The POST is on the API reference.

require() is not a source

const googleTrends = require('google-trends-api');
googleTrends.interestOverTime({ keyword: 'air fryer' });

The function name is the widget. There is no mode. There is no source. property: 'youtube' is YouTube search interest on Trends, not the live board Trends API names as type YouTube Trending.

The readme says the library is for Node because of CORS. Putting it in a browser bundle was never the design. Putting it on a serverless function still uses that function's IP against Google.

Unofficial endpoints, already broken once

The v3-to-v4 section exists because old Trends endpoints were deprecated and throttled. The package adapted once. It has not shipped a release since 4.9.2.

GitHub issue 175 (opened Feb 2025, still discussed in 2026) reports dailyTrends returning 404 after Google retired the old daily RSS. The workaround in that thread is the new trending/rss feed, not a patched npm method. That RSS stop is on the RSS alternative.

RapidAPI listings often wrap this class of client. Shopping those listings is the RapidAPI page. The R equivalent of the same scrape class is gtrendsR.

fetch instead of the package

{
  "mode": "get_time_series",
  "source": "google search",
  "keyword": "air fryer"
}

POST that JSON to https://api.trendsapi.ai/api. Parse the response, then parse the body string. value is 0-100. For a live Google list, switch to get_top_trends and type Google Trends. For another platform, change source or type. Those strings are not npm method names.

Keep google-trends-api for a small Node script that only needs Google and can absorb a breakage. Leave when the same service must share a contract with Python or must read Amazon. The language-wide shopping list is modern pytrends replacements.

Common questions

What is the npm google-trends-api package?

An unofficial Node library (pat310/google-trends-api on GitHub) that calls Google Trends methods such as interestOverTime, interestByRegion, relatedQueries, relatedTopics, dailyTrends, and autoComplete. The readme says CORS keeps it on the server. It is not Google's official API.

Does the package support the official Google Trends alpha?

No. It targets the public Trends site's unofficial endpoints, and npm still serves 4.9.2 from December 2020. GitHub issue 175 reports dailyTrends 404 after Google retired the old daily RSS. That is the current risk, not a missing official-alpha flag.

Can this package read sources other than Google?

Documented methods are Google Trends widgets. There is no source argument for TikTok or Steam. A second npm package for another site is a second unofficial client.

What does a Node replacement look like?

fetch POST to https://api.trendsapi.ai/api with Authorization Bearer and a JSON body. Parse JSON, then parse the body string. npm install trendsapi decodes the envelope if the team does not want raw fetch.

The npm google-trends-api package, and where it stops

require() is not a source

Unofficial endpoints, already broken once

fetch instead of the package

What you get

Common questions

Related

Start pulling trend data in 60 seconds.

Get your free API key

Check your inbox