For most of the web's history, asking a question meant getting a list. You typed a few words, a search engine handed back ten ranked links, and the actual work—reading, weighing, deciding which source deserved your trust—was left to you. That arrangement is quietly being replaced. More and more, the first thing you see is not a list of places to look but a finished paragraph that has already done the looking, written in the even, confident cadence of ChatGPT, Gemini, Claude, Perplexity, or Google's own AI Overviews.

Comparing generated answers means running the same question through several of those systems and reading the replies side by side—treating where they agree, where they contradict each other, and what they quietly leave out as the useful signal, instead of trusting whichever one you happened to open. It is a genuinely different act from the older skill of comparing links, and understanding why is the point of this piece.

None of this means classic search is finished. To find a specific page, a nearby store, a phone number, or the official text of a document, a ranked list of links is still the better instrument and probably always will be. The change is narrower than the "search is dead" headlines suggest: for the open-ended, judgment-heavy questions people increasingly bring to a chatbot, the unit of the answer has changed—from a link you open to a claim already written for you—and so has the work of checking it.

From ten blue links to one paragraph

The web's answer machine was built in layers, and it helps to remember how thin the current top layer is. Yahoo started in the mid-1990s as a directory maintained largely by hand—people sorting sites into categories, more librarians than algorithm. Google's advantage, described in Sergey Brin and Lawrence Page's 1998 paper on the engine's design, was to let the web rank itself: PageRank treated a link from one page to another as a kind of vote, so authority emerged from the structure of the web rather than from an editor's judgment. For roughly two decades the pattern held steady—crawl the pages, rank them, return a list—and we all learned to read it, skimming past the ads, distrusting the too-perfect result, opening three tabs before believing anything.

Generative chat broke that habit for one specific class of question. When the answer to "how should I think about this" or "what are the tradeoffs here" arrives as a written paragraph rather than a set of destinations, the reader's job changes shape. You are no longer choosing among sources; you are being handed a synthesis and asked, implicitly, to trust it. That is a real convenience for a lot of everyday questions. It is also where the trouble starts, because the thing you are now trusting is much harder to inspect than a link ever was.

Why comparing answers is not like comparing links

A link is a durable object. It points at a specific page you can open, read in full, check the date on, and return to later — where, barring an edit or a takedown, you will usually find the same words waiting. Two people who follow the same link see the same thing. You can judge a source partly by where it lives—a court filing, a manufacturer's spec sheet, and a stranger's forum post announce their reliability, in part, just by their address.

A generated answer is none of those things. It is produced on demand, phrased slightly differently each time you ask, and shaped by which model version happens to be live that week. Its sources, when it has them, are folded into fluent prose or appended as citations you have to trust it got right. That last assumption is the fragile one. In a study published by Columbia Journalism Review in March 2025, researchers at the Tow Center for Digital Journalism at Columbia Journalism School made the problem concrete: they took excerpts from real articles—ten each from twenty publishers—and asked eight AI search tools to name the headline, publisher, date, and URL each excerpt came from, running 1,600 queries in all. Across the tools, more than 60 percent of those answers were wrong, and the spread was wide: Perplexity was incorrect on 37 percent of queries, while xAI's Grok-3 missed 94 percent. Several tools did not merely misattribute a source; they produced fabricated or broken URLs that led to nothing.

So comparing links and comparing answers ask different things of you. With links, the sources are the objects, and your job is to pick the good ones. With generated answers, the sources are a claim the model is making about itself—and that claim, the Tow Center's numbers suggest, cannot be taken at face value. Reading several answers next to each other is the closest thing to inspecting the sources you get back, because the disagreements are where the hidden uncertainty finally becomes visible.

Why agreement is not proof

The natural next move, once you accept that one answer can be confidently wrong, is to ask a few systems and trust whatever they agree on. The instinct is sound, and it is most of what a comparison is good for—but it carries a trap worth naming plainly. Today's leading models are trained on heavily overlapping slices of the same public web. When they converge on an answer, that convergence can be genuine corroboration, or it can be the same gap in the same training data surfacing four times. Agreement narrows your risk; it does not manufacture a fact none of the models actually had.

The BBC's own research, published in February 2025, points at a related failure mode. When its journalists reviewed how ChatGPT, Copilot, Gemini, and Perplexity answered a hundred questions about the news, 13 percent of the quotes those tools attributed to BBC articles had been altered or did not appear in the cited article at all. The study did not test whether the same invented quote recurred across models, but correlated error is a real possibility: systems drawing on overlapping source material, retrieval indexes, or widely repeated inaccuracies can independently arrive at the same wrong claim. When that happens, agreement is repetition, not corroboration.

This is why a comparison is a triage tool rather than a verdict. Contradictions tell you which claims need inspection, while a source or qualification supplied by just one system may expose what the other syntheses silently omitted. But the points of agreement still have to earn their trust the old-fashioned way on anything that matters—against a primary source, not against another model.

What the pattern already looks like in practice

None of this is abstract for the people already doing it by hand. On forums like r/ChatGPT you can find users who built their own ways to run one prompt across several assistants at once and read the results together. A builder posting in an AI forum is an early-adopter example, not evidence about mainstream search behavior. What it does show is that the comparison habit emerged before vendors packaged it.

That emerging habit is what a comparison engine automates. Qorpus is one implementation of the pattern—a desktop browser extension that pushes a single prompt through the AI accounts you are already signed into and stacks the returning answers in one view. Its limits are the honest kind: it drives the vendors' own web interfaces rather than a hosted API, so it needs you logged in, runs on the desktop rather than a phone today, and—like every approach described here—cannot turn four agreeing answers into a fact that none of them actually held.

Where this leaves classic search

The web is not trading links for answers so much as growing a second layer on top of the first. The ranked list is still underneath, still the right tool for known-item lookups, navigation, shopping, and any question where you want the source itself rather than a summary of it. What is new is the layer above it, where a model reads on your behalf and returns a paragraph—faster than a list, and harder to verify than one.

For that layer, skepticism means following citations, checking dates, and noticing what the synthesis leaves out—not merely accepting a polished paragraph as the end of the search. Comparing outputs can reveal where to inspect, but the source still has to answer for the claim. There is a practical method for making those checks proportionate, along with the fuller case for questioning a single answer before acting.

References

  1. Sergey Brin and Lawrence Page. The Anatomy of a Large-Scale Hypertextual Web Search Engine (1998)
  2. Tow Center for Digital Journalism at Columbia Journalism School. AI Search Has a Citation Problem, published by Columbia Journalism Review (March 2025)
  3. BBC. BBC research shows issues with answers from AI assistants (February 2025)
  4. I made a way to compare multiple AI answers at once — r/ChatGPT (early-adopter account)