Report
Which blocks Google renders
Prevalence of every result feature across the corpus.
Measured 2026-W36 · 2026-08-31 · google.com, gl=us
2026-W36
Across the corpus
These five shares are the answer to the question every SERP API buyer asks first: how often will I actually get the block I am paying to parse.
Topics
By topic
| Feature | Market | JavaScript | Proxies | Compliance | Localisation | Retrieval-augmented |
|---|---|---|---|---|---|---|
| AI Overview | 60% | 59% | 57% | 57% | 56% | 55% |
| People Also Ask | 69% | 67% | 67% | 66% | 65% | 65% |
| Related searches | 83% | 82% | 81% | 81% | 80% | 80% |
| Knowledge panel | 28% | 28% | 27% | 26% | 26% | 26% |
| Sitelinks | 53% | 52% | 48% | 48% | 48% | 48% |
Method
The measurement behind it
A fixed corpus of 4,185 queries, run once a week from the United States through one endpoint, stored and never re-fetched. 82,620 observations across 12 weeks so far. The method is written out in full on how we measure.
curl --request GET \
--url 'https://serpens.p.rapidapi.com/api/v1/search_ai_overview?q=best%20search%20apis&gl=us&hl=en&format=json' \
--header 'x-rapidapi-host: serpens.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_KEY'Reproduce any figure here
Free tier, no card. Same endpoint, same parameters — the corpus is the only thing you would need to supply.