SEO glossary · Updated
Cloaking in SEO: what it is and why it's risky
Cloaking is showing search engines different content from what human visitors see, in order to manipulate rankings or mislead users.
Founder, SEO·AEO·GEO
Builds SEO·AEO·GEO and writes the crawler, schema, and citation research published here.
Cloaking is serving one version of a page to search engine crawlers and a different version to people. Google's spam policies define it as presenting different content to users and search engines with the intent to manipulate search rankings and mislead users.
Examples Google gives
- Showing a page about travel destinations to search engines while showing a page about discount drugs to users.
- Inserting text or keywords into a page only when the visitor is a search engine crawler.
Sites that break Google's spam policies may rank lower or not appear in results at all, and cloaking is a classic cause of manual actions.
Accidental cloaking
Some setups make crawlers and people see different things without anyone intending to deceive:
| Situation | Risk | Fix |
|---|---|---|
| A firewall or bot filter serves crawlers a challenge page | Crawlers can't see your content at all | Allow verified search and AI crawlers |
| Content only loads with JavaScript | Crawlers that don't run JavaScript see an empty page | Render the content on the server |
| Paywalled content shown to Googlebot | Can look like cloaking | Use Google's paywalled content structured data |
| Different content by country or device | Fine if users in that situation see the same | Serve the same content to Googlebot as to users in its location |
Personalizing for users is fine. What crosses the line is deliberately showing crawlers something users don't get.
Check it on your own site
What the free audit tests for this
- Edge access
- Raw HTML visibility
One URL, about 20 seconds, no login. You get the result of every check and the exact fix for the top three issues.
Audit your website freeFAQ
Is dynamic rendering cloaking?+
Google has said dynamic rendering, serving pre-rendered HTML to crawlers, isn't cloaking as long as the content is the same, but it now recommends server-side rendering instead.
Can cloaking be done accidentally?+
Yes, in effect. Firewalls, bot filters and JavaScript-only content can mean crawlers see something different. It isn't deceptive, but it still costs you visibility.
Sources
- Spam policies for Google web search — Google Search Central (2026-08-28)
- Understand JavaScript SEO basics — Google Search Central