What is adaptive rendering?
Adaptive rendering serves a machine readable version of a website to AI crawlers while people see the site unchanged. How it works and how it differs from cloaking.
Adaptive rendering is serving a different presentation of the same content depending on who is asking for it.
A person gets your website: the design, the imagery, the interactivity, the brand. An AI crawler gets a clean, structured, text first version of the same information, built so a machine can actually read it.
Same facts. Two presentations. One website to maintain.
Why it is needed
Modern websites are built for browsers. A large share of what is on the page is assembled by JavaScript after the initial load, carried in images, or buried under layers of layout that make sense visually and not structurally.
AI crawlers mostly do not execute all of that. Many fetch the raw HTML and read what is there. If your service areas live in a dropdown that renders on interaction, or your proof lives in a carousel of logos, or your actual expertise is in a video, the crawler sees a mostly empty page from a company it cannot describe.
So it recommends a competitor whose site it could read. Not because they are better, but because they were legible.
This is a delivery problem, not a content problem. Most businesses already have the substance. It is just not reaching the machine.
How it works
Appear serves the machine readable version from its own hostname, usually appear.yourdomain.com. Your website remains a separate site.
- A request arrives. Something asks for a page on the Appear hostname.
- The requester is identified. A human browser and an AI crawler can be told apart from the request.
- The right version is served. A person is normally redirected to the matching page on your website. A crawler gets the stored machine readable page.
The design and content of your website do not change. The setup is one DNS record. Some setups also use a connection on the website, such as middleware or a CMS connector.
Is this cloaking?
This is the right question to ask, and it deserves a direct answer.
Cloaking means showing crawlers content that contradicts what users see, in order to deceive. Keywords users never see. Topics the page is not about. A landing page that bears no relation to what the listing promised. Search engines penalise it, correctly.
Adaptive rendering serves the same content in a different format. The claims match. The facts match. The topic matches. A person reading both versions would say they are the same page, differently presented.
The distinction is substance versus presentation:
| Adaptive rendering | Cloaking | |
|---|---|---|
| Content | Same facts both ways | Different content per audience |
| Intent | Legibility | Deception |
| If compared side by side | Consistent | Contradictory |
| Precedent | Format changes, long precedent | Penalised |
Serving different renderings to different user agents is not new or exotic. Mobile versus desktop, AMP, server side rendering for crawlers and client side for users: the web has done this for years. What is new is the audience, not the technique.
The test is simple. If the version served to machines says something your customers would be surprised to read, that is cloaking, whoever is selling it to you.
What it does not do
Adaptive rendering makes your content readable. It does not invent content you do not have.
If you have never addressed a question a buyer is asking, there is nothing to render for it. That gap is a content problem, and it is why GEO (generative engine optimisation) is more than a delivery layer.
Why it matters competitively
Most products in the AI visibility category measure. They tell you how often you are mentioned and by whom, and that report is genuinely useful the first time you read it.
Changing the answer requires changing what the engines can read. That is an architectural capability rather than a reporting one, and it is a meaningfully smaller field.