The Google AI Overview API trusted by the top brands

The AI Overview block (often abbreviated AIO) renders at position 0 above organic results, marked by a small sparkle/asterisk icon and the words "AI Overview" or "Search Labs · AI Overview" depending on the rollout phase. The logo is Google's standard four-color sparkle (blue, red, yellow, green dots arranged in an asterisk pattern). When scraping programmatically, you don't need to identify it visually — pass `include: {"aioverview": {"markdown": true}}` and the API returns the parsed block in `result.aioverview` if present, or omits the field if AI Overview didn't render for that query. The AI Overview response schema documents every field it can contain — text, sources, citation pills, videos, and inline ads.

Google has never shipped one. The Search SERP API returns organic results without the AI Overview block; Vertex AI gives you Gemini without the Google index. AI Overview is a rendered UI feature, not an API surface. To monitor it you have to render the SERP and parse it, which is what cloro does. Rolling that parsed block into a brand-level score across engines is the AI visibility tracking use case.

Yes, and the share is growing. AI Overview increasingly embeds YouTube videos directly in the answer (with platform, duration, thumbnail) for how-to and product queries, plus sponsored shopping ads (price, store, domain) for commercial intent. cloro returns both as `aioverview.videos` and `aioverview.ads`. If your competitive set is running Performance Max or YouTube ads, this is the surface that places them.

Yes. The same `/v1/monitor/google` request returns organic results, AI Overview (if triggered), People Also Ask, related searches, and sponsored results in one payload. AI Overview citations correlate strongly with organic top-3, so capturing both lets you measure that relationship directly. Grounding an AI app or agent on that SERP instead of tracking it? The same endpoint powers cloro's web search API.

Substantially. We see roughly 30–50% trigger-rate divergence between US and EU on the same prompt set. Some EU regions roll out AI Overview slower or scope it tighter under DMA constraints. Pass `country` per request to capture the regional variation.

Each request runs against Google live with typical latency of 30–60 seconds end-to-end and no caching layer. Citations reflect Google's current SERP pass, not yesterday's snapshot.

Use the async task API: `POST /v1/async/task` with `taskType: "GOOGLE"` and the monitor-google payload, including `aioverview` in the include block. Submit a batch, receive results via webhook. This is the right pattern when you're sampling thousands of prompts per day across multiple countries.

DIY Google SERP scraping is the hardest sustained anti-automation fight on the public web. Realistic in-house cost for AI-Overview-aware monitoring at production volume is $5–10k/month before engineering time, and the success rate is fragile. cloro's Hobby plan ($100/month) covers the same workload with managed reliability.

Different layer. Ahrefs, Authoritas, and BrightEdge are dashboard products for SEO marketers tracking keyword visibility inside AI Overviews. cloro is the API and data layer underneath: structured JSON for every AI Overview citation, source, video, and inline ad, returned per request across 250+ locations. Teams build their own dashboards, alerting, or competitive workflows on top of cloro's feed. If you want a turnkey marketer UI, use one of those tools. If you want the raw structured data feed to integrate into your stack or product, use cloro.