JavaScript and TypeScript
The runtime most of this tooling is written in.
Measured 2026-W36 · 2026-08-31 · google.com, gl=us
The shape of this topic
Google answers javascript and typescript queries itself more often than it does across the corpus as a whole — 58.6 against 50.8 percent.
Who Google cites here
Who ranks here
Cited more often than ranked
| Domain | Citations | Page-one finishes | Gap |
|---|---|---|---|
| docs.python.org | 15 | 0 | +15 |
| docs.next-js.com | 13 | 0 | +13 |
| aws.amazon.com | 13 | 0 | +13 |
| docs.vite.com | 12 | 0 | +12 |
| developer.mozilla.org | 12 | 0 | +12 |
| docs.deno.dev | 12 | 0 | +12 |
These domains earn a place in Google's own answer more often than they earn a place on page one. Whatever gets a source into an AI Overview, it is not only ranking.
By what the searcher wants
| Intent | Queries | AI Overview |
|---|---|---|
| commercial | 56 | 48.2% |
| informational | 79 | 77.2% |
| comparison | 27 | 40.7% |
| navigational | 12 | 33.3% |
| support | 12 | 50.0% |
Intent is assigned when the query enters the corpus, not inferred afterwards, so this split is stable from week to week.
Result features
Queries in this topic
Measure a topic of your own
Pick your queries, run them on a schedule, keep what comes back. That is the whole method — the endpoint below returns the overview, its citations and the organic results together.
curl --request GET \
--url 'https://serpens.p.rapidapi.com/api/v1/search_ai_overview?q=best%20javascript%20and%20typescript&gl=us&hl=en&format=json' \
--header 'x-rapidapi-host: serpens.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_KEY'
Start measuring
Free tier, no card. Same endpoint that produced every number on this page.