The Librarian Pattern: websites you talk to instead of browse

This is a condensed version of my preprint (DOI: 10.5281/zenodo.21345310, CC BY 4.0). Reference implementation: askbar.pro.

The library problem

For thirty years the website has been a library: a visitor arrives with one question and is expected to find the answer themselves, navigating menus, pages, and filters. Visitors read a small fraction of site content. Most leave without doing the thing the site owner hoped for. Chat widgets bolted onto such sites change nothing: the maze remains, the widget just answers questions about the maze.

The pattern

The Librarian Pattern inverts the relationship. The site does not present itself; it asks what you need and assembles the answer.

1. The bar as the primary interface. One persistent input, text and hold-to-talk voice. It replaces navigation.
2. Scene reassembly (generative UI). The center of the screen is not a page but a scene, composed per recognized intent. Transitions morph rather than reload.
3. A guide with a plan. The conversational layer is a consultant with a goal ladder, asking one next question, never presenting menus of three options.
4. Two button systems. Global suggestion chips above the bar are visually separated from in-scene action cards. This prevents the "six buttons" degeneration of chat UIs.
5. The static shadow. Every live scene has a server-rendered twin page: full text in the DOM, question-shaped headings, FAQ schema, llms.txt, freshness stamps. Humans get the agent; crawlers and AI answer engines get complete, citable pages, generated from the same content source.
6. Structural GEO-readiness. Content already organized as questions and answers matches how generative engines retrieve and cite, by construction.

The result that surprised me

24 hours after the discoverability layer went public, Yandex Alice (the largest Russian AI answer engine) began citing the reference implementation as its prime example for the "next-generation website" query, describing the mechanics correctly and distinguishing it from "a chat widget in the corner". One week earlier, equivalent queries returned nothing. Screenshots are dated and timestamped (OpenTimestamps + Wayback).

The lesson generalizes: as search migrates from ranked links to generated answers, the unit of discoverability shifts from the page to the citable answer. A site structured as a dialogue is preferentially legible to engines whose whole job is answering questions.

Honest positioning

Conversational UIs, chatbots and AI site builders all predate this. What I'm documenting is the specific combination (bar as THE interface + model-assembled scenes + goal-driven guide + dual-face static shadow) as a single reproducible pattern, with a verifiable date and a production implementation. Full details, provenance and limitations are in the preprint.

Author: Eduard Gutarin, founder of AskBar.