GlossaryWhat is cloaking, and how is it different from adaptive rendering?

What is cloaking, and how is it different from adaptive rendering?

Cloaking shows machines different content to deceive them. Adaptive rendering shows them the same content in a format they can read. How to tell the two apart.

Cloaking is showing search engines or AI crawlers different content from what people see, in order to deceive them. Adaptive rendering shows machines the same content as people, in a format they can read.

The difference is not whether machines and people get different versions. It is whether the versions say the same thing.

What cloaking looks like

Cloaking exists to make a page look like something it is not. Common forms:

  • Keywords or text that crawlers see and visitors never do
  • A page shown to crawlers about one topic, while visitors get a page about another
  • Doorway pages built only to rank, which send visitors somewhere else
  • Claims, prices or credentials shown to machines that the real page does not make

In every case, a person reading both versions side by side would say they are different pages.

Why it gets sites penalised

Search engines and answer engines recommend a page based on what they read. If visitors then land on something different, the recommendation was false.

That is why search engines treat cloaking as spam and can demote or remove sites that do it. Answer engines read the same web, and many of them run live searches to build their answers. A site caught cloaking is unlikely to be trusted there either.

The risk is not only a penalty. If an answer engine cites something your customers cannot find on your site, you have a credibility problem on the first call.

What adaptive rendering does instead

Adaptive rendering serves one set of facts in two presentations.

A person gets your website as it is: the design, the imagery, the interactivity. An AI crawler gets a clean, structured, text first version of the same information, because many crawlers read raw HTML and cannot see content that only appears after JavaScript runs, or that lives in images and video.

The facts match. The topic matches. The claims match. Only the format changes.

Side by side

CloakingAdaptive rendering
ContentDifferent per audienceSame facts for both
PurposeDeceive the readerMake the content readable
If compared side by sideContradictoryConsistent
What visitors find after clickingSomething other than what was promisedWhat the answer described
Track recordPenalisedLong precedent

Serving different formats is not new

The web has served different presentations of the same content for years. Mobile and desktop versions, accelerated mobile pages, and server side rendering for crawlers alongside client side rendering for people all work this way.

None of those are cloaking, because the content stays the same. Adaptive rendering applies the same principle to a new audience: answer engines.

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.

How to check what a vendor is doing

If someone offers to make your site more visible to answer engines, ask to see the version they serve to machines. Then compare it with your real site.

Warning signs:

  • Text, keywords or topics that do not appear anywhere on your real site
  • Claims about services, locations or credentials you do not offer
  • Pages that machines can reach and visitors cannot
  • Reluctance to show you the machine version at all

A legitimate approach should be easy to show you, and the comparison should be boring.

What adaptive rendering does not do

It does not make thin content good. It makes existing content readable.

If your site never answers a question your buyers ask, there is nothing to render for it. Closing that gap means writing the answer, not changing how it is delivered.

Where Appear fits

Appear uses adaptive rendering. The version we serve to answer engines has to match what your customers see, and we will not write anything that contradicts your real site. That is the line between adaptive rendering and cloaking, and it is not one we move.