Trust Center

Same facts,
every rendering.

AEO rendering is where cloaking accusations start, so we published the rule instead of leaving it to trust.

The Audience-Aware CMS delivers a page in more than one form: a machine-readable rendering with explicit structure and entity markup, and a rich rendering for human readers, with variants adapted to what different audiences need to know. There is one rule governing all of it. Every rendering carries the same facts and the same claims.

The rule, stated plainly.

The machine-readable version is clearer, not different. It contains no assertion the human version does not make.

We do not detect crawlers and serve them separate content. Audience variants are selected by declared or contextual signals available to any visitor, never by identifying the reader as a bot. Every rendering is publicly reachable and can be inspected by anyone, including our clients' competitors.

How parity is enforced

Four controls.

✓

Audience variants are selected by declared or contextual signal, never by user-agent or bot detection

✓

The same claims underlie every rendering; the machine-readable version adds structure, not content

✓

Any visitor, including a competitor or a regulator, can load any rendering directly and compare it

✓

Publishing this page is itself part of the control: a public commitment a client's counsel can cite

Why we publish this

Absolute transparency in how we deliver content.

Serving distinct versions of a page to search engines or AI crawlers compared to human readers can be viewed negatively by major platforms and risks unintentional policy violations. To ensure total trust, we prefer to define our standards publicly, ensuring our methods remain clearly above board and consistently aligned with platform best practices.