Search & SEO

How do you get Google Trends data via API?

Call ReefAPI's google-trends engine: interest_over_time for the 0-100 curve, related_queries for top and rising queries, interest_by_region for a per-state or per-country map, plus trending_now, realtime_trending, suggest and categories. The three keyword actions were switched off from 2026-07-29 and came back on 2026-11-15, when 178 of 180 test calls across 20 keywords returned data. related_topics is still disabled and returns an explicit DISABLED error.

Google Trends engineLive JSON6 steps1,000 free credits

This guide demonstrates the real Google Trends API engine with a captured response from . The example is only published because the engine passed the SEO snapshot gate.

Use case

Trend analysis, keyword research, regional demand, newsroom alerting and demand-signal discovery.

Step by step

Call the live endpoint

  1. 1

    Disambiguate the keyword first

    google-trends/v1/suggest returns entity candidates with a mid and a type label. 'apple' resolves to a Fruit and a Technology company among others, and picking the wrong one silently changes the topic.

  2. 2

    Pull the curve with interest_over_time

    keyword, geo and timeframe (today 12-m, today 5-y, now 7-d and so on) return the 0-100 series; pass keywords with up to five terms to put them on one scale. 'black friday' in the United States returned 54 weekly points on 2026-11-15.

  3. 3

    Get top and rising queries with related_queries

    25 top and 25 rising for 'black friday' in the United States; rising entries carry a percentage or Breakout. If one keyword and region returns TARGET_BLOCKED, retry later.

  4. 4

    Map it with interest_by_region

    geo=US returns the 51 state-level regions with a 0-100 score each; resolution switches to COUNTRY, CITY or DMA.

  5. 5

    Watch what is spiking with trending_now and realtime_trending

    trending_now gives the news articles behind each trend; realtime_trending gives story clusters with related_queries, category_ids and increase_percentage. hours accepts 4, 24, 48 or 168.

  6. 6

    Treat traffic as an ordinal

    '2000+' and 2000000 are both bucket floors. Rank on them, alert on changes in them, but never total them or report them as search volume.

Code

Copy the request

These snippets use the captured request params for google-trends/v1/trending_now.

curl -X POST https://api.reefapi.com/google-trends/v1/trending_now \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"geo":"US"}'
MCP one-liner
Ask your MCP-connected assistant: call reefapi.google-trends.trending_now with {"geo":"US"}.
Real response

Captured output from ReefAPI

Captured on UTC. The response below is the committed snapshot, including the API envelope and metadata.

Captured request
{
  "method": "POST",
  "url": "https://api.reefapi.com/google-trends/v1/trending_now",
  "headers": {
    "x-api-key": "$REEF_KEY",
    "content-type": "application/json"
  },
  "body": {
    "geo": "US"
  }
}
Captured response
{
  "ok": true,
  "meta": {
    "api": "google-trends",
    "endpoint": "trending_now",
    "mode": "live",
    "latency_ms": 654.8,
    "record_count": 10,
    "bytes": 21435,
    "cache_hit": false,
    "completeness_pct": 100,
    "charged_credits": 1,
    "version": "1.2.0"
  },
  "data": {
    "geo": "US",
    "trends": [
      {
        "title": "miami airport",
        "traffic": "500+",
        "approx_traffic": 500,
        "link": "https://trends.google.com/trending/rss?geo=US",
        "picture": "https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcR3K6tdTzhCkrHFaHQw6XIXirKTZA2t8y8-TuOGhVOYbD0IurECyZl5hH-xBi8",
        "pub_date": "Wed, 23 Sep 2026 14:20:00 -0700",
        "articles": [
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          },
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          },
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          }
        ]
      },
      {
        "title": "kevin durant",
        "traffic": "500+",
        "approx_traffic": 500,
        "link": "https://trends.google.com/trending/rss?geo=US",
        "picture": "https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcQ3EyNGAFSuAojJjxgQ8ewrwgV3d2zZ5kAuR_6Dbpv-ptPVlegWwGfzBUOYgYo",
        "pub_date": "Wed, 23 Sep 2026 14:20:00 -0700",
        "articles": [
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          },
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          },
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          }
        ]
      },
      {
        "title": "khloe kardashian",
        "traffic": "500+",
        "approx_traffic": 500,
        "link": "https://trends.google.com/trending/rss?geo=US",
        "picture": "https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcT9rFVSerPT52NKJBS_AUuAnI8G86RkiJZOpVXgh8WJO2xTC2th3fbaWpvLrzs",
        "pub_date": "Wed, 23 Sep 2026 14:20:00 -0700",
        "articles": [
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          },
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          },
          {
            "title": "[trimmed-depth]",
            "url": "[trimmed-depth]",
            "source": "[trimmed-depth]",
            "picture": "[trimmed-depth]"
          }
        ]
      }
    ]
  }
}
Manual way

