AI Grounding: Every AI Engine Grounds in Live Search — Except Gemini

Ask ChatGPT, Perplexity, or Google’s AI Mode a question today and the answer almost always comes with citations — little numbered links to pages the model read while answering. That’s AI grounding: the engine ran a live search, read real web results, and wrote its answer from them instead of from memory.

It has quietly become the default. But not for everyone. We ran the same measurement across six AI engines, and one of them behaves nothing like the rest.

What AI grounding actually means

AI grounding is the step where a model connects its answer to live web content retrieved at query time. Instead of generating a response purely from the statistical patterns it learned in training, a grounded engine issues a search, pulls back real pages, and composes its answer from them — attaching citations so you can check the sources. Google calls its version Grounding with Google Search and describes it plainly: it “connects the Gemini model to real-time web content” and shows “the sources for the model’s claims.”

It helps to place AI grounding next to the three things people confuse it with:

• Fine-tuning bakes knowledge into the model’s weights before it ships. It’s expensive, slow to update, and frozen the moment training ends — useless for anything that changed yesterday.
• Long context lets you paste a lot of text into a single prompt. Useful, but you have to supply the text, and it doesn’t reach anything the model wasn’t handed.
• RAG (retrieval-augmented generation) retrieves passages from a corpus you control — your docs, your knowledge base — and feeds them to the model at answer time.

Grounding is retrieval where the corpus is the live web. Mechanically it’s RAG whose retriever is a search engine instead of a private vector store: the freshest, broadest source available, with citations built in. That’s why grounding specifically means live search data — freshness, breadth, and verifiability are the whole point. When an AI answer cites a news article from this morning, that’s grounding; fine-tuning could never have known.

The natural question is how consistently AI grounding actually happens across the engines people use. So we measured it.

We measured grounding across six AI engines

cloro monitors how AI engines answer real prompts — it’s what the AI visibility product is built on. That gave us a direct way to quantify grounding: for each answer an engine returned, does it carry at least one live source, and how many?

We pulled a slice of cloro’s monitoring corpus — roughly 2,500 prompts per engine over a 7-day window — and scored every answer. “Grounded” means the response carried ≥1 live source (a cited web page). The prompts are real customer AI-visibility queries: conversational, commercial, and multilingual — the kind of questions people actually put to these tools, not a synthetic benchmark set.

Here’s what five of the six look like.

Engine	Grounded (≥1 live source)	Avg sources per answer
ChatGPT	98.4%	14.1
Google AI Mode	98.2%	9.9
Copilot	97.5%	4.6
Perplexity	94.9%	9.5
Google AI Overview	91.2%	9.1
Gemini	41.1%	3.2

Five engines cluster tightly between 91% and 98%. For ChatGPT, AI Mode, Copilot, and Perplexity, AI grounding isn’t a feature that sometimes fires — it’s how they answer almost every time. This lines up with our earlier finding that ChatGPT uses web search in 80%+ of prompts under clean testing conditions; measured on this corpus, with citation parsing across the full answer, the grounded share is higher still. Google’s AI Overview sits slightly lower at 91.2% — some queries render an Overview that leans more on Google’s own knowledge layer than on cited pages — but it’s still grounded nine times in ten.

Then there’s Gemini.

The Gemini exception

Gemini grounded 41.1% of its answers. On the other roughly 59%, it answered from training memory — no live search, no citations. That’s not a rounding difference from the pack; it’s a different behavior.

The reason is architectural, not accidental. For the Gemini API, grounding is an opt-in tool a developer turns on — Google’s documentation describes enabling the google_search tool, after which “the model handles the entire workflow of searching, processing, and citing information automatically.” When that tool isn’t invoked, Gemini does what a language model does by default: it answers from its parameters. The consumer surface reflects the same tendency — Gemini reaches for live search selectively rather than reflexively. (If you want to see the grounded-vs-ungrounded split up close, we pulled it apart in scraping Gemini, and /gemini/ shows how cloro parses its citations.)

This matters more than a trivia stat. It means that when Gemini answers, there’s a better-than-even chance it’s telling you what it remembered, not what the web currently says. For a factual or fast-moving query, that’s the difference between a citation you can verify and an assertion you can’t. And for anyone doing AI-visibility work, it means live-source strategies — the ones that get you cited — reach Gemini least often of any major engine.

