/serp

SERP API for localized search results

View examples Talk to sales

keyword: running shoes

example.com

Rank 1 · desktop · United States

keyword: running shoes

example.com

Rank 2 · commercial intent

Running guide — informational result

example.com

keyword: running shoes

example.com

Rank 1 · desktop · United States

keyword: running shoes

example.com

Rank 2 · commercial intent

Workflows

Illustrative workflows built with search data

Workflows

Illustrative workflows built with search data

SERP API capabilities

Collect ranked URLs, ads and search features by keyword, market, language and device. Choose live or queued collection and use structured results in your own rank tracker.

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

Collect Google, Bing, Yahoo, Baidu, YouTube, Naver and Seznam results through source-specific endpoints. Research organic results and supported maps, news, images, jobs, shopping and other search surfaces.

Running shoes — organic result

             example.com
            

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

Trail running shoes — category page

             example.com
            

Collect organic results, ads and search features across supported search engines, markets and devices. Use structured JSON, HTML and source-specific collection options for rank tracking and competitive research.

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

Set the query, location, language and device for repeatable research. Preserve rank_group and rank_absolute to distinguish positions within a result type from placement across the whole page.

Structured data for your workflow

              "content"
             
              : {
             
              "
              
              keyword
              
              "
             
              :
             
              keyword: running shoes 
              
              "
              
              result_type
              
              "
             
              :
             
              "
              
              organic
              
              "
             
              example.com
             
              "
              
              location
              
              "
             
              :
             
              "
              
              United States
              
              "
             
              example.com
             
              "
              
              device
              
              "
             
              :
             
              "
              
              desktop
              
              "
             
              }

Structured outputs

Choose advanced structured results, regular results or HTML where the endpoint supports them. Keep item types visible so your parser reads the fields relevant to each search feature.

Structured data for your workflow

Compare the results your audience sees in different markets and on desktop or mobile. 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 screenshot and AI-summary capabilities when your workflow needs a visual record or an additional interpretation of the result page. Retain the underlying query and source context.

Illustrative response fields

Use live requests for immediate checks or queued tasks for scheduled workloads. Track task identifiers and retrieval status separately from the search observations returned.

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 search 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

Compare dated results for the same keyword set, markets and devices. Connect ranking changes to URLs, competing pages and result features before deciding what to investigate.

extended Extended

Confirm the selected route and source

FROM IDEA TO FIRST REQUEST

Build with SERP API

Set the keyword, search engine, location, language and device. Preserve those settings with each observation so ranking comparisons describe the same audience and market.

Read the docs ↗Talk to our team ↗

NODE.JS

// Server-side example; configure your deployment and credentials.
const url = new URL("/v3/serp/google/organic/live/advanced", 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([{"keyword": "running shoes", "location_code": 2840, "language_code": "en", "device": "desktop"}])
});
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