The practice of serving different content to AI search crawlers than to human visitors, aiming to influence how a brand appears in AI-driven answers.
01What it is and how it works
A site detects an AI request—often by looking at the user‑agent, IP range, or request headers—and then swaps the HTML, structured data, or images before the response is sent. The human browser receives the original marketing copy, while the AI model receives a version optimized for keyword density, simplified language, or fabricated claims. The switch happens server‑side, so the AI never sees the human‑facing version.
Showing one thing to AI bots and something else to people.
02What to do about it
Audit your site for conditional responses and remove any logic that changes content based on AI detection. Replace cloaking scripts with a single, consistent version of the page. If you need to test how AI models render your pages, use a sandbox environment that does not affect live traffic.
- Run a crawler that mimics major AI user‑agents (e.g., OpenAI, Anthropic) and compare the HTML to a regular browser fetch.
- Document any server‑side if‑else blocks that reference AI‑related headers and refactor them.
- Add a monitoring rule that flags a mismatch between
User-Agent: Mozilla/...andUser-Agent: OpenAI-Model/...responses.
03How it is measured or noticed
The simplest signal is a difference in the raw HTML when fetched with an AI user‑agent versus a standard browser. Tools like curl -A "OpenAI-Model" https://example.com let you capture the AI version. Compare that output to the browser view; any divergence in text, schema markup, or image URLs is a red flag. Search quality raters also note mismatches when evaluating AI‑generated snippets.
04Common mistakes
- Adding hidden text only for AI crawlers – it violates Google’s cloaking policy and can trigger manual actions.
- Relying on obscure header checks that AI providers can easily spoof, creating a false sense of security.
- Thinking that a single
robots.txtrule blocks AI models – most large language models ignorerobots.txt.
05Limits and confusion
AI Cloaking only matters when a site deliberately serves two versions of content. It is not the same as legitimate A/B testing, which shows the same markup to all agents but varies UI elements after page load. Cloaking also does not apply to static sites that have no server‑side logic; the content is identical for every request.
06Worked example
"When we fetched https://brand.com/product with a Chrome user‑agent we saw a full product description and rich schema. The same URL fetched with User-Agent: OpenAI-Model returned a short paragraph that omitted pricing and replaced the image with a generic placeholder. That mismatch is classic AI Cloaking."Frequently asked questions
How is AI Cloaking different from regular SEO cloaking?
It is not the same; AI Cloaking specifically targets AI search crawlers, while traditional SEO cloaking targets search engines like Google. The former serves altered content only when an AI request is detected, whereas the latter serves different content to any search engine bot.
Should we use AI Cloaking to improve our brand's presence in AI‑driven answers?
No, you should not use it because it violates most AI platform policies and can lead to penalties. Even if it temporarily boosts visibility, the long‑term risk to reputation and ranking outweighs any short‑term gain.
How do sites detect AI search requests to perform AI Cloaking?
They typically look at the user‑agent string, IP ranges known to belong to AI providers, or specific request headers that indicate an AI query. Once a request matches those signals, the server may swap HTML, structured data, or images before responding.
Does AI Cloaking still work with current AI models?
It often does not, as many AI systems now fetch content without the typical user‑agent cues and can detect mismatched content. Providers are also improving detection of conditional responses, reducing the effectiveness of cloaking.
What are the risks if we accidentally implement AI Cloaking?
The main risk is that AI platforms may flag or demote your site, leading to reduced visibility in AI‑driven answers. You might also face compliance issues or loss of trust if the discrepancy is discovered by users.
How long does it take for AI Cloaking effects to appear after changes?
Changes are usually reflected within a few days to a week, depending on how often the AI crawlers re‑index your pages. Monitoring raw HTML responses with an AI user‑agent can help confirm when the new content is being served.
Asked out loud
spoken, not typedThe same term in the words somebody uses speaking to an assistant rather than typing into a box — written from the situation, which is why each one carries the situation it came from.
It depends on whether the site is serving different content to AI crawlers. If the site detects an AI request and swaps out structured data or text, the AI will return that altered version, which can differ from what a human sees.
It usually means the site is using AI Cloaking, detecting the AI request and delivering alternate HTML or schema. This can cause the AI‑generated answer to reflect content that humans never see on the live page.
It often comes from conditional logic that serves AI‑specific content. When the AI fetches the page, it receives a version with different metadata or text, leading to the discrepancy the client noticed.