How many sources each engine pulls

AI grounding isn’t binary. An engine that cites one source is grounded; so is one that cites twenty. Depth tells you how much of the live web an answer is actually built on.

ChatGPT is the heaviest reader in the set, pulling 14 sources per answer on average — it fans a query out across many pages before writing. AI Mode, Perplexity, and AI Overview land in a middle band around 9–10 sources. Copilot grounds nearly every time but reads shallower, around 4.6. And Gemini, on the minority of answers where it does ground, cites just 3.2 — both the least likely to ground and the thinnest when it does.

Depth is its own lever for visibility: a 14-source answer has far more citation slots than a 3-source one. We took the citation anatomy apart engine by engine in how each AI engine cites sources — worth reading alongside this if you care about which pages get pulled, not just how many.

Why AI grounding is the whole game for AI visibility

Step back and the pattern is the story: most AI answers are now grounded in live web content. Five of the six engines people use every day run a search before they answer, and they cite between 3 and 14 pages when they do.

That’s precisely why AI visibility — being one of the sources an engine cites — is a real, winnable channel rather than a black box:

• If an engine grounds, its citations are contestable. ChatGPT reading 14 live pages per answer means 14 slots your content could occupy. Grounding is what turns “getting mentioned by AI” from luck into an addressable surface.
• The engine’s grounding behavior is your strategy input. For ChatGPT, AI Mode, Copilot, and Perplexity, live-source optimization pays off on nearly every query. For Gemini, being cited helps only on the ~41% of answers it grounds — reaching it more often means winning where it does search, and accepting that memory covers the rest.
• You can’t optimize what you don’t measure. Which engines ground on your queries, and whose pages they cite, is an empirical question with a different answer for every brand and topic.

That last point is the job cloro does. It runs your prompts across these engines and reports, per query, which grounded and who they cited — the same measurement behind this study, pointed at your footprint. If you’re doing brand or AI search tracking, knowing which engines answer from the live web (and can therefore cite you) versus which answer from memory is the difference between a plan and a guess.

How to ground your own LLM or agent

If you’re building on models rather than monitoring them, grounding is a pattern you implement, and it’s simpler than it sounds:

user question
   → call a search API for the query
   → format the top results as context (title, url, snippet)
   → pass that context to the model
   → model answers, citing those results

Either inject the results into the prompt as context, or expose search as a tool the model calls itself (which is exactly what Gemini’s google_search tool and ChatGPT’s web search do under the hood). The quality of the grounding is only as good as the search layer feeding it — which is where the retriever choice matters.

A Google SERP API like cloro returns the live results page as structured JSON — organic links plus the AI Overview, People Also Ask, and shopping units — so you can ground a model on what Google actually surfaces, features included. If you’d rather the search happen inside the model’s own tool loop, Copilot and Bing-based grounding and Anthropic’s Claude both wire a web index in directly; we measured how close one of those indexes sits to Google in Brave Search API vs Google. Pick the retriever whose output your product needs, then feed it in — that’s grounding.

Methodology and honest caveats

A few things to hold this data honestly:

• It’s cloro’s own corpus, presented with methodology. These are first-party measurements from cloro’s AI-visibility monitoring — real customer prompts, not a public benchmark. Numbers are within-engine and directional: they describe how each engine behaved on this prompt mix, not a universal census of all AI answers.
• The prompt mix has a shape. The corpus skews conversational and commercial, and spans multiple languages. A different query set — pure factual lookups, or code questions — would move the absolute grounding rates. The ordering (five engines high, Gemini low) is the robust finding.
• AI Overview is measured where it rendered. The 91.2% figure is computed only on captures where an AI Overview actually appeared, with sources read from the Overview’s own block (result.aioverview), not the surrounding organic SERP. Queries that render no Overview aren’t counted for that row.
• “Grounded” is a floor, not a grade. It means ≥1 live source was present. It doesn’t judge whether the source was good, whether the model used it faithfully, or whether the citation was relevant — only that the engine reached for the live web at all.

Within those bounds, the headline is stable and striking: grounding is now the norm across the AI engines people use — and Gemini is the one that most often answers from memory instead. If you’re deciding where to invest in being seen by AI, that map of who searches and who remembers is where to start.

Want to know which engines ground on your queries — and whose pages they cite? See how cloro’s web search and AI visibility monitoring works.