Google Search API / Trend Analysis

The fastest Google Search API for trend analysis

A category's results page is a running record of what is gaining ground. Track how it changes week over week, in any market, with responses in under one second from $1 per 1,000 requests, dropping under $0.50 at volume.

Track result-set movement and related_searches drift over time
Compare the same term set across countries and cities
Blocked attempts are retried at our cost and never billed

<1s

Typical response time

$1/1K

List price, under $0.50 at volume

Charge for failed requests

195

Countries, city-level targeting

Who tracks category movement in search

New entrants appear on the results page before they appear in a market report. Watching that page over time is the cheapest early-warning system available.

Category and demand planning teams

See a category's competitive set changing before it reaches the sales report.

Content and editorial teams

Commission against terms where the result set is turning over, not against last quarter's winners.

Investment research

Use competitive churn in a category as an alternative signal alongside pricing and filings.

Brand and category managers

Watch your own position against the category's trajectory rather than in isolation.

Agencies and consultancies

Support a recommendation with an observable change in the market, not an assertion about it.

Why category shifts are noticed late

The signals are public and continuous. Three things stop teams from collecting them consistently.

Failure 01

Nobody stores the results page

Teams look at a category, form an impression, and move on. Without a stored series there is nothing to diff, so change is remembered rather than measured.

Change noticed only in hindsight

Failure 02

One market is not the trend

A category often turns in one country months before another. A single-market read tells you what already happened somewhere else.

Entrants spotted after they scale

Failure 03

Manual tracking dies after two weeks

Checking a handful of terms by hand is sustainable until it isn't. The series breaks exactly when it would have started being useful.

Series too short to show anything

The data a trend run returns

One call to the scraper.google.search actor returns the category's results page. Store it per run, and the diff between runs is the trend.

organic_results[]

array

Ranked results for the query.

position

integer

Organic rank, excluding ads and feature blocks.

title

string

Result headline as rendered by Google.

link

string

Destination URL.

snippet

string

Description text shown under the title.

snippet_highlighted_words

array

Terms Google bolded in the snippet.

source

string

Publisher name attributed by Google.

related_searches

object

Queries Google associates with the term — drift here is often the earliest signal a category is shifting.

knowledge_graph

object

Entity panel, when the category triggers one.

pagination

object

current, next, and other_pages for going deeper.

search_information

object

Query displayed, total results, and spelling-correction state.

metadata

object

Engine used and the stored raw page URL for auditing.

POST /api/v1/scraper/request

200 ok

# request
curl --location 'https://api.scrapeless.com/api/v1/scraper/request' \
--header 'x-api-token: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
    "actor": "scraper.google.search",
    "input": {
        "q": "cold plunge tub",
        "gl": "us",
        "hl": "en",
        "num": "20"
    }
}'

# response (trimmed)
{ "organic_results": [
    { "position": 1,
      "title":  "9 Best Cold Plunge Tubs Tested",
      "link":   "https://review-site.com/plunge",
      "source": "Review Site" } ],
  "related_searches": {},
  "search_information": {
    "total_results": 2840000 },
  "metadata": {
    "rawUrl": "https://www.google.com/…" } }

Full parameter and field reference

Mapping the whole competitive landscape rather than tracking it? See Product & market research

Read the official product reference

How trend tracking works

Build your term set

Category terms, brand terms, and competitor terms, crossed with the markets you report on. One request per pair.

Pull on a fixed schedule

Sub-second responses mean a large term set refreshes weekly or daily without the job outgrowing its window, which is what produces a usable series.

Diff run against run

New domains entering the top twenty, incumbents dropping, and related_searches drift are the three signals worth alerting on.

Built for category planning, editorial, and research teams

The fastest response in the category

Trend tracking is terms multiplied by markets, refreshed often enough to see a turn. Sub-second responses are what let a large term set run on a schedule rather than as an occasional look.

under 1s

typical vendor window

request

unblock

parse

Adjacent queries as an early signal

What Google suggests alongside a term shifts before the ranking set does. Storing related_searches per run gives you a leading indicator rather than a lagging one.

Trend Signals

related_searches{}

search_information.total_results

diff run over run

Compare markets, not just periods

Run the identical term set with different country, language, and city values. A category often turns in one market months before another, which is the most actionable version of a trend.

Market Parameters

"gl": "de" "hl": "de"

"gl": "br" "hl": "pt"

"location": city level

Depth where entrants appear first

New competitors show up at position 15 before they show up at position 3. Page with start and set num so the series captures them while it still counts as early.

Pagination

"start": 0 | 10 | 20 …

"num": results per page

pagination.next

Plans built for continuous trend tracking

