speedyindex — Python client for the SpeedyIndex API
speedyindex is a small, dependency-free Python client and command-line tool for SpeedyIndex, a service for link indexing, Google, Bing and Yandex index checking and Google rank tracking. It wraps the SpeedyIndex API v2, so you can check whether URLs are indexed, submit links for indexing, track keyword positions and react to webhooks from scripts, cron jobs or CI.
- Standard library only (
urllib), Python 3.8+ - Index checks for Google, Bing and Yandex, with reports that list indexed and unindexed URLs
- Link indexing tasks for Google and Yandex, single-URL submission and drip-feed
- Rank Tracker: projects, keywords, regions, checks, positions, history, AI Overview citations, CSV export
- Webhooks: verify
X-SpeedyIndex-Signatureand parsecheck.finishedevents - Backlink checks: find links to your domains on donor pages
speedyindexCLI for quick jobs from the shell
Install
pip install speedyindex
API key
Every request needs an API key from your SpeedyIndex dashboard or the SpeedyIndex Telegram bot settings. The client reads it from the SPEEDYINDEX_API_KEY environment variable:
export SPEEDYINDEX_API_KEY="your-key"
Keep the key out of source code and commit history; use environment variables or your CI secret store.
Index checks and indexing
from speedyindex import SpeedyIndex
si = SpeedyIndex() # reads SPEEDYINDEX_API_KEY
# Which URLs are in Google's index?
task = si.create_task(
["https://example.com/", "https://example.com/blog/post-1"],
engine="google", task_type="checker", title="blog check",
)
task_id = task["task_id"]
print(si.task_status([task_id], engine="google", task_type="checker"))
report = si.report(task_id, engine="google", task_type="checker")
print(report["unindexed_links"]) # plain URL lists
full = si.full_report(task_id, engine="google", task_type="checker")
# indexed_links: [{url, title}] - title as shown in the search results
# unindexed_links: [{url, error_code}] - -1: noindex found, 0: no error, otherwise the HTTP status
Bing supports checker tasks only. Submit links for indexing, spread over several days (drip feed is for Google indexing tasks):
si.create_task(urls, engine="google", task_type="indexer", drip_feed=True, drip_feed_days=7)
si.index_url("https://example.com/new-page", engine="yandex")
Rank Tracker
Projects created through the API are the same projects you see in the dashboard.
rt = si.rank
loc = rt.locations("new york", gl="us")[0]
project = rt.create_project(
"example.com",
regions=[{"location": loc["canonical_name"], "gl": loc["country_code"]}],
keywords=["pizza delivery", "best pizza near me"],
depth=30,
ref="my-project-1", # safe to repeat after a timeout
)["project"]
check = rt.run_check(project["id"])
check = rt.wait(check["id"]) # polls every 30 s; or use a webhook
for row in rt.positions(project["id"], check_id=check["id"]):
print(row["q"], row["position"] if row["found"] else "not found")
open("positions.csv", "wb").write(rt.export(project["id"]))
Also available: update_project, bulk, add_region, add_keywords, replace_keywords, edit_keywords, keyword_history, trend, keyword_in_check (top 10 and AI Overview: present, cited, sources), cost, limits, usage. Lists are iterators that follow next_cursor for you.
Webhooks
Set an account webhook with rt.set_webhook("https://hooks.example.com/speedyindex"); the first answer contains the signing secret. Verify each delivery over the raw body before parsing it:
from speedyindex import parse_event
# Flask example
@app.post("/speedyindex")
def hook():
event = parse_event(request.get_data(), request.headers.get("X-SpeedyIndex-Signature"),
os.environ["SPEEDYINDEX_WEBHOOK_SECRET"])
# event["event"]: check.finished / check.failed / check.skipped
# a delivery may repeat: process each event["event_id"] once
return "", 200
During secret rotation the header carries two signatures; either one is accepted.
Command line
speedyindex balance
speedyindex check urls.txt --engine google --title "weekly check"
speedyindex check urls.txt --engine bing
speedyindex index urls.txt --engine google --drip-feed-days 5
speedyindex status 65f8c7315752853b9171860a --type checker
speedyindex report 65f8c7315752853b9171860a --type checker --unindexed > not-indexed.txt
speedyindex report 65f8c7315752853b9171860a --type checker --full > report.json
speedyindex tasks --engine google --type indexer
speedyindex rank locations "new york" --gl us
speedyindex rank create example.com --location "New York,New York,United States" --gl us --keywords kw.txt
speedyindex rank check PROJECT_ID --wait
speedyindex rank positions PROJECT_ID --changed-only
speedyindex rank export PROJECT_ID --format csv > positions.csv
speedyindex backlinks donors.txt --target mysite.com
Input files hold one item per line; empty lines and lines starting with # are skipped. Use - to read from stdin.
Errors and limits
Errors raise SpeedyIndexError with .code (API code), .status (HTTP status), .error (machine-readable name from the Rank Tracker API, e.g. rows_expired) and .retry_after on HTTP 429. The client checks the documented request limits before sending:
| Rule | Value |
|---|---|
| URLs per task | up to 10,000 |
| Task IDs per status request | up to 1,000 |
| Drip-feed days | 2–30, at least as many URLs as days, Google indexing only |
| Bing | checker tasks only |
Google indexer tasks |
sent with pay_per_indexed: true (the mode the API accepts now) |
Tips before you run an index check
- Clean the list first: remove UTM parameters, fragments and duplicates.
- Check status codes and
noindexbefore submitting: a 404 or anoindexpage will not be indexed whatever you do. - Google's own URL Inspection tool remains the reference for a single URL on a site you own.
License
MIT
Metadata
Release files for speedyindex 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| speedyindex-0.2.0.tar.gz | 14.3 kB | With provenance | Details for speedyindex-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| speedyindex-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for speedyindex-0.2.0-py3-none-any.whl |
Total release size: 29.7 kB
Release files / speedyindex-0.2.0.tar.gz
| Download URL | speedyindex-0.2.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a4a91621b6de0511cac0d56aaed497617a1a248b60aa2ff3abc26960199520c
|
|
BLAKE2b-256 checksum How to use checksums |
fe7918e7bd1908bd134fec25585f35db2a9dc36efb1008f822d6fe665e7d54a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logRelease files / speedyindex-0.2.0-py3-none-any.whl
| Download URL | speedyindex-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a446badcc5474281964b24a95c8bb371b8f739208b4d8f62408096ffd391491f
|
|
BLAKE2b-256 checksum How to use checksums |
cb428920562ccf27ec74907d5b644d3432183d3e43b5edc847bf49f090926a4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logSecurity for speedyindex 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for speedyindex-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.