Making Your Site Legible to AI

Imagine hiring a brilliant, impatient researcher to evaluate your practice. They can only spend four seconds on your website. They read the raw text — they don't admire the design. And anything they can't verify, they just skip.

That researcher is every AI assistant that will ever consider recommending you.

Designing for that reader isn't dumbing anything down. It's the discipline of stating facts where machines — and, not coincidentally, hurried humans — can actually find them.

Here's the legibility rule. Every fact that should earn you a recommendation must exist as plain, retrievable text on an open page. Not inside an image. Not behind a click-to-reveal. Not implied by beautiful prose. Not gated behind a form. If a literal-minded reader in a hurry couldn't quote it, it doesn't exist.

The checkable list

It renders without tricks. Some sites only serve their content after JavaScript runs. To a crawler that doesn't wait around, those pages are blank. This is a checkable fact, not an opinion. View your page with JavaScript off, or read its source, and see whether your services and details are actually there. Modern, well-built sites pass this automatically. A surprising share of expensive ones don't.

The facts are stated, not implied. What you do. For whom. Where. Hours. Price signals. All as plain, declarative sentences. "Serving families across the South Shore since 2009" gives a machine, and a stranger, something to hold onto. "Excellence in care, close to home" gives it nothing. Every service gets its own named mention — the assistant can't recommend you for implant work it never saw claimed anywhere.

Real questions, really answered. The questions clients actually ask. Cost. Duration. Alternatives. Who it's for. Answered honestly, on the pages where they belong. These are precisely the snippets assistants retrieve and quote, which is why the FAQ habit pays twice.

Structured data, in plain words. Behind the visible page, sites can carry a machine-readable card. Name. Type. Address. Hours. Services. In a standard format. That removes all the guesswork for the reader. You don't need to know the format's name. You need to know it's a standard item on any competent developer's checklist. It's verifiable with free testing tools. And its absence is one of the most common gaps on professional practice sites.

Nothing load-bearing lives in a PDF or an image. Price lists as photos. Service menus as downloads. Both invisible to the researcher. Open pages carry the substance. Files are for humans who already found you.

The five-minute test

Open your own site and play the impatient researcher. From the homepage's raw text alone, in one minute, can you answer what does this practice do, for whom, where, and what does anything cost? Then pick your most valuable service, and check it has a page stating those same facts. Wherever you just hesitated, the assistant skips. That's your fix list. It is usually one afternoon long. And the instrumented version of this exact check is what the Distribution Assessment runs.

Questions practices actually ask

Do I need to rebuild my site for this? Usually not. Most legibility gaps are content gaps. Missing statements. Buried facts. Absent service pages. The rebuild question only really comes up if the site fails the renders-without-tricks test, which is worth knowing regardless.

Should I publish prices? Publish signals, at minimum. "From." Ranges. Typical-case examples. Assistants asked "how much does X cost" cite whoever actually answers. Silence just delegates your pricing conversation to a competitor's page.

Is this different from SEO? It's the surviving core of it. The same clarity serves search engines, assistants, and humans, all at once. What died was everything else.

What about blocking AI from reading my site? You can. And for a business that wants clients, you mostly shouldn't. Three kinds of AI visitor exist, each with a different job. Blocking the ones that fetch and cite pages is opting out of the answers entirely.