/search

Rank Tracking API for search visibility

running shoes

Build a rank tracker with consistent keywords, locations, languages and devices. Follow ranking URLs and search features over time, then investigate the changes that matter.

example.com

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

Running shoes — category page

example.com

Research organic search, maps, news, images, shopping and other supported result types. Use item types to interpret the fields returned by each endpoint.

rank_group describes a position within a result type, while rank_absolute describes placement across the results page. Keep both when ads or rich features affect visibility.

example.com

Use live collection for immediate checks or task-based collection for scheduled workloads. Select the response format and result depth that fit your integration.

Track a consistent keyword set across locations and devices. Compare current observations with dated records to investigate search visibility and competing pages.

example.com

Retain task status, collection time and source settings alongside result URLs. Route individual collection failures separately from changes in a domain’s rankings.

Example Brand — AI citations

example.com

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

Workflows

Illustrative workflows built with search data

Workflows

Illustrative workflows built with search data

Outputs structured for your workflow

Research organic search, maps, news, images, shopping and other supported result types. Use item types to interpret the fields returned by each endpoint.

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

rank_group describes a position within a result type, while rank_absolute describes placement across the results page. Keep both when ads or rich features affect visibility.

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
            

Track a consistent set of keywords, locations, and devices over time.

Example Brand — citation research

             example.com
            

No. Engines and result types have their own coverage and request options. Select the endpoint that matches your workflow.

Highlights

Use live collection for immediate checks or task-based collection for scheduled workloads. Select the response format and result depth that fit your integration.

Structured data for your workflow

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

Structured outputs

Track a consistent keyword set across locations and devices. Compare current observations with dated records to investigate search visibility and competing pages.

Structured data for your workflow

Compare the results your audience sees in different markets and on desktop or mobile. 1 Start with the targets and markets you need to investigate. Keep the source and collection time with each SERP API response. 2 3 Combine SERP API with complementary datasets when your question spans search visibility, demand, links, page health, or AI citations. 4 .

AI Summary

Retain task status, collection time and source settings alongside result URLs. Route individual collection failures separately from changes in a domain’s rankings.

Explore search visibility by market

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

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Parallel (Adv) 46.0% / 2.7s

Parallel (Basic) 41.0% / 1.3s

Brave 43.0% / 547ms

Perplexity 50.0% / 583ms

Accuracy / Latency

Search visibility

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

Parallel (Adv) 46.0% / 2.7s

Parallel (Basic) 41.0% / 1.3s

Brave 43.0% / 547ms

Perplexity 50.0% / 583ms

300ms 500ms 1s 2s 4s

Latency (ms, log scale)

Pricing

Collection options for your product

Request a quote for your volume

View examples Talk to sales

batch Queued

Scheduled data collection

live Live

Research organic search, maps, news, images, shopping and other supported result types. Use item types to interpret the fields returned by each endpoint.

extended Extended

Confirm the selected route and source

FROM IDEA TO FIRST REQUEST

Find the context. Build the next thing.

rank_group describes a position within a result type, while rank_absolute describes placement across the results page. Keep both when ads or rich features affect visibility.

Read the docs ↗Explore SERP API →

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.