Rising Keywords Scraper — Google Trends Breakout Queries

Seed keywords in, Google's rising and Breakout queries out — with the growth number Google's own UI hides. When a query grows more than about +5,000%, Google Trends stops showing a percentage and prints the word Breakout. The number is still in the payload, and this actor ships it:

nike mind 001

Just want to see it work? Click Start without typing keywords and the run fetches up to 5 rising queries for one real seed (ai agents), charged like any run at your plan's per-row price. Set a region, a time range or any other setting and leave the keywords empty, and that same sample runs under your settings — one uncharged note row names them, and a row limit above the sample's own 5 is a ceiling, not a request. Put your own seeds in searchTerms for your own run.

Unofficial. This actor is not affiliated with, endorsed by, or sponsored by Google. "Google" and "Google Trends" are trademarks of Google LLC, used here only to describe what this tool reads.

You only pay for keyword rows that are delivered. Every row carries status and charged, so the invoice reconciles against the dataset itself. Only rows with charged: true were billed.

Output

This is the dataset table of a real run — rising queries for the seed ai agents — exactly as it appears in the Apify console:

Real output, unedited:

{
  "schemaVersion": 1,
  "seedKeyword": "ai agents",
  "query": "moltbook",
  "kind": "rising",
  "rank": 1,
  "isBreakout": true,
  "growthPercent": 64700,
  "value": 64700,
  "formattedValue": "Breakout",
  "trendsUrl": "https://trends.google.com/trends/explore?q=moltbook&date=today+12-m",
  "timeline": null,
  "geo": "",
  "timeRange": "today 12-m",
  "category": 0,
  "status": "ok",
  "message": null,
  "charged": true,
  "fetchedAt": "2026-08-27T05:52:11.104Z"
}

And the row you are not charged for, when a seed has too little search volume for Google to compute a rising list at all:

{
  "seedKeyword": "best project management software for small teams",
  "query": null,
  "status": "no_rising_data",
  "charged": false,
  "message": "Google Trends has no rising queries for this seed in the selected time range and region — this row was not charged. Seeds need real search volume before Google will compute a rising list."
}

Browse the full live example dataset → — one real run of the current code, unedited: 13 rows — 11 charged adidas rising queries with their growth numbers, one seed that returned nothing and was not charged, and the run's own summary row last.

isBreakout is Google's own label and nothing else — we never derive it from the number. A query at +1,500% is a big riser and is still not a Breakout, because Google did not call it one.

The dataset schema and Output tab carry the same fields, so status and charged filter cleanly in the console, the API and any spreadsheet export.

The last row of every run is an uncharged summary row — _summary: true, status: "run_summary", charged: false — carrying delivered, noticeRows, seedsRequested, seedsDone, seedsLeft, stoppedBy and chargedEvents. Its chargedEvents["breakout-keyword"] equals the number of rows above it marked charged: true, so the invoice reconciles from the dataset alone. Export with clean=true for a spreadsheet-ready CSV, and reconcile from the per-row charged flags immediately, or from the run's charge counter once it settles (about 12 seconds after the run ends).

Agent / API paste-block

Actor:      steadyfetch/breakout-keywords-scraper
Required:   searchTerms           (array of seed keywords — leave it out for a sample run; any setting you
                                   send alongside is applied to that sample)
