Making Your Site Legible to AI

Imagine hiring a brilliant, impatient researcher to evaluate your practice — but they can only spend four seconds on your website, they read the raw text rather than admire the design, and anything they can't verify they simply skip. That researcher is every AI assistant that will ever consider recommending you.

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

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 serve their content only after JavaScript runs — and 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 automatically; a surprising share of expensive ones don't.

The facts are stated, not implied. What you do, for whom, where, hours, and price signals — as declarative sentences. "Serving families across the South Shore since 2009" gives a machine (and a stranger) something to hold. "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.

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 — the business's name, type, address, hours, services in a standard format — that removes all 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: 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, usually one afternoon long — and the instrumented version of this exact check is what the Get Found by AI Audit 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 arises when the site fails the renders-without-tricks test, which is worth knowing regardless.

Should I publish prices? Publish signals at minimum — "from," ranges, or typical-case examples. Assistants asked "how much does X cost" cite whoever answers; silence delegates your pricing conversation to competitors' pages.

Is this different from SEO? It's the surviving core of it: the same clarity serves search engines, assistants, and humans. What died was everything that wasn't this.

What about blocking AI from reading my site? You can — and for a business that wants clients, mostly shouldn't. The three kinds of AI visitor have different jobs, and blocking the ones that fetch and cite pages is opting out of the answers.

---

Part of Get Found by AI — the deep dive on the second front door.