What a SERP API contributes to rank tracking

A SERP API supplies result positions for a specific query and search context. It does not, by itself, run a recurring campaign, maintain keyword history, calculate visibility share or explain why a result moved. Those are application responsibilities.

Collect a repeatable snapshot

Send the same query and market settings each time. For Google web results, a request can look like this:

curl https://api.serqo.io/v1/search \
  -H "x-api-key: $SERP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q":"espresso grinder","engine":"google","type":"web","gl":"us","hl":"en","device":"desktop"}'

Store the exact query, engine, type, gl, hl, device and collection time beside each response. Small changes in query or market create a different measurement and should be tracked separately.

Calculate a page-level position

  1. Read data.results and inspect each item’s type, url, domain and position.
  2. Decide whether the report measures a specific URL, a canonical page or any page on a domain.
  3. Match URLs consistently, including redirects, trailing slashes and canonical paths.
  4. Keep “not found in this response” distinct from a numeric position; the result may be beyond the returned page range.
  5. Store the original snapshot so a changed URL or parsing rule can be reviewed later.

Compare snapshots carefully

Compare only records with the same query, engine, type, country, language and device. Record missing results instead of treating them as position zero. A result page can change between checks, and its layout may contain modules besides organic links. If the report is about organic ranking, filter by the result category your application considers organic rather than mixing maps, news or other modules into one sequence.

Set cadence and history in your system

Your scheduler determines how often to collect. Store timestamps in a consistent timezone and keep raw request inputs with the results. Aggregations such as daily median position, first-seen position or share of voice are your own metric definitions; document how each is calculated so reports remain comparable.

Frequently asked questions

Does Serqo automatically track a keyword over time?

No. Serqo returns a response for each request. Your system schedules checks and stores historical snapshots.

Can search position be compared across countries?

Yes, as separate market observations. Keep gl and hl with each record; do not combine markets into one position series.

Should I use the page’s position as a universal rank?

No. It is the position in one returned snapshot. Define the result type and market before comparing it, and do not assume every person sees the same results page.

Read the Google Search API reference or see how Google SERP requests work.