Why this is hard manually

Most Google Trends write-ups are built around interest_over_time: pick a keyword, a timeframe and a region, get a 0-100 curve. That is what this engine returns again since 2026-11-15, after answering DISABLED from 2026-07-29. The number is relative: 100 is the peak of the window you asked for, so two calls with different timeframes are not on the same scale, and terms are only comparable inside one call (keywords, up to five). Seven of the eight actions on this engine return data; related_topics is the one that does not, and it says so with an error rather than an empty list.

The second thing to know before building on trends data is that the 'traffic' number in the trending feeds is never a search volume. It is a bucket floor. trending_now returns it as a string with a plus sign - '200+', '2000+', '5000+' - and realtime_trending returns it as a rounded integer that only ever takes values like 50000, 100000, 200000, 500000 and 2000000. Ranking on it works. Summing it does not.

Third, 'apple' is not one thing. Google resolves keywords to entities, and until you know which entity you are asking about, two trend queries that look identical can be about a fruit and a phone company.

ReefAPI way

Why ReefAPI solves it

The keyword-analysis half of Trends is live again. On 2026-11-15 we ran 20 keywords through interest_over_time, related_queries and interest_by_region three times between 14:16 and 15:05 UTC, in the United States, the United Kingdom, Brazil, Japan, Germany, Turkey, India, Canada, Australia, France, Mexico, Spain and worldwide: 178 of 180 calls returned data (98.9%), and 15 calls made in parallel all returned data. The engine averaged 2.8 to 4.4 seconds per call; calls through the public gateway measured 1.1 to 1.8 seconds.

interest_over_time for 'black friday' in the United States over today 12-m returned 54 weekly points on the 0-100 scale, peaking in the week of 2025-11-23. The timeframes today 12-m, today 3-m, today 5-y, today 1-m, now 7-d and now 1-d all returned data, as did a category filter and a two-keyword comparison.

related_queries for the same keyword returned 25 top and 25 rising queries. Rising entries carry a percentage increase or Breakout - 'walmart black friday deals 2026' was Breakout. 2 of its 60 calls that day returned TARGET_BLOCKED ('chatgpt' worldwide and 'world cup' in Brazil); both keywords returned data in the other two rounds.

interest_by_region returned 51 state-level regions for 'black friday' in the United States, Kansas highest at 100. resolution accepts COUNTRY, REGION, CITY and DMA (US metro areas); we measured the state level.

related_topics is still disabled on 2026-11-15: ok:false, code DISABLED, HTTP 503, retryable false. Google's related-topics list has come back empty even when related queries for the same keyword returned results, so we return an explicit error rather than an empty list.

realtime_trending was rebuilt on 2026-11-15 (engine 1.3.0) after returning PARSE_ERROR on every call from 2026-11-07, when Google changed its Trending now page. It honours geo and hours: the United States feed held 76 stories for the last 4 hours, 576 for 24, 1,059 for 48 and 3,222 for 7 days, in about 0.5 to 1.0 seconds. Each story carries its related_queries array - the 'tim curry' cluster in our 2026-08-26 US run had 127 of them, from 'tim curry movies' through plain misspellings like 'tm curry' - plus started_date, active, article_count and, since 2026-11-15, increase_percentage. An unknown geo returns INVALID_PARAM; a country with no trending feed, such as Vatican City (VA), returns NOT_FOUND.

