/keywords

Keyword Research API for demand planning

View examples Talk to sales

keyword: running shoes

search_volume: 18100

example.com

Estimated monthly volume: 18,100

cpc: 1.42

example.com

Example CPC: $1.42 · competition: high

competition: HIGH

example.com

Compare monthly trends and keyword demand

search_volume: 18100

example.com

Estimated monthly volume: 18,100

search_volume: 18100

example.com

Example CPC: $1.42 · competition: high

Workflows

Illustrative workflows built with search data

Workflows

Illustrative workflows built with search data

Keywords Data API capabilities

Compare search volume, monthly trends, CPC and advertising competition. Build a keyword plan around demand, product relevance and the intent shown in the search results.

Running shoes — research example

             example.com
            

Ask which question you need to answer first. Then select the data family, fields, and collection cadence that support that decision.

Results

Research search volume, monthly history, CPC, advertising competition and keyword suggestions. Keep the source and market with each metric; Google and Bing can use different field conventions.

Running shoes — organic result

             example.com
            

Example ranking: 1 · United States · desktop · organic result.

Trail running shoes — category page

             example.com
            

Validate keyword demand with search-volume estimates, CPC, advertising competition and historical trends. Compare search and clickstream sources to prioritize commercially relevant opportunities.

Running guide — informational page

             example.com
            

Review field coverage and collection options for the endpoint you select before expanding a recurring workflow.

Example Brand — citation research

             example.com
            

Use comparable inputs for repeated research. Inspect the source context before interpreting a change as a trend.

Highlights

Generate ideas from seed terms or a target website. Group suggestions by relevance and intent rather than turning every spelling variation into a separate content opportunity.

Structured data for your workflow

              "content"
             
              : {
             
              "
              
              keyword
              
              "
             
              :
             
              cpc: 1.42 
              
              "
              
              Group related searches and compare demand before building a content or campaign plan.
              
              "
             
              :
             
              "
              
              organic
              
              "
             
              example.com
             
              "
              
              location
              
              "
             
              :
             
              "
              
              United States
              
              "
             
              example.com
             
              "
              
              Compare search demand with advertising metrics to prioritize a useful keyword set.
              
              "
             
              :
             
              "
              
              desktop
              
              "
             
              }

Structured outputs

Research advertising-related traffic and bid signals for keyword planning. Separate estimated paid-search outcomes from organic difficulty, clicks and conversion forecasts.

Structured data for your workflow

Review monthly trends and distinguish absolute volume estimates from normalized popularity scores. 1 Plan API requests for individual tasks or discuss a bulk dataset when your analysis needs a broader historical view. 2 3 The demo records are illustrative. Discuss production access, request volume, and collection cadence with the DataSEO team. 4 .

AI Summary

Use Google Trends and DataForSEO Trends data to investigate changing interest, geographic patterns and available demographic signals. Normalized trend scores are not absolute monthly search counts.

Illustrative response fields

Compare supported clickstream-derived demand with advertising-platform metrics. Keep source definitions and periods visible when combining local, global or bulk keyword-volume research.

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Sample collection 46.0% / 2.7s

Sample collection 41.0% / 1.3s

Example collection 43.0% / 547ms

Sample collection 50.0% / 583ms

Accuracy / Latency

Example keyword intelligence

Accuracy / Latency

Example coverage (%)

30%

40%

50%

60%

70%

80%

90%

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Sample collection 46.0% / 2.7s

Sample collection 41.0% / 1.3s

Example collection 43.0% / 547ms

Sample collection 50.0% / 583ms

300ms 500ms 1s 2s 4s

Latency (ms, log scale)

Pricing

Collection scope and access

Request a quote for your volume

View examples Talk to sales

batch Queued

Scheduled data collection

live Live

Use volume, advertising activity, seasonality, search intent and product relevance together. Link each chosen topic to a useful page and a defined conversion path.

extended Extended

Confirm the selected route and source

FROM IDEA TO FIRST REQUEST

Build with Keywords Data API

Research keywords for a selected location and language. Review search volume together with monthly history before treating a temporary spike as sustained demand.

Read the docs ↗Talk to our team ↗

NODE.JS

// Server-side example; configure your deployment and credentials.
const url = new URL("/v3/keywords_data/google_ads/search_volume/live", process.env.DATASEO_API_ORIGIN);
const auth = Buffer.from(`${process.env.DATASEO_LOGIN}:${process.env.DATASEO_PASSWORD}`).toString("base64");
const response = await fetch(url, {
  method: "POST",
  headers: {Authorization: `Basic ${auth}`, "Content-Type": "application/json"},
  body: JSON.stringify([{"keywords": ["running shoes"], "location_code": 2840, "language_code": "en"}])
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
for (const task of data.tasks ?? []) {
  if (task.status_code !== 20000) throw new Error(task.status_message);
}
// Use task.result only after checking task status.

Browse the complete API endpoint reference