All articles
4 min readsearchAIinformation literacy

Search in the AI Era: Why You Still Need to Pick Your Own Engines

Chat assistants make answers cheap, but sources, recency and bias are harder to audit. Why parallel multi-engine search still matters, and how to tell whether an AI answer is usable.

The fastest answer to most questions now comes from a chat box, not a search box. So why maintain a set of search engines at all?

Because "getting an answer" and "judging whether the answer holds" are different jobs — and the second one got harder.

Three hidden costs of an AI answer

One: the sources are compressed into a sentence. A model states a conclusion with two or three links attached, but the reasoning is omitted. When the conclusion is off, the fluent paragraph gives you no clue which step went wrong.

Two: recency is opaque. A model may know how a tool worked in 2024 and not that its API changed last month. Search rankings at least carry time signals; a chat answer carries none.

Three: the illusion of consistency. Ask twice and you may get differently worded, equally confident answers. Confidence is not evidence of correctness, yet in a chat interface it is easily treated as such.

None of this argues against AI. It argues that AI is a starting point, not a destination.

Parallel search matters more, not less

When the answer is generated, you need original, mutually independent sources even more — to cross-check.

Take a concrete question: should this frontend framework be used in production right now?

  • Search gives you official docs, GitHub issues, community threads, posts from the last six months;
  • AI gives you a paragraph: "mature ecosystem, good for small and mid-sized projects";
  • Only the first lets you discover "there was a breaking change last week and the issue is still open."

Four engines at once is not mainly about speed. It is about making disagreement visible. Disagreement is usually where the decision actually lives.

Treat AI as a tenth engine

The practical move is not either/or — it is putting AI inside the same retrieval loop:

Situation Start with Then
A field you know nothing about AI (build the map, learn the terms) Search (verify the key facts)
A specific error or version issue Search + GitHub AI (explain the cause, suggest a fix)
Writing that needs citations Search (find primary sources) AI (structure it, do not generate facts)
A purchase or tooling decision Parallel multi-engine (real experience) AI (summarise patterns, flag disagreement)

In one line: AI converges, search verifies.

How to tell whether an AI answer is usable

Four checks, a few seconds each:

  1. Look for what it omitted. A "comprehensive" answer with no qualifications is usually unreliable.
  2. Verify numbers and version strings. These are both the easiest to hallucinate and the easiest to check.
  3. Ask for sources. If you cannot get a clickable link, treat it as a hypothesis, not a conclusion.
  4. Search for the counter-case. Search "X problems / downsides / pitfalls" and see whether there is a large body of opposing experience.

Steps 3 and 4 both depend on the same thing: a search entry point within reach. That is precisely what a start page is for.

A note on GEO

GEO — generative engine optimization — describes making content more likely to be cited by AI search, not just ranked by traditional search.

What actually works overlaps with SEO and is rather unglamorous:

  • Conclusion first, then reasoning. Generators tend to extract clearly structured passages; lead with a direct sentence.
  • Use question-and-answer structure. Turn real user questions into subheadings and answer immediately beneath.
  • Give checkable specifics. Versions, commands, parameters, comparison tables — not adjectives.
  • Stay crawlable. Server-rendered or prerendered static HTML is read far more reliably than client-only rendering; many AI crawlers do not execute JavaScript.
  • Show the update date. Recency is a signal generators weigh.

These choices are also kinder to humans: writing that leads with the conclusion simply wastes less of your time.

A concrete daily loop

How I approach an unfamiliar problem:

  1. Ask AI: "What are the core concepts here, and what does each one solve?" — thirty seconds to build a map.
  2. Take two key terms and search them in parallel (Baidu/Bing for Chinese, GitHub for code, Zhihu/Xiaohongshu for experience).
  3. If search contradicts the model, trust the primary source and note the disagreement.
  4. Save the useful links to the start page with one line on why they matter.

Step 4 is the one people skip. In three months you will not remember what you concluded today, but you will see that note.

FAQ

Will AI replace search engines?

Not entirely, but it changes the order of use. Fact-checking, time-sensitive content and primary sources still rely on search; structured summarisation, terminology and code rewriting are faster with a model.

Does multi-engine search cause overload?

Yes, which is why two engines are ticked by default. The fix for overload is fewer open tabs, not fewer sources.

Is GEO just writing for AI?

No. GEO is about clear structure, concrete facts and machine-parseable content — not a particular tone. Filler written for machines is useless to people and stops working on models quickly too.

The dividing line in search skill is moving from "can you find it" to "can you judge it." What a tool can do is make the raw material for judgement cheaper to obtain.

Keep reading

Open MyNav

No sign-up. Open it and start.

MyNav