trending_now and realtime_trending look similar and are not. trending_now is the news feed: each row carries three linked articles with title, URL, source and image, a bucketed traffic string, and an RFC-822 pub_date. realtime_trending is the cluster feed: no article bodies, only article_count (44, 19, 51 on our first three stories on 2026-08-26), but the full related-query list and numeric category_ids. Use trending_now to show a reader what happened; use realtime_trending to mine what people typed.

One honest wart in trending_now: the link field is the same generic Trends RSS URL on every row, not a per-trend permalink. Do not store it as a deep link. The per-row articles carry the real destination URLs.

Timestamps come back in Google's own offset, not yours and not the region's. A German trending_now row was stamped 'Wed, 26 Aug 2026 14:30:00 -0700' - US Pacific, for a DE query. Parse the offset rather than assuming local time, or your 'trending in the last hour' window will be eight hours off.

suggest solves the entity problem in one call. Asking for 'apple' returns five candidates with a Knowledge Graph mid and a human-readable type: /m/04st9hr Topic, /m/014j1m Fruit, /m/0k8z Technology company, and so on. categories returns the full taxonomy - 1,426 entries on 2026-08-26 - and is searchable: querying 'finance' returns id 7 Finance at depth 1 under All categories, id 1138 Business Finance at depth 2 under Business & Industrial, and id 1161 Public Finance at depth 3 under Government. Pass an id as category to interest_over_time, related_queries or interest_by_region to narrow them.

FAQ

Questions developers ask

Is there a Google Trends API for interest over time?

Yes. interest_over_time returns Google Trends' 0-100 interest index as JSON for one keyword or up to five compared keywords, in any country or worldwide. Measured 2026-11-15: 'black friday' in the United States over 12 months returned 54 weekly points, peaking in the week of 2025-11-23. It had returned DISABLED from 2026-07-29 until that day.

Can I get Google Trends data by region or US state?

Yes. interest_by_region returned 51 state-level regions for 'black friday' in the United States on 2026-11-15, Kansas highest at 100. resolution accepts COUNTRY, REGION, CITY and DMA (US metro areas).

Does it support related queries and rising queries?

Yes. related_queries returns a top list and a rising list; rising entries carry a percentage increase or Breakout. 'black friday' in the United States returned 25 top and 25 rising on 2026-11-15, including 'walmart black friday deals 2026' marked Breakout. 58 of 60 related_queries calls that day returned data.

Why is related_topics not available?

It is still disabled on 2026-11-15 and answers ok:false with code DISABLED (HTTP 503), retryable false. Google's related-topics list has come back empty even when related queries for the same keyword returned results, so we return an explicit error instead of an empty list. Use related_queries and suggest instead.

Is traffic a search volume?

No. trending_now returns it as a bucket string ('200+', '2000+', '5000+') with approx_traffic as the floor integer. realtime_trending returns rounded integers that only take values like 50000, 100000, 200000, 500000, 2000000. Both are ordinals. The 0-100 values from interest_over_time are relative to the peak of the window, not counts either.

What is the difference between trending_now and realtime_trending?

trending_now gives three linked news articles per trend and no related queries. realtime_trending gives related queries, category_ids and increase_percentage but only an article_count, not the articles. They cover the same trends from opposite sides.

Why is a German trend stamped -0700?

Because Google publishes the feed in US Pacific time regardless of the geo you requested. We pass the timestamp through unchanged rather than reinterpret it. Parse the offset in the RFC-822 string.

How do I tell which 'apple' Google means?

Call suggest. It returns entity candidates with a Knowledge Graph mid and a type: /m/014j1m is the Fruit, /m/0k8z is the Technology company. The mid is the stable identifier.

How large is the category tree?

1,426 entries when we counted on 2026-08-26. categories accepts a query and returns matches with id, name, parent_id, parent_name and depth, so you can resolve 'finance' to Finance (7, depth 1), Business Finance (1138, depth 2) or Public Finance (1161, depth 3).