Optional:   geo                   (string, "" = worldwide, or "US", "GB", "DE", "US-CA")
            timeRange             (now 1-H | now 4-H | now 1-d | now 7-d | today 1-m | today 3-m |
                                   today 12-m | today 5-y | all — default "today 12-m")
            category              (integer Google Trends category id, default 0 = all)
            breakoutOnly          (boolean, default false — only rows Google labels "Breakout")
            minGrowthPercent      (integer, default 0 — drop rising rows under this growth)
            includeTop            (boolean, default false — also return the top-queries list)
            maxResultsPerKeyword  (integer 1-25, default 25 — Google's own ceiling is 25)
            includeTimeline       (boolean, default false — attach the 12-month curve)
            timelineLimit         (integer 0-25, default 5 — curves per seed)
Charges:    breakout-keyword      once per delivered keyword row
Build spec: https://apify.com/steadyfetch/breakout-keywords-scraper/api
Token:      https://console.apify.com/settings/integrations

curl -X POST "https://api.apify.com/v2/acts/steadyfetch~breakout-keywords-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"searchTerms":["ai agents","weight loss"],"geo":"US","breakoutOnly":true}'

Calling from an agent or MCP client: omit an option you do not want rather than sending null — the platform rejects an explicit null before the run is even created.

What each seed costs

One event, breakout-keyword, charged once per delivered keyword row — from $1.50/1,000 breakout keywords on the volume tier, $0.0060 each on the free plan. No start fee, no minimum, no subscription. Google caps each list at 25 rows per keyword, so a seed that returns a full rising set is 25 rows; the median across 90 measured keyword × country combinations was 23.

Rows that were not charged, and never will be:

Maximum cost per run is the ceiling. The run stops cleanly against it and tells you how many seeds were left, rather than being killed mid-way.

Which seeds actually return data

Measured over 90 keyword × country combinations before this actor was built:

Anything a keyword researcher would realistically type comes back full. Sentences and very thin niches come back empty — and an empty seed is never charged. Use the head term instead.

Country matters: the same seed returns different rising queries in the US, GB, IN and DE. So does category — ai agents under Computers & Electronics returns a different top rising query than under all categories.

Chaining: from a breakout keyword to the ads already running on it

The natural next question after "what is breaking out?" is "who is already advertising on it, and what do their ads say?" Look the breakout query up in an ad library, then hand the advertiser domain or the ad links to the matching actor below and get the words those ads actually use.

There is a ready-made n8n workflow template for this actor — see Free templates below.

Freshness and failures

Rising data is computed by Google against the time range you pick, and it moves daily — the same seed can return a different rising set tomorrow. Rows carry fetchedAt so you always know when a figure was true.

This actor may fail when the platform changes things — failed items are never charged.

FAQ

How do I find breakout keywords on Google Trends? Pass your seed keywords in searchTerms. Each seed returns Google's rising related queries, and the ones Google labels Breakout carry isBreakout: true plus the real growth percentage.

What does "Breakout" mean in Google Trends? Google prints Breakout instead of a percentage when a query's growth is above roughly +5,000%. It is a display cut-off, not a separate metric — this actor gives you the underlying number.

Can I get rising keywords for a specific country? Yes, set geo to a country code (US, GB, DE) or a sub-region (US-CA). Leave it empty for worldwide.

Can I filter to only the fastest-growing queries? Set breakoutOnly: true for Google-labelled Breakouts, or minGrowthPercent for a numeric floor. Filtered-out rows are never charged.

What happens if I set a filter but no keywords? The sample runs under your settings: your region, time range, category and filters are kept, everything you did not set takes the sample's own value, and a row limit above the sample's own 5 is treated as a ceiling. One uncharged sample_note row names the settings that were kept. Only an input field name this actor does not recognise, or a searchTerms list you filled with blanks, gets a guidance row instead.

Why did my keyword return no rising data? Google needs enough search volume to compute a rising list. Whole sentences and very thin niche phrases usually return nothing at all — you get an uncharged no_rising_data row instead of an empty run.

Does it return related topics as well as queries? No — this actor is built around rising and Breakout queries only. Related topics are a different surface, and its sibling Google Trends Scraper — Interest Over Time, Related Queries delivers them: add relatedTopics to that actor's surfaces for the top and rising topic entities with their knowledge-graph ids.

Can I use this through an MCP server? Yes. It is a standard Apify actor, so any MCP client that can call Apify actors can call it.

Why does a run cost more than the keyword rows? Apify bills platform usage (compute and proxy) for what a run actually consumes, separately from these events. Maximum cost per run is the ceiling that covers both.

Steadyfetch trends & keyword suite

One actor per surface, one job each, the same contract everywhere: all-inclusive pay per event, nothing charged for starting a run, charged only on delivery — so a workflow built for one of them ports to the next. Keyword volume is the one exception: from 16 September 2026 a run that buys fresh volume data adds one fresh-lookup fee of $0.19; runs answered from the 30-day cache pay none.

The rest of the steadyfetch shelf — same contract everywhere: all-inclusive pay per event, nothing charged for starting a run, charged only on delivery (three actors add a small delivery-conditional fee from 16 September 2026: keyword volume's fresh lookup, profile posts' profile lookup, Google Jobs' search fee — each README states it).

Free templates

Free n8n workflow templates for this actor are listed on our profile website (link on our Apify profile).

Feedback & support

Found an issue? Open it on the Issues tab — we usually reply within a couple of hours, always within a day.

Using an AI agent? Pin this actor in Apify's MCP server with one link: https://mcp.apify.com?tools=steadyfetch/breakout-keywords-scraper.

If it earned its keep, a rating helps other buyers find it, and saving the actor keeps it one click away.