June 2, 2026  ·  6 min read

AI search summaries feel like progress. They aren't. Here's the case for search that returns results and nothing else.

The shift happened gradually and then all at once. One day you searched for something, got a page of blue links, clicked through, read the thing. The next day there was a box at the top — confident, authoritative, already summarized — and the links felt almost redundant.

Google calls it AI Overviews. Bing calls it Copilot answers. Perplexity built its whole product around it. Everyone with a search box is racing to bolt on a language model and call it an improvement.

Note: this is the blog for SearchZee, a search engine without AI summaries. Bias disclosed.

The summary is not the answer

When you search for something, you're usually not looking for a sentence. You're looking for evidence. You want to read the Stack Overflow thread where someone had your exact problem and the accepted answer has seventeen caveats in the comments. You want the original study, not a paragraph describing it. You want to see that three different sources agree — or that they contradict each other, which is often more useful.

AI summaries collapse this. They flatten multiple sources into one paragraph, present it with the confidence of a textbook, and make the underlying disagreement invisible. The nuance, the caveats, the "this applies to version 3.x but not 4.x" footnotes — they get dropped. A language model's job is to produce fluent, coherent text. That's in tension with accurately representing uncertainty.

There's a reason experienced researchers scan a results page before clicking anything. The shape of the results is itself information. When the top five results are all forum posts, that signals something different than when one of them is official documentation. When every result is three years old, that tells you the landscape hasn't changed — or that it has and the index is stale. AI summaries erase this signal entirely. You get a paragraph with no topography.

The verification problem is real and it compounds

I want to describe something that has almost certainly happened to you if you use AI-enhanced search regularly: you read the summary, it sounds right, you act on it, and it was wrong. Not spectacularly, hallucination-wrong — just quietly, confidently wrong in a way that's hard to catch because you never looked at a source.

With traditional search, the path to verification is obvious and psychologically natural: you click the link. With an AI summary, the citation is there in small text, but the experience has changed the framing. The system already presented you with an answer. Clicking through now feels like expressing distrust in the tool, rather than just doing your homework.

This matters most on exactly the queries where it matters most. Medical questions. Legal questions. Technical decisions with downstream consequences. Configuration options where one wrong flag breaks something in production. These are precisely the searches where you should be reading the primary source rather than a synthesized paragraph — and they're the searches where the summary is most seductive.

What stops clicking through does to the web

Here's the part of the AI-search debate that doesn't get enough attention: websites exist because people visit them. Writers and researchers publish because readers arrive. When a search engine absorbs traffic that would otherwise go to a source, the economic basis for producing that source weakens.

The web's quality is not a given. It's an ongoing output of people who create things because doing so is worthwhile — financially, reputationally, or intrinsically. Drain the traffic long enough and you change the incentive structure. The AI eats the web and then, over time, produces summaries of a web that's no longer being maintained.

You can already see early signs of this. Forum communities that were once dense with real, battle-tested answers are thinning out. Long-tail technical documentation sites are getting less traffic. The stuff that would have been a second or third click is getting fewer second and third clicks because the first response was a summary that felt sufficient.

Using a search engine that passes traffic through to sources is a small, individual way to not accelerate this. It probably won't reverse anything at SearchZee's scale. But it's still a thing worth doing.

What results-only search actually gives you

When there's no AI box at the top, something simple happens: you read the results. You scan titles, notice sources, make judgments. You click two or three things instead of one. You build a picture from several angles rather than accepting a synthesis.

This is slower. That's real. It's more work. And it is, in practice, more accurate — because accuracy in information retrieval is a function of reading, not of being read to.

When a search engine returns results and nothing else, that minimalism is doing real work — the absence of a summary isn't a limitation, it's an opinion about who should be synthesizing the information.

You should be. You're the one who knows what question you're actually asking.

To be honest about when AI search works fine

Unit conversions. The capital of a country. When a movie came out. Dictionary definitions. For factual lookups with well-established, low-ambiguity answers, an AI summary is genuinely useful — the cost of a small error is low and the time saved is real.

The problem is that you can't apply this only to some queries. Once the summary box exists, it appears on everything, including the queries where the cost of a confident wrong answer is high. And the model doesn't know which kind of query it's responding to — it produces equally confident-sounding prose for a unit conversion and for a question about drug interactions.

That's not a fixable UX problem. It's a structural feature of the approach.

If you've felt the nagging sense that you're trusting search results more and verifying them less, that instinct is worth listening to. Try searching without the summary box for a week and notice what changes.