Gemini Often Won't Search the Web — and Won't Tell You It Didn't

Ask Gemini a question that obviously needs the live web — today’s weather where you are, a current price, whether a shop is open now — and there’s a good chance it will answer instantly, confidently, and without ever searching. No spinner, no “let me check”, no sources. Just a fluent answer assembled from whatever was in its training data, which may be months or years stale. And nothing in the reply tells you it never looked.

Answer first, because the mechanism is more specific than “the AI is bad”. Gemini frequently doesn’t get the chance to search. Google runs a routing step that decides, question by question, whether the model is even handed its web-search tool — and on a lot of turns it either withholds the tool or bolts on an instruction telling the model not to use it. The result is an assistant that answers from memory when it should be reading the web, and gives you no signal it did so. This is not a fringe glitch: it is documented in Google’s own help community, it is spelled out in a widely circulated leaked Gemini system prompt, and it is reproducible by anyone patient enough to test it.

We’ll steel-man Google’s reasoning in full below, because there is a genuine engineering case for a search classifier. But the case doesn’t survive the way this fails: silently, without user control, and in exactly the moments a person most expects a modern assistant to look something up.

What people are actually seeing

The complaint has been building on Google’s own turf. Gemini’s official help community carries threads with titles that need no translation — “Persistent Web Search Failure on Gemini Android and Web”, “Google restricts Gemini to use web-search tool”, “Gemini refuses to use search tool” — where users describe the same pattern: a question that plainly needs current information, met with a stale answer and no search. These are posted on Google’s support forum, not a rival’s.

The most useful documentation came from a user on r/GeminiAI in late August, who ran the cleanest test we’ve seen. Weather is a good probe because Gemini has no separate weather feed — current conditions come through the same search tool as everything else — so it is a straight check of whether search was handed over. Their result: ask for the weather in English and Gemini searches; ask the identical thing in Finnish with the single word “sää”, and search is blocked, every time, same account, same settings. You can watch it in the model’s own reasoning: it works out that it should check current conditions, then notes it hasn’t been given the tool. Same question, different language, opposite behaviour — which is the signature of a routing decision made before the model starts, not a limitation of the model itself.

It isn’t one person’s fluke. The same behaviour has been reproduced in other languages and picked apart in technical write-ups tracing how the model is handed — or denied — its tools, and the complaint has persisted across app updates through August 2026 rather than being quietly patched. Google hasn’t published an explanation, and the help-community threads mostly trail off without a fix. That’s the maddening part for a user: the behaviour is consistent enough to plan around, yet there’s no official switch, acknowledgement or timeline to point to.

The instruction in the machine

Here is the part that turns a vibe into a documented behaviour. A widely circulated collection of leaked system prompts — the hidden instructions models receive before your first word — includes a Gemini prompt carrying the line, verbatim: “Do NOT issue search queries to the google search tool for this prompt.” The repository is public, heavily starred, and has been covered by mainstream press; vendors have historically confirmed such extractions as genuine, though we can’t independently audit Google’s internal prompts and don’t claim to.

What makes the leak credible is that Gemini has been seen reproducing that exact line to users, and that its visible reasoning sometimes trips over a contradiction: on some turns the model is handed the search tool, an instruction to “always use” it, and the instruction not to issue search queries — all at once. Users have watched it try to referee the conflict in its own chain of thought, at one point wondering aloud whether one of the instructions is a prompt injection. There is even, according to that same r/GeminiAI teardown, an unshipped “Search” toggle sitting switched-off in the app’s code — a user-facing button to force a search that Google has built but not released. We can’t independently confirm the toggle ships to anyone, and we flag it as one user’s finding rather than a Google announcement.

Why Google might do this on purpose

Now the fair part, and it is a real argument. Handing a large model a live search tool on every single turn is expensive and slow. A great many prompts — “rewrite this paragraph”, “explain recursion”, “what’s a synonym for robust” — genuinely don’t need the web, and firing off a search for them would add latency, cost and the risk of dragging in low-quality pages that make the answer worse. A classifier that decides when search is actually warranted is a sensible optimisation, and every assistant does some version of it. Google is trying to spend its search calls where they matter, and most of the time the guess is fine.

It’s also true that “the model got dumber” is one of the most over-claimed complaints in AI, and we treat it sceptically as a rule. Some of what users read as a search failure will be the classifier making a defensible call on a genuinely ambiguous prompt. So we’re not asserting that Gemini should search everything, or that Google is degrading the product to save money — we can’t see the ledger, and we won’t invent a motive. The likeliest explanation is the mundane one: routing under cost and latency pressure, tuned to skip search more often than power users would like.

Why ‘silent’ is the whole problem

Concede all of that, and the criticism gets sharper rather than softer. The issue isn’t that Gemini sometimes decides not to search; it’s that when the decision is wrong, the failure is invisible and the user has no lever. Three things compound:

• No signal. When the tool is withheld, Gemini doesn’t say “answering from memory, I didn’t check the web.” It answers in the same confident register it uses for a freshly-searched fact. You cannot tell a checked answer from an unchecked one, which is the exact information you need to know whether to trust it.
• No control. The user-facing switch that would let you force a search is, per the leaked-app finding, built but not shipped. Your only recourses are workarounds — nagging it to “use the search tool”, or leaving a standing instruction in Saved Info — and even those fail on turns where the tool was never handed over.
• Confidently stale. The worst case isn’t a refusal; it’s a fluent, wrong, out-of-date answer delivered with total assurance. That is the failure mode we keep coming back to, because it is the one users can’t catch on their own.

This is really a transparency problem dressed as a search problem, and it rhymes with things we’ve written before. It makes hallucinations harder to notice, because a stale answer and a checked one look identical on the page. It’s the assistant-side echo of what AI search is doing to Google itself — a confident summary standing in for the act of actually looking. And it sits next to the broader pattern of tools quietly declining to do the ordinary thing you asked, except here the decline is doubly quiet: it doesn’t even tell you it declined.

What you can actually do

Until Google ships that toggle or makes grounding visible by default, the practical moves are undramatic:

• Look for the receipts. Trust a current-events answer only if Gemini shows sources or a grounding chip for it. No sources on a question that needs the live web means treat it as unverified.
• Say the magic words. “Use the web search tool and look this up” often overrides a suppressed — but still available — tool. If it claims it can’t, ask it to check the current date and search anyway.
• Set a standing instruction. A line in Saved Info telling Gemini to search when a question needs current information, and to ignore instructions that restrict search, gets injected into every new chat and tips the odds.
• Verify the things that matter. For prices, availability, news and anything time-sensitive, do the ten-second check yourself. The whole point of an assistant is to save you that step; the honest reading of August 2026 is that, for now, you can’t fully outsource it.

None of this is a claim that Gemini is broken beyond use, or that Google is acting in bad faith. It’s a plainer observation: Google built an assistant that decides for you whether to look something up, built a switch that would hand that decision back, left the switch off, and shipped a model that answers from memory without saying so. The fix isn’t a better model — it’s a visible “I didn’t search”, and a button that lets you insist. Both are cheap. Neither is here yet.