public data vs rate limit etiquette
Measured weekly since 2026-W25. 12 observations.
Measured 2026-W36 · 2026-08-31 · google.com, gl=us
This week
Google is answering this query itself, and 2 of the 6 sources it credits do not appear in the ten results below.
What the AI Overview cites
| Domain | Status | Organic position |
|---|---|---|
| npmjs.com | Cited and ranking | 2 |
| digitalocean.com | Cited and ranking | 3 |
| robots-txt.com | Cited and ranking | 4 |
| stackoverflow.com | Cited, not ranking | — |
| docs.hiq-v-linkedin.com | Cited, not ranking | — |
| hiq-v-linkedin.com | Cited and ranking | 1 |
A domain marked Cited, not ranking is credited in Google's answer while sitting outside the ten organic results. Across the whole corpus that is true of 38.8% of citations.
Organic results
| # | Domain | Title | In the overview | Sitelinks |
|---|---|---|---|---|
| 1 | hiq-v-linkedin.com | hiQ v LinkedIn: public data vs rate limit etiquette | Cited | — |
| 2 | npmjs.com | npmjs: public data vs rate limit etiquette | Cited | 3 |
| 3 | digitalocean.com | A practical guide to public data vs rate limit etiquette | Cited | — |
| 4 | robots-txt.com | robots.txt: public data vs rate limit etiquette | Cited | — |
| 5 | docs.gdpr.com | GDPR: public data vs rate limit etiquette | Not cited | — |
| 6 | gdpr.com | GDPR: public data vs rate limit etiquette | Not cited | — |
| 7 | dev.to | dev: public data vs rate limit etiquette | Not cited | — |
| 8 | pypi.org | A practical guide to public data vs rate limit etiquette | Not cited | — |
Position history
| Domain | W29 | W30 | W31 | W32 | W33 | W34 | W35 | W36 |
|---|---|---|---|---|---|---|---|---|
| hiq-v-linkedin.com | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| npmjs.com | 2 | 2 | 2 | 2 | 3 | 2 | 2 | 2 |
| digitalocean.com | 3 | 3 | 4 | 3 | 2 | 3 | 3 | 3 |
| docs.gdpr.com | 7 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| robots-txt.com | 4 | 4 | 3 | 4 | 4 | 4 | 4 | 4 |
| gdpr.com | 5 | 6 | 7 | 6 | 7 | 6 | 6 | 6 |
A dot means the domain was not on page one that week. This is the part no live SERP checker can show you: it needs someone to have been measuring before you asked.
Features on this page
Filled means Google rendered the block for this query this week. AI Overview, People Also Ask, Related searches, Knowledge panel, Sitelinks — each has its own prevalence across all 4,185 queries.
Reproduce this page
Every figure above comes from one call. This is that call — the same endpoint, the same parameters, run once a week.
curl --request GET \
--url 'https://serpens.p.rapidapi.com/api/v1/search_ai_overview?q=public%20data%20vs%20rate%20limit%20etiquette&gl=us&hl=en&format=json' \
--header 'x-rapidapi-host: serpens.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_KEY'Run it on your own queries
Free tier, no card. The AI Overview endpoint returns the overview, its citations, and the organic results in one response.