# Google Trends SEO Keyword Data

**Google Trends SEO Keyword Data** is an independently documented x402 Atlas bridge at https://google-trends.use.x402atlas.com.
This document describes only this bridge; it does not aggregate routes, schemas,
or content from any other bridge.

## How payment works

Paid operations use the [x402 payment protocol](https://x402.org) and settle in
USDC. Atlas supports deployments on Base, Polygon, and Arbitrum, plus configured
Solana networks. This bridge currently advertises Arbitrum One (`eip155:42161`), Base (`eip155:8453`), Polygon (`eip155:137`), Solana mainnet (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`).

1. Send the HTTP request without a payment signature.
2. Read the `402 Payment Required` response. Its `accepts` entries are the
   authoritative network, asset, amount, and recipient options for that call.
3. Select an option, sign it with an x402-compatible wallet or SDK, and repeat
   the request with the `PAYMENT-SIGNATURE` header. The successful response is
   returned after verification and settlement.

TypeScript clients can automate the challenge, signing, and retry flow with
[`x402-fetch`](https://www.npmjs.com/package/x402-fetch) or
[`x402-axios`](https://www.npmjs.com/package/x402-axios). Fund a dedicated
wallet only with the working USDC balance it needs and keep that key separate
from treasury accounts.

## Pricing

Atlas route prices start at $0.005 per successful call. This bridge's fallback
price is $0.005; operations below state their exact configured price in
`x-x402` and `x-payment-info`. The live `402` challenge remains authoritative.

## Worked payment example

Request one documented operation without a signature to inspect its live terms:

```bash
curl -i 'https://google-trends.use.x402atlas.com/interest-by-region?country=us&keyword=bitcoin'
# HTTP/1.1 402 Payment Required
# Read accepts[].network, asset, amount, and payTo from this response.
```

Sign one accepted option and repeat the identical request with the
`PAYMENT-SIGNATURE` header. Do not invent or cache payment terms; read them from
the current challenge.

## Use this API

- Interactive reference: https://google-trends.use.x402atlas.com/docs
- OpenAPI 3.1 specification: https://google-trends.use.x402atlas.com/openapi.json
- Agent-readable route corpus: https://google-trends.use.x402atlas.com/llms.txt
- Endpoint index: https://google-trends.use.x402atlas.com/index.json

Use the operation schemas and examples below to construct requests. Copy the
server URL, path, method, parameters, and request body from the operation you
want to call. Path and query examples are concrete and can be used directly.

## Atlas response metadata

Successful JSON responses include an additive top-level `_atlas` block, kept
separate from the bridge's data fields. `_atlas.docs` links this bridge's
`/llms.txt` corpus. `_atlas.related` suggests adjacent APIs, each with a callable
`url`, its own `docs` link, and a short `summary`. Suppress this block by sending
`X-Atlas-Meta: none` or by adding `?_atlas=0` to the request.

## Errors and compatibility

Validation failures use HTTP `400`. Paid operations may return `402` before
dispatch. Upstream and internal failures use the documented `5xx` responses.
Clients should rely on documented fields and tolerate additive response fields,
including `_atlas` unless they explicitly opt out.

## Protocol reference

- x402 protocol and SDKs: https://x402.org

## Google Trends SEO Keyword Data

Docs: https://google-trends.use.x402atlas.com/docs · OpenAPI: https://google-trends.use.x402atlas.com/openapi.json

### GET /interest-by-region

Google Trends interest by region for a keyword — search popularity by geography for geo-targeting, local SEO and market research.

Google Trends interest broken down by geographic region for a concise seed `keyword` within a `country` (both required; `country` is a short ISO code like `us`, lower-cased before use). This analyzes aggregate Google Trends data: it does not search the web, answer a question, or follow an instruction. Use an established term with meaningful search interest; highly specific or low-volume phrases can return an empty `regions` list. Returns `{ keyword, country, queried_at, regions }`, where `regions` contains `{ region, value }` and `value` is the 0–100 relative search popularity across that country's subregions. Use it for geo-targeting, local SEO, market research, and regional demand mapping; for a global timeline use `/trend`, and for idea generation use `/related-queries` or `/related-topics`.

**Price:** 0.03 per call.

Parameters:
- `country` (required, string) — Country code, e.g. us (case-insensitive); maxLength: `8`; example: `"us"`
- `keyword` (required, string) — Concise Google Trends seed term with meaningful search interest; not a question, instruction, or web-search request; maxLength: `100`; example: `"bitcoin"`

Example:

```sh
curl 'https://google-trends.use.x402atlas.com/interest-by-region?country=us&keyword=bitcoin'
```

Response example:

```json
{
  "country": "us",
  "keyword": "bitcoin",
  "queried_at": "2026-06-05T12:00:00Z",
  "regions": [
    {
      "region": "California",
      "value": 100
    }
  ]
}
```

### GET /related-queries

Google Trends related search queries for a keyword by country — top & rising terms for SEO keyword research, query expansion and content ideas.

Google Trends related search *queries* for a concise seed `keyword` within a `country` (both required; `country` is a short ISO code like `us`, lower-cased before use). This analyzes aggregate Google Trends data: it does not search the web, answer a question, or follow an instruction. Use an established term with meaningful search interest, such as `bitcoin` or `electric vehicles`; highly specific or low-volume phrases can return empty `top` and `rising` lists. Returns `{ keyword, country, queried_at, top, rising }`, where both lists contain `{ term, value }` — `value` is a 0–100 popularity score for `top` and a growth index for `rising`. Use the results for keyword research, query expansion, content ideas, and demand discovery; for higher-level entities/subjects use `/related-topics`, and for a global timeline use `/trend`.

**Price:** 0.03 per call.

Parameters:
- `country` (required, string) — Country code, e.g. us (case-insensitive); maxLength: `8`; example: `"us"`
- `keyword` (required, string) — Concise Google Trends seed term with meaningful search interest (for example bitcoin or electric vehicles); not a question, instruction, or web-search request; maxLength: `100`; example: `"solana"`

Example:

```sh
curl 'https://google-trends.use.x402atlas.com/related-queries?country=us&keyword=solana'
```

Response example:

```json
{
  "country": "us",
  "keyword": "solana",
  "queried_at": "2026-06-05T12:00:00Z",
  "rising": [
    {
      "term": "solana etf",
      "value": 250
    }
  ],
  "top": [
    {
      "term": "solana price",
      "value": 100
    }
  ]
}
```

### GET /related-topics

Google Trends related topics for a keyword by country — top & rising topics for SEO content research, trend discovery and market analysis.

Google Trends related *topics* for a concise seed `keyword` within a `country` (both required; `country` is a short ISO code like `us`, lower-cased before use). This analyzes aggregate Google Trends data: it does not search the web, answer a question, or follow an instruction. Use an established term with meaningful search interest; highly specific or low-volume phrases can return empty `top` and `rising` lists. Returns `{ keyword, country, queried_at, top, rising }`, where both lists contain `{ term, value }` — `value` is a 0–100 popularity score for `top` and a growth index for `rising`. Use the results for content ideas, topic discovery, SEO research, and market research. Topics are higher-level subjects/entities rather than literal search strings; for exact related searches use `/related-queries`, and for a global timeline use `/trend`.

**Price:** 0.03 per call.

Parameters:
- `country` (required, string) — Country code, e.g. us (case-insensitive); maxLength: `8`; example: `"us"`
- `keyword` (required, string) — Concise Google Trends seed term with meaningful search interest; not a question, instruction, or web-search request; maxLength: `100`; example: `"bitcoin"`

Example:

```sh
curl 'https://google-trends.use.x402atlas.com/related-topics?country=us&keyword=bitcoin'
```

Response example:

```json
{
  "country": "us",
  "keyword": "bitcoin",
  "queried_at": "2026-06-05T12:00:00Z",
  "rising": [
    {
      "term": "Spot ETF",
      "value": 180
    }
  ],
  "top": [
    {
      "term": "Cryptocurrency",
      "value": 100
    }
  ]
}
```

### GET /trend

Google Trends interest over time for a keyword — worldwide search popularity as a monthly series for keyword research, SEO & demand trend analysis.

Worldwide Google Trends interest-over-time for one concise seed `keyword` (required) — this route takes no `country` and is always global. This analyzes aggregate Google Trends data: it does not search the web, answer a question, or follow an instruction. Use an established term with meaningful search interest; highly specific or low-volume phrases can return an empty `series`. Returns `{ keyword, queried_at, series }`, where `series` is a monthly timeline of `{ date, value }` (ISO `YYYY-MM-DD` dates; `value` is the 0–100 relative search-popularity index). Use it for keyword research, demand-trend discovery, content planning, and seasonality analysis; for geographic research use `/interest-by-region`, and for idea generation use `/related-queries` or `/related-topics`.

**Price:** 0.05 per call.

Parameters:
- `keyword` (required, string) — Concise Google Trends seed term with meaningful search interest; not a question, instruction, or web-search request; maxLength: `100`; example: `"bitcoin"`

Example:

```sh
curl 'https://google-trends.use.x402atlas.com/trend?keyword=bitcoin'
```

Response example:

```json
{
  "keyword": "bitcoin",
  "queried_at": "2026-06-05T12:00:00Z",
  "series": [
    {
      "date": "2026-05-01",
      "value": 78
    }
  ]
}
```