Cloaking

What is cloaking?

Cloaking is the practice of showing different content to search engines than to users in order to manipulate search rankings and mislead people. The server detects a crawler like Googlebot and serves it one page, while human visitors get something else. It is a clear breach of Google’s cloaking policy.

Google’s examples include showing a page about travel destinations to search engines while users see a page about discount drugs, and inserting text or keywords only when the request comes from a search engine. Cloaked images, where Google Images sees a different picture from the site, have their own manual action type.

Not every difference is cloaking. Paywalls and subscription content are fine if Google sees the full content you show subscribers and you follow Google’s guidance on flexible sampling. Showing different layouts to mobile and desktop users, or translating for different languages, is fine when the content is the same for Googlebot and users in the same situation.

Why cloaking matters for SEO

Cloaking is one of the oldest and most clearly banned tactics. It is also a common sign of a hacked site: attackers often cloak injected spam so the owner sees a normal page while Google sees pharma or casino links.

The white hat alternative is to make the real page good enough to rank: content optimisation, and server-side rendering if you worry Googlebot cannot see JavaScript content.

Risks of cloaking

• A “Cloaking and/or sneaky redirects” manual action, or “Major spam problems” for aggressive cases.
• Removal from search results for the cloaked pages or the whole site.
• If the cloaking comes from a hack, users may be sent to harmful pages and browsers may show security warnings.
• Loss of trust from users who land on something other than what the search result promised.

How to check a site for cloaking

1. Use URL Inspection in Search Console and view the crawled page and screenshot. Compare it with what you see in a browser.
2. Compare the title and snippet Google shows for the page with the live page; big differences are a warning sign.
3. Look in server config, CDN rules and plugins for logic that changes content by user agent or IP for search engines.
4. If you find cloaking you did not add, treat the site as hacked: clean it, close the hole and request review.
5. Remove any intentional cloaking and serve everyone the same content, then request review if there is a manual action.

Cloaking example

A search result shows “Beginner’s guide to houseplants” with a matching snippet. Clicking it opens a page selling replica watches. URL Inspection shows Googlebot sees the houseplant guide; your browser never does.