What is cloaking in SEO?
The short answer to what is cloaking in SEO is this: it is the practice of deliberately showing search engine crawlers different content than the content real human visitors see, in order to manipulate rankings. The server detects who is requesting the page — usually by inspecting the user-agent string or the visitor's IP address — and serves one version to Googlebot and a completely different version to people. Because Google ranks the page on content the searcher will never actually get, cloaking is treated as deception, not optimization.
The reason this matters is that Google's entire ranking system rests on one assumption: the page it crawls is the page the user lands on. Cloaking breaks that promise. A site might rank a page for "free recipes" by feeding Googlebot a keyword-rich cooking article, while human visitors get a page full of ads, an affiliate redirect, or unrelated spam. The searcher clicks a relevant-looking result and gets something else entirely — which is exactly the bad experience Google's spam policies exist to prevent.
Cloaking is a form of black hat SEO — tactics that violate search engine guidelines to chase short-term ranking gains. For the contrast with legitimate, sustainable methods, see white hat vs black hat SEO. The defining test for cloaking is simple: is the difference between what the crawler sees and what the user sees intended to deceive? If yes, it is cloaking, regardless of the technical method used to pull it off.
Common examples of cloaking
Cloaking takes several forms, but every one shares the same fingerprint: the content served depends on who is asking. Here are the patterns Google's spam team looks for:
- User-agent cloaking — the server checks the request's user-agent and returns keyword-stuffed HTML when it sees Googlebot, but the real (often thin or spammy) page to a normal browser.
- IP-based cloaking — the site maintains a list of known search-engine IP ranges and serves them a special version, hiding it from everyone else.
- Invisible text and keywords — stuffing a page with keywords set to the same color as the background, or hidden with CSS, so crawlers read them but users never see them.
- Sneaky redirects — the crawler is allowed to index a clean landing page, while users are silently redirected via JavaScript to a different destination, such as a scam or affiliate offer.
- HTML-vs-Flash / content swaps — historically, serving crawlers a text-rich version while users got a media-only page with no crawlable content.
A classic real-world example: a page ranks for a competitive medical query by showing Google an authoritative, well-written article, while human visitors are redirected to an unlicensed pharmacy. Google indexes trust; the user gets risk. That gap is the whole point of cloaking — and the whole reason it is penalized.
Serving the same page to everyone and letting Google decide how to rank it is the safe default. The moment your server branches its output based on "is this a crawler?", you are one design decision away from a policy violation.
Why cloaking is against Google's guidelines
Cloaking is explicitly listed in Google's spam policies as a violation, and it can trigger either an algorithmic suppression or a manual action from Google's webspam team. The consequences scale with intent and severity: a page can lose its rankings, a whole section of a site can be demoted, or — in serious cases — the entire domain can be removed from the index. Recovering from a manual action means removing the cloaking, then filing a reconsideration request, a process that can take weeks with no guaranteed outcome.
The risk is asymmetric, which is why cloaking is never worth it. The upside is a temporary ranking boost that lasts only until detection; the downside is losing the organic traffic a site may have spent years building. Because search engines continuously improve at fetching pages the way a real browser would — rendering JavaScript, comparing crawler and user responses — detection has only gotten more reliable over time.
There is also a compounding cost. Once a domain earns a manual action for cloaking, it draws closer scrutiny going forward. Legitimate future changes may be reviewed more harshly, and rebuilding trust with Google is far slower than losing it. If you want to understand where cloaking sits in the broader landscape of crawl and index controls, what is technical SEO maps the legitimate levers you actually have.
Cloaking vs. legitimate dynamic rendering
Not every case of serving different responses to crawlers is cloaking. Dynamic rendering, geolocation, and personalization can all be legitimate — the line is intent to deceive. Cloaking manipulates rankings by hiding the real page from users; legitimate techniques serve everyone equivalent content and exist to solve a real user or technical problem, not to game the ranking.
Here is how to tell the difference at a glance:
| Technique | What differs | Intent | Cloaking? |
|---|---|---|---|
| User-agent content swap | Crawler gets keyword-rich page, users get spam | Manipulate rankings | Yes — violation |
| Hidden text / invisible keywords | Text visible to bots, hidden from users | Manipulate rankings | Yes — violation |
| Sneaky JS redirect | Bot indexes clean page, users redirected elsewhere | Deceive searchers | Yes — violation |
| Dynamic rendering | Bot gets pre-rendered HTML snapshot | Help bots read JS-heavy pages | No — content is equivalent |
| Geolocation | Visitor sees region-appropriate page | Serve relevant local content | No — bot sees the same |
| AI-crawler content mismatch | GPTBot/ClaudeBot get different content than users | Influence AI citations | Yes — AI cloaking |
The key principle Google publishes is equivalence: whatever a crawler receives should be materially the same content a user would receive. Dynamic rendering — serving a pre-rendered HTML snapshot to bots that struggle with heavy JavaScript — is fine because the bot gets the same content, just rendered server-side. Geolocation is fine because you show a French visitor and Googlebot-from-France the same French page. Personalization is fine because the core content is the same for everyone; only minor, non-deceptive elements differ.
It becomes cloaking the moment the crawler's version is chosen specifically to rank for something the user will not get. If you are ever unsure, apply the test: would you be comfortable showing Google exactly what the user sees, and vice versa? If the honest answer is no, it is cloaking.
AI cloaking: the emerging GEO version
AI cloaking is a newer variant where a site shows AI crawlers — like OpenAI's GPTBot, Anthropic's ClaudeBot, or PerplexityBot — different content than it shows human users or Googlebot. As AI answer engines (ChatGPT, Perplexity, Google AI Overviews) become a real source of traffic and citations, some sites are tempted to feed those bots optimized, keyword-loaded, or misleading content to influence how they get summarized and cited. It is the same deception as classic cloaking, aimed at a new set of crawlers.
AI cloaking is a genuine generative engine optimization (GEO) problem for two reasons. First, it can poison AI answers: if a model is trained or grounded on content the user never sees, its citations misrepresent the real page. Second, it is often unintentional — a site may block or mis-serve AI bots through aggressive bot rules, a firewall, or a CDN setting, without realizing crawlers and users are now getting different responses. Whether deliberate or accidental, the mismatch is what matters.
This is exactly what our auditor probes for. The tool fetches your URL as a normal browser and again using AI user-agents, then compares the responses to flag mismatches — the signature of AI-crawler cloaking. It also checks whether you are blocking these bots at all. To decide who *should* reach your content, see how to block AI crawlers for the legitimate, transparent way to control access — blocking a bot openly in robots.txt is a policy choice, not cloaking. The line is the same as before: transparency is fine, deception is not.
You can check your own site in seconds. Run a free SEO + GEO audit — it verifies indexability, AI-crawler access, and content-equivalence across user-agents, so you catch accidental cloaking before it costs you citations. For the wider optimization playbook, read how to do AI search optimization.