Text-first search: why the default decides everything

Every search engine made one quiet decision on your behalf: results are a visual experience. Thumbnails beside links, image carousels above answers, and the Images tab one reflexive tap away — because engagement metrics love pictures, and search engines are engagement businesses. The decision was never about answering better. Most questions people actually ask — what time, how much, which way, is it open, what does the posuk say — are answered completely in text. The image grid is not the answer; it is the exposure.

The default is the product

The mainstream concession is a settings page: strict modes, image toggles, safe flags — each one on by choice, off by drift, reset by updates, negotiated by teenagers. Two decades of family experience with those toggles teaches one lesson, the same lesson the sight-protection architecture starts from: a protection that must be maintained is a protection that decays. Defaults are what actually ship; settings are what actually lapse.

Text-first search flips the burden. The result page arrives as ranked, readable answers — clean text rows, sources named, zero ambient thumbnails. Images exist downstream of a decision: the household's tier decides whether an image request opens a judged image lane (every picture passing the same per-image evaluation as the browser's) or stays closed entirely. On the children's tier, the decision is simply never offered — which is the whole architecture of a child's first search box.

This is only buildable, note, by an engine that owns its results end to end. A wrapper around someone else's index inherits someone else's page — thumbnails, carousels, and all. An engine built from the index up — the position of KolBo Search, in the homepage's words "a proprietary search engine, not a filtered feed" — decides its own result page the way a publisher decides its own layout.

“The mainstream engine asks "how do we show more?" A kosher engine asks "what does the answer require?" Most answers require words.”

kolbo.life

What text answers better anyway

The dirty secret of text-first search is that it is frequently the superior product, standards aside:

• Factual queries — zmanim, prices, dates, measurements — resolve faster as text; the thumbnail row is pure latency.
• Navigational queries ("the bank's site," "the school portal") want one right link, not a collage.
• Learning queries — the posuk, the halacha, the how-to — are reading tasks by nature; pictures decorate, text delivers. The Torah-content case runs deeper still, in searching Torah sources.
• Comparison queries want tables and specifications — text structures — which is why serious purchasing research reads better than it scrolls, per the errand-door shopping discipline.

The honest remainder: some queries are legitimately visual — the identification tasks ("what does this rash/plant/part look like"), the visual crafts, the suitcase whose size only a photo conveys. That remainder is exactly what the judged image lane exists for: purposeful image search, opened by tier, every result evaluated. The remainder never justified making every other query visual; it justified a door.

The attention dividend

Families who switch report the same second-order effect: search sessions got shorter. The image grid was not only an exposure surface — it was the drift engine, the place where "what time does the store close" became twenty minutes of looking at things. Text-first pages end when the answer is found, because there is nothing else to look at. In a household economy where attention is the scarcest resource, the quiet result page is not a restriction. It is a refund.

Frequently asked questions