Beautiful to people, legible to machines
A site can look immaculate and still read as fog to the systems deciding what to recommend. The blind spot is structure, and unlike taste, structure is checkable.
Definition
An AI-readable website is one whose meaning machines can parse without guessing: semantic HTML, a logical heading hierarchy, copy that exists as real text in the document, structured data naming the business and its offer, and a core message that survives with JavaScript disabled.
Structure study / surface and what holds it
Where sites silently fail
The common failures are invisible in a design review. Headlines baked into images or canvas. Meaning that only exists after JavaScript runs. Heading levels chosen for size instead of hierarchy. A homepage that says everything about feeling and nothing about category. Each one reads fine to a person and costs the site a machine reader.
The test is unglamorous: switch JavaScript off and look at what survives. Read the page as headings alone. If category, audience, offer, and proof are not obvious from those views, the systems assembling answers about your market are working from guesswork, and guesswork loses to any competitor who made it explicit.
Which machines actually run your JavaScript
Google renders JavaScript, and that is the exception people generalise from. Vercel instrumented AI crawler traffic across its network and found the crawlers behind ChatGPT and Claude request JavaScript files, ChatGPT on 11.50% of requests and Claude on 23.84%, then never execute them. In Vercel's words: they cannot read client-side rendered content.
This is why the raw HTML matters more than the rendered page. If your category, offer and proof only appear once the bundle has run, then Google may see them and the systems answering questions about your market largely will not.
"Server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript."
An answer engine never sees your layout. It reads the structure beneath it, and that is what decides whether you get quoted.
11.50%
of ChatGPT's crawler requests fetch JavaScript files. None of them are executed.
Vercel, The rise of the AI crawler23.84%
of Claude's crawler requests fetch JavaScript files, with the same result: no execution, no client-rendered content.
Vercel, The rise of the AI crawler97%
of llms.txt files received zero requests in May 2026, across server logs from 137,000 domains. Structure inside the HTML matters more than a side file.
Ahrefs server-log analysis, via PPC LandHow Reidify builds for both
Every Reidify build treats the document as a first-class surface: real text everywhere meaning lives, one h1 per page, schema for the organisation and each offer, and copy whose first sentence can be lifted into an answer accurately. The visual layer, motion, atmosphere, and typography, sits on top of that structure and never replaces it. Designed for humans, structured for AI is an engineering claim before it is a tagline.
| Element | What a person sees | What a machine reads |
|---|---|---|
| Hero | A striking visual and a feeling | The h1, or nothing if the words are pixels |
| Services | Cards with icons and polish | Headings and text, if they exist in the DOM |
| Proof | A wall of logos | Alt text and schema, or an empty div |
| Identity | The vibe of the brand | Organization schema: name, category, founder, location |
Common questions
What makes a website AI-readable?
Semantic HTML, a logical heading tree, meaningful copy that lives in the DOM as real text, structured data that names the business and its offer, and pages whose core message survives with JavaScript disabled.
Can AI crawlers read JavaScript-heavy sites?
Unevenly. Google renders JavaScript reliably; many AI crawlers and answer engines read the raw HTML first or only. If meaning only exists after hydration, part of your audience of machines never sees it.
Does AI-readable mean plain or ugly?
No. Readability lives in the document structure, not the visual layer. A site can be cinematic for people and perfectly legible to machines; this site is built that way.
How do I check my own site?
Disable JavaScript and see what survives. Then read your page as a list of headings only. If the category, offer, audience, and proof are not obvious from those two views, machines are guessing.