Google index checker API

Endpoints, request bodies and response fields of the SpeedyIndex bulk Google index checker API, with notes for teams migrating from Custom Search JSON API.

The SpeedyIndex checker API verifies whether URLs are present in Google’s index. It is the programmatic side of the bulk Google index checker. Teams migrating off the Google Custom Search JSON API (retired on January 1, 2027) use it as a drop-in for site:-based checks; the migration walkthrough covers the code changes, and the background on the shutdown covers why.

Base URL and authentication

Item	Value
Base URL	https://app.speedyindex.com
Auth header	Authorization: <API key>
Content type	application/json
Key issued in	app.speedyindex.com or the Telegram bot

The checker draws on its own balance, separate from indexing tokens. Current per-URL pricing is on the checker page.

Endpoints

Create a check task

POST /v2/task/google/checker/create

Request

{
  "title": "backlinks batch 2026-09",
  "urls": ["https://example.com/page-1", "https://example.com/page-2"]
}

Limit: 10,000 URLs per request. Split larger lists into several tasks.

Task status

POST /v2/task/google/checker/status with body { "task_id": "..." }. Processing is asynchronous; poll this endpoint rather than expecting the report immediately.

Full report

POST /v2/task/google/checker/fullreport with body { "task_id": "..." }. The response carries two arrays: indexed_links and unindexed_links.

Verify

A successful run ends with code: 0 on every call and a report where indexed_links plus unindexed_links equals the number of URLs submitted. A non-zero code means the request was rejected (bad key, empty list, over the limit); the message field says which.

Keep the API key in an environment variable or secret store. Any client holding the key can spend the account balance.

Related

• Official API documentation
• Google Custom Search JSON API overview — the API being retired