Gemini answers live-web questions without searching and without saying so, tests show

Ask Google's Gemini for something that plainly depends on current information — today's weather, a price right now, whether a shop is open — and there is a fair chance it responds immediately, in its usual confident tone, without ever consulting the web. According to an analysis published on dev.to, this is not a random glitch: Google runs a routing step before the model answers, deciding turn by turn whether it receives its web-search tool at all. On many turns the tool is either withheld entirely or paired with a hidden instruction not to use it, and nothing in the resulting reply tells the user which happened.

What users have documented

The complaints are filed on Google's own ground. Gemini's official help community carries threads with titles such as "Persistent Web Search Failure on Gemini Android and Web" and "Gemini refuses to use search tool", where users describe current-information questions being met with stale answers and no visible search.

The cleanest test, per the dev.to write-up, came from a user on r/GeminiAI in late August. Because Gemini has no dedicated weather feed — current conditions arrive through the same search tool as everything else — weather makes a good probe. The result: requesting weather in English triggered a search; the identical request in Finnish, using the single word "sää", blocked search every time, on the same account with the same settings. The model's visible reasoning reportedly shows it concluding it ought to check current conditions, then noting it has not been given the tool. The dev.to author points out that the behaviour has been reproduced in other languages and has survived app updates through August 2026, with no official explanation from Google and help threads that mostly end without a fix.

The hidden instruction

The behaviour also appears in a widely circulated collection of leaked system prompts — a public, heavily starred repository that has drawn mainstream press coverage. One Gemini prompt contains the line, verbatim: "Do NOT issue search queries to the google search tool for this prompt." The dev.to author cautions that Google's internal prompts cannot be independently audited, while noting that vendors have historically confirmed such extractions as genuine.

Two observations lend the leak weight. Gemini has reportedly been caught repeating that exact line to users, and on some turns the model receives contradictory directives at once — the search tool, an instruction to always use it, and an instruction not to issue queries — and has been watched trying to referee the conflict in its own chain of thought, at one point speculating about prompt injection. Separately, the same r/GeminiAI teardown claims an unshipped "Search" toggle sits switched-off in the app's code: a user-facing way to force a search that Google has built but not released. The dev.to author flags this as one user's finding rather than a confirmed feature.

The case for the classifier

There is a real engineering argument on Google's side. Handing a large model a live search tool on every turn is expensive and slow, and prompts like "explain recursion" genuinely do not need the web. A classifier deciding when search is warranted is standard practice among assistants, and the dev.to author explicitly declines to claim Google is degrading the product to save money. The likeliest explanation offered is mundane: routing tuned under cost and latency pressure, skipping search more often than power users would like.

Why the silence is the real problem

Conceding all of that, the dev.to analysis argues, makes the criticism sharper rather than softer. Three things compound. There is no signal: an answer from memory and a freshly searched one look identical, delivered in the same confident register. There is no control: the available workarounds — nagging the model to use the search tool, or leaving a standing instruction in Saved Info — fail on turns where the tool was never handed over. And the worst case is not a refusal but a fluent, out-of-date answer delivered with complete assurance, which users have no way to catch on their own.

Why it matters

For anyone relying on Gemini for time-sensitive facts, this is a practical reliability problem: you cannot tell a checked answer from an unchecked one, so you cannot calibrate trust. At bottom it is a transparency issue presented as a search issue — the assistant quietly declines to do the ordinary thing asked, and declines to mention the decline. Until Google makes grounding visible by default or ships the toggle that reportedly already exists in the app's code, the safe assumption is that a live-data answer from Gemini may come from stale training data, and independent verification is not optional.