Characterizing Web Search by Conversational LLM Agents

From the decision to search, through how queries are built and what the search engine hands back, to which of it actually survives into the final, cited response — traced across four commercial platforms.

ChatGPT logo ChatGPT
OpenAI
Claude logo Claude
Anthropic
Grok logo Grok
xAI
DeepSeek logo DeepSeek
DeepSeek‑AI
4
platforms studied — ChatGPT, Claude, Grok, DeepSeek
613
users donated their real chat histories (invivo)
171,264
conversations analyzed across all platforms
1,000
prompts replayed identically across APIs (invitro)
Three headline results

Agents disagree about when to search — and searching isn't always the win it looks like.

01
Decisions

Agents are good at knowing when not to search.

Web‑calling rates range from 14% to 83% of identical prompts across models. Prompts an agent answers from parametric knowledge alone score higher on quality than prompts it sends to search — search helps, but doesn't fully close the gap.

02
Querying & results

Every platform queries differently — and their search engines play favorites.

Some agents fan out several queries per turn; others iterate one query deeply. The search engines behind them return few results (often <15) drawn from a narrow, platform‑specific set of preferred domains.

03
Grounding

Not every claim traces back to a citation — even when it could.

Cited URLs skew toward popular, high‑Tranco‑rank domains. A non‑trivial share of claims is supported only by uncited search results, and claims with no retrieval support at all score the lowest on factuality.

The life cycle of agentic search

One prompt, four stages, wildly different behavior per platform.

The paper follows a single user turn through four stages — this page is organized the same way. Every arrow below is a place where ChatGPT, Claude, Grok, and DeepSeek measurably part ways.

STAGE 1

User Prompt

A verbose, conversational request — often with prior turns of context behind it.

STAGE 2

Web‑Search Decision

The model judges whether its parametric knowledge is enough, or whether to reach for the web.

STAGE 3

Query Formulation

The prompt is compressed into one or more web queries, fanned out and/or refined across iterations.

STAGE 4

Response Generation

Search results are synthesized with parametric knowledge into a cited, grounded answer.

Figure 1. The life cycle of agentic Web search — the same four‑stage frame the paper's Figure 2 uses to trace a prompt from decision through to a grounded response. Every arrow above is a point where ChatGPT, Claude, Grok, and DeepSeek measurably diverge, charted in the sections below.

chatgpt logoChatGPT claude logoClaude grok logoGrok deepseek logoDeepSeek — the same four marks and colors recur in every chart below
Stage 2 · invitro, same 1,000 prompts

Same prompts, same knowledge cutoff window — four very different call rates.

Each model saw the identical 1,000 sanitized prompts through its own API. GPT‑5.3‑chat searches for 1 in 7; Claude Sonnet 4.6 searches for more than 4 in 5.

Share of prompts that triggered a web search
invitro replay · 1,000 identical prompts per model
14.0%
chatgpt logoGPT‑5.3‑chat
82.5%
claude logoClaude Sonnet 4.6
76.6%
grok logoGrok‑4.3
58.4%
deepseek logoDeepSeek‑v4‑flash

Figure 2. Share of the same 1,000 invitro prompts that triggered a Web search, per platform. GPT‑5.3‑chat searches for roughly 1 in 7; Claude Sonnet 4.6 searches for more than 4 in 5 — nearly a six‑fold spread on identical prompts.

Harness instructions vs. the model's own instinct
Web‑search calls out of 1,000 prompts, when a GPT model is run under another GPT model's search instructions (a heat‑mapped matrix; ringed cells = a model under its own native harness)
Replay model ↓ / Developer prompt →GPT‑5.3‑chatGPT‑4.1‑minio4‑mini
o4‑mini 478 640 634
GPT‑4.1‑mini 407 417 440
GPT‑5.3‑chat 140 145 169

Swapping in another model's harness moves the needle — o4‑mini drops from 634 to 478 calls under GPT‑5.3‑chat's conservative instructions — but never enough to close the gap. The model's own disposition still dominates the decision.

Figure 3. Web‑search calls out of 1,000 prompts when a GPT model is replayed under another GPT model's own developer‑prompt search instructions (ringed cells = a model under its native harness). Harness swaps shift the rate but never close the gap to the model's native behavior.

Reading this carefully: more search isn't automatically better search. For prompts an agent chose to answer without search, response quality was consistently higher than for prompts it sent to search — across every platform and every metric (factuality, completeness, relevance). Web search closes part of the gap for prompts that genuinely need it, but for Claude specifically the paper finds only mixed effects despite its high call rate.
Stage 3 · invivo, real user traffic

How a prompt becomes a query — and where that query goes looking.

Claude fires one deep, iteratively‑refined query per turn. Grok fans out the most queries and racks up the most search results. Every engine returns far fewer pages than a plain Google search would.

Average web queries issued per user prompt
invivo · real conversations, when search was invoked
1.15
chatgpt logoChatGPT
1.80
claude logoClaude
4.55
grok logoGrok
2.63
deepseek logoDeepSeek

ChatGPT, Grok, and DeepSeek issue parallel fan‑out queries within a turn; Claude issues one query per turn and instead goes deeper across more iterations — same query budget, opposite strategy.

Figure 4. Average number of Web queries issued per user prompt when search was invoked (invivo). Grok fans out the most queries per turn — nearly 4× ChatGPT's rate — while Claude deliberately issues one query and iterates instead.

Search results returned per user prompt
invivo · average number of URLs surfaced by the platform's own search engine
chatgpt logoChatGPT
28.4
claude logoClaude
16.6
grok logoGrok
40.7
deepseek logoDeepSeek
14.4

For comparison, a typical open web search returns far more than 40 results — every one of these platform‑built engines is working from a deliberately narrow slate.

