Domain
docs.json-rpc.com
How docs.json-rpc.com performs across a fixed corpus of 4,185 queries, measured every week.
Measured 2026-W36 · 2026-08-31 · google.com, gl=us
2026-W36
Visibility
Queries ranked
35
of 4,185 measured
Average position
4.7
best seen: 1
Top three finishes
13
5 at position one
AI Overview citations
12
6 without ranking
Week on week
-10%
vs 2026-W35
Google credits docs.json-rpc.com in its own answer on 6 queries where the domain does not appear in the ten organic results. That gap is the whole argument for measuring citations separately from rankings.
Topics
Where it shows up
Citations
Queries where Google cites it
| Query | Status | Topic |
|---|---|---|
| how to use OpenAPI | Also ranking | API design |
| REST python | Also ranking | API design |
| how to use REST | Cited, not ranking | API design |
| gRPC rate limits | Cited, not ranking | API design |
| JSON-RPC example | Cited, not ranking | API design |
| what is JSON-RPC | Also ranking | API design |
| idempotency keys api | Also ranking | API design |
| API versioning rate limits | Also ranking | API design |
| HTTP 429 alternatives | Cited, not ranking | API design |
| HTTP 429 review | Also ranking | API design |
| gRPC vs idempotency keys | Cited, not ranking | API design |
| exponential backoff vs API versioning | Cited, not ranking | API design |
Rankings
Queries where it ranks
API
Track any domain yourself
This page is an aggregate of ordinary search calls — one per query, once a week. Nothing here needs a special endpoint or a rank-tracking contract.
curl --request GET \
--url 'https://serpens.p.rapidapi.com/api/v1/search?q=site%3Adocs.json-rpc.com&gl=us&hl=en&format=json' \
--header 'x-rapidapi-host: serpens.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_KEY'
Build this for your own domain
Free tier, no card. One endpoint returns organic results, the AI Overview and its citations together, so ranking and citation come out of the same call.