Insights · 2026-10-20 · 4 min read

How we make a website AI assistants can quote

Search engines read pages. AI assistants read answers. The difference changes how we write every page.

What changed

A growing share of buyers ask an assistant before they search. The assistant reads a handful of pages, extracts facts, and names two or three companies. If your page doesn't state the fact plainly, you are not one of them.

One question, one plain answer

Every service page carries the questions buyers actually ask, with a direct answer under each, in the words a buyer would use. Price, time, who owns the code, whether it runs on a phone. Marked up as structured data so the answer can be lifted whole.

A facts page

One page, no adjectives: legal name, founded, headquarters, regions, languages, services, method, contact. Quotable by a journalist or an assistant without interpretation. Ours is at /facts.

Structured data on every page

Organization, Service, FAQPage, BreadcrumbList and Article where they apply. Not for a badge: so that a machine reading the page can say what it is about without guessing.

An llms.txt

A plain-text index at /llms.txt that lists what the site contains and where, for the crawlers that read it.

Seven languages, one source

Each edition is a full translation with the same structure and its own language links, so an assistant answering in Arabic or Japanese finds the Arabic or Japanese answer, not a translation of a translation.

What we don't promise

Which sources an assistant cites is its decision. Anyone who promises placement is guessing. We make you the clearest answer available and measure what follows.

Tell us what you need built.

An engineer reads it and replies within minutes, in your language. Every project starts with a two-week prototype at a flat price.

How we make a website AI assistants can quote — eORB