Tracking cost is terms multiplied by markets multiplied by refresh rate, so effective cost per successful request decides how wide your term set can be. Start at $1 per 1,000 and move down the curve.

Basic

$0.00/1K

Pay as you go

No commitment. Consumption-based pricing at list rates.

Comparing trend tracking methods

Teams watching a category usually choose between looking it up when someone asks, licensing a panel, and storing the results page on a schedule.

Scrapeless Google Search API

Manual checks

Typical SERP API vendor

Typical response time

Under one second

Human speed

Multiple seconds

Terms per run

As many as you send

A handful

Limited by plan tier

Output

Structured JSON

An impression

Structured JSON

Cross-market comparison

City-level, 195 countries

Rarely attempted

Country-level on most plans

Entry price per 1K

$1.00, under $0.50 at volume

Analyst time

$1.00 and up

Cost of a blocked request

Never billed

Repeat the lookup

Usually billed

Start tracking category movement on the fastest, lowest-cost API

Sub-second results from $1 per 1,000 requests, dropping under $0.50 at volume, with failed requests never billed. See the full endpoint reference, parameter list, and pricing.

View the product page

Drops into the stack you already run

Official SDKs and verified nodes, so a scheduled rank pull is a configuration task rather than a build.

Python SDK

Node.js SDK

Go SDK

n8n verified node

Make

Pipedream

Activepieces

Dify

MCP server

Webhooks

Need implementation details? View product details or open the Google Search API docs for the full parameter list, response schema, and SDK examples.

Choose the search workflow your team needs

Explore focused solutions for search visibility, AI retrieval, commerce intelligence, research and monitoring. Each use case connects Google Search API results to a clear business outcome.

SEO Rank Monitoring

Measure domain visibility, ranking pages and SERP feature presence across keyword groups, markets and devices.

Local SEO & Rankings

Compare local rankings, business listings, Maps visibility and review signals across cities, regions and service areas.

AI SEO & GEO Visibility

Monitor brand mentions, citations and source visibility across AI-generated search experiences and target topics.

Product & Market Research

Study demand signals, alternatives, category presence and competing offers through structured search results.

AI Models & RAG

Give LLMs, agents and RAG pipelines current, attributable search context for grounding and retrieval workflows.

Keyword Rank Tracking

Track exact keyword positions and movement over time by location, language, device and result type.

Shopping Price Monitoring

Compare public Google Shopping prices, merchants, ratings and product visibility for selected categories.

News & Media Monitoring

Follow headlines, publishers, emerging stories and shifts in public narratives across relevant queries.

Travel Data

Structure Google Flights and Hotels results for route, stay, destination and travel-market research.

Recruitment Data

Collect Google Jobs results to monitor roles, employers, locations and labor-market demand.

Ad Verification

Verify PPC and Ads visibility, placement and competitive messaging across target queries and markets.

Academic Research

Organize Google Scholar results, authors and cited sources for academic and evidence-based research.

You are here

Trend Analysis

Use Google Trends signals to compare changing interest across topics, time periods and markets.

Image Search

Use Google Lens and Images results to discover visual matches, sources and related content.

Brand Monitoring

Track where a brand appears across organic results, news, shopping and other SERP surfaces.

Need Google Search API specifications and pricing?

Review supported Google API categories, structured response examples, integration steps and pricing on the Product page.

Questions teams ask before they buy

Which is the cheapest API for trend tracking?

Compare effective cost per successful request rather than list price. Scrapeless lists at $1 per 1,000 and drops under $0.50 at volume, and blocked attempts are never billed — which matters when most runs return little change.

Which search API is fastest for tracking a term set?

Scrapeless returns most requests in under one second, so a term set spanning hundreds of queries and several markets refreshes on schedule rather than overrunning it.

How do I turn search results into a trend?

Store the result set per run and diff between runs. New domains entering the top twenty, incumbents dropping out, and related_searches drift are the three signals that move before anything else does.

Can I compare the same terms across countries?

Yes. Send the identical term set with different gl and hl values, and pass a city in location where local structure matters. Coverage spans 195 countries and regions.

Can I track beyond the first ten results?

Yes. Use start to paginate and num to control results per request. New entrants appear well down the page before they reach the top, which is where the early signal lives.

What happens when Google changes the results layout?

Parsing is maintained on our side and the response schema stays stable, so a long-running series doesn't break when the page changes shape.

Do I still need my own proxies?

No. IP sourcing, rotation, fingerprinting, and CAPTCHA handling sit behind the endpoint, across 195 countries and regions.

Tracking hundreds of terms? Get a custom rate.

A solutions engineer will scope your term set, markets, and refresh frequency, then send back custom pricing — usually within one business day. Smaller sets can start free today.

Try for free

Explore workflow