Figure 5. Average number of search‑result URLs surfaced per user prompt, per platform (invivo). Grok's engine returns the most (40.7); DeepSeek's the fewest (14.4) — a roughly 3× spread across platforms working from the same open web.

Where the search engines keep going back
Top domains by share of returned search‑result URLs (invivo) — same domain, wildly different rank across platforms
ChatGPT logoChatGPT
  1. reddit.com
  2. wikipedia.org
  3. youtube.com
  4. facebook.com
  5. amazon.com
  6. instagram.com
Claude logoClaude
  1. amazon.com
  2. github.com
  3. wikipedia.org
  4. learn.microsoft.com
  5. dmv.ca.gov
  6. medium.com
Grok logoGrok
  1. youtube.com
  2. reddit.com
  3. facebook.com
  4. tiktok.com
  5. instagram.com
  6. quora.com
DeepSeek logoDeepSeek
  1. youtube.com
  2. wikipedia.org
  3. reddit.com
  4. github.com
  5. facebook.com
  6. tiktok.com

reddit.com and youtube.com dominate ChatGPT, Grok, and DeepSeek results — and are completely absent from Claude's top domains, which instead lean toward developer and reference sites (github.com, learn.microsoft.com, stackoverflow.com).

ChatGPT logoChatGPT — top‑10 domain concentration
21.3% invivo
47.8% of results in the invitro replay
Grok logoGrok — top‑10 domain concentration
32.3% invivo
29.0% of results in the invitro replay

Figure 6. Top domains by share of returned search‑result URLs, per platform (invivo), with top‑10 domain concentration for ChatGPT and Grok under both real usage and controlled replay. reddit.com and youtube.com dominate three of the four platforms and are entirely absent from Claude's list.

Stage 4 · citing and grounding the response

What a claim is actually standing on.

Every response claim was checked against the URLs it cited, the URLs the search engine returned but the model chose not to cite, and — failing both — attributed to the model's own parametric memory.

Citation rate — share of returned search URLs that get cited
invivo · cited search‑result URLs ÷ all returned search‑result URLs
13.3%
chatgpt logoChatGPT
19.9%
claude logoClaude
1.8%
grok logoGrok
34.1%
deepseek logoDeepSeek

Grok returns the most search results of any platform (page above) yet cites almost none of them — a strikingly low 1.8% citation rate, versus 34.1% for DeepSeek.

Figure 7. Citation rate — the share of returned search‑result URLs that actually get cited in the response, per platform (invivo). Grok's 1.8% is an outlier against every other platform's double‑digit rate.

What actually grounds a response claim
invivo · share of response claims traced to each evidentiary source (rows sum to 100%)
Associated citation Other cited URL in response Uncited search result Ungrounded / parametric
chatgpt logoChatGPT
37.3%
25.1%
15.4%
22.1%
claude logoClaude
37.0%
16.3%
25.2%
21.5%
grok logoGrok
52.7%
29.7%
deepseek logoDeepSeek
33.6%
15.8%
45.6%
Show exact values as a table
PlatformAssociated citationOther cited URLUncited search resultUngrounded / parametric
ChatGPT37.3%25.1%15.4%22.1%
Claude37.0%16.3%25.2%21.5%
Grok8.6%9.0%52.7%29.7%
DeepSeek33.6%15.8%5.0%45.6%

Grok's pattern stands out: over half of its grounded claims (52.7%) trace back to search results it retrieved but never cited — consistent with its 1.8% citation rate above. Ungrounded claims, wherever they occur, consistently score the lowest of any source on factuality in the paper's evaluation.

Figure 8. Where each response claim's supporting evidence actually comes from, per platform (invivo) — an associated citation, another cited URL elsewhere in the response, an uncited search result, or nothing retrieved at all. Grok's claims lean overwhelmingly on uncited search results; DeepSeek's lean overwhelmingly on unsupported, parametric knowledge.

Two complementary datasets

invivo real usage, invitro controlled replay.

invivo traces come from GDPR data donations by real platform users — nothing here was prompted for the study. invitro replays the same 1,000 sanitized prompts through each provider's API for an apples‑to‑apples comparison.

invivo — donated conversation traces
PlatformUsersConversationsTurnsTurns with web search
chatgpt logoChatGPT (OpenAI)310143,730690,75442,273
claude logoClaude (Anthropic)1029,26764,3541,696
grok logoGrok (xAI)1009,00553,8403,004
deepseek logoDeepSeek1019,26236,0201,730
invitro — models replayed via API
CompanyModelAPIReleaseKnowledge cutoff
chatgpt logoOpenAIGPT‑5.3‑chatResponses APIMar 2026Aug 2025
claude logoAnthropicClaude Sonnet 4.6Messages APIFeb 2026Aug 2025
grok logoxAIGrok‑4.3OpenAI‑compatible Responses APIMay 2026Dec 2025
deepseek logoDeepSeekDeepSeek‑v4‑flashAnthropic‑compatible Messages APIApr 2026Unknown
Citing this work

BibTeX

Available as an arXiv preprint.

@misc{amani2026characterizingwebsearchconversational,
      title={Characterizing Web Search by Conversational LLM Agents: From Search Decisions and Strategies to Results and Responses},
      author={Mahsa Amani and Seungeon Lee and Abhisek Dash and Asmaa El Fraihi and Yunah Jang and Elisabeth Kirsten and Qinyuan Wu and Krishna P. Gummadi and Manish Gupta and Abhilasha Ravichander and Muhammad Bilal Zafar and Soumi Das},
      year={2026},
      eprint={2609.19244},
      archivePrefix={arXiv},
      primaryClass={cs.AI},
      url={https://arxiv.org/abs/2609.19244},
}