Resolve

Google links every result through a google.com/goto redirect, and for a few results per page it holds the destination back for seconds, sometimes longer than a request lasts. SerpKite keeps such a result in its position with link_resolved: false. Its link is then still Google's redirect and its domain is the host Google displayed. meta.unresolved_links counts them.

For batch jobs and monitor runs SerpKite goes on following those redirects after Google's delay, for up to 2 minutes, and they wait for them, so their results rarely carry any. Send such links here to get their destinations; a pending link comes with retry_after seconds to wait. Links held back from a live request are not followed after the response and come back failed: repeat the search, or run it as a batch job, to get them.

Request body

Example request

Authenticate with Authorization: Bearer $SERPKITE_API_KEY (GET requests may pass ?api_key= instead). The official SDKs read SERPKITE_API_KEY for you. See Authentication.

curl https://api.serpkite.com/v1/resolve \
  -H "Authorization: Bearer $SERPKITE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"links":["https://www.google.com/goto?url=CAESgwEB6zsw"]}'

Response fields

Every billed response also carries credit and latency headers (X-Credits-Used, X-Credits-Remaining, X-Request-Id…).

Example response

{
  "results": [
    {
      "link": "https://www.google.com/goto?url=CAESgwEB6zsw",
      "status": "resolved",
      "destination": "https://www.example.com/espresso-guide",
      "domain": "example.com"
    }
  ],
  "meta": {
    "request_id": "01JC8S9V5Q4ZB3H6M2N7P0R1T4",
    "credits_used": 0
  }
}

Errors

Errors use one shape: {"error":{"code","message","request_id"}}. Errors are never billed. Full list in Errors.

Notes

• Not billed; counts toward the key's rate limit.
• It never follows arbitrary redirects: only links SerpKite returned unresolved are known.

Related

• Response meta (unresolved_links)
• Rank tracking guide
• OpenAPI spec