Cloaking
Cloaking is the practice of showing one version of a page to search engine crawlers and a different version to actual human visitors. Done to game rankings: feed Google keyword-stuffed text, show users something completely different. A clear violation of every search engine’s webmaster guidelines and one of the more reliable ways to get a domain manually penalised.
How cloaking actually works
The server detects whether the incoming request is from a known search-engine bot (by user-agent string or IP range) and serves different content based on the detection. Three common implementations:
User-agent cloaking - checking the visitor’s user-agent header. Crude and easily detected because Google occasionally crawls with non-bot user-agents specifically to catch this.
IP-based cloaking - checking against published bot IP ranges. Slightly harder to detect but Google maintains evolving detection that catches the pattern over time.
JavaScript-rendered cloaking - serving search engines the static HTML and humans a dynamically rewritten version via client-side JS. The most modern variant, still violates the guideline.
Why people still do it
Two reasons. The math sometimes works short-term - a cloaked site can rank, generate traffic, monetise, and exit before the penalty hits. And the line between cloaking and legitimate dynamic serving has fuzzy edges that operators exploit.
What’s NOT cloaking, despite looking similar to nervous SEO teams:
Geo-targeted content (showing UK visitors UK content). Allowed.
Mobile vs desktop content variation when both are indexed. Allowed.
Personalisation based on logged-in state when the public version is what gets crawled. Allowed.
Paywalls with first-click-free disclosure. Allowed when properly marked up.
The line: if Google’s crawler and a real user would see substantially the same content given the same URL and context, it’s not cloaking. If you’re showing the crawler keyword-stuffed text and the user a different page entirely, it is.
What happens when Google catches it
Three escalating outcomes:
Algorithmic demotion - the cloaked pages quietly stop ranking. The site doesn’t get a notification; traffic just drains.
Manual action via the Manual Actions report in Search Console. The site owner can see exactly what was flagged and submit a reconsideration request after fixing.
Full deindexing. Rare for first offences, common for repeat offenders or particularly egregious cases. The domain effectively disappears from Google search.
An example
I worked with a recovery client whose previous SEO contractor had implemented IP-based cloaking on 200+ programmatically-generated landing pages. The cloaked version targeted 50+ keywords each. The user-facing version was a generic squeeze page.
It worked for about 14 months. Traffic peaked at 380,000 monthly sessions. Then a manual penalty hit and the site dropped to under 4,000 sessions in a week. The contractor had moved on. The client had to:
Audit and remove every cloaked page (3 weeks of dev work). File a reconsideration request explaining the violation and the fix (a week of writing and back-and-forth with Google). Wait six months for any meaningful traffic recovery, which topped out at about 22,000 sessions - under 6% of the previous peak.
The “cheap” rankings cost a year of revenue and the site never fully recovered. Black-hat tactics remain a reliable way to lose more than you ever earned.
We built Penfriend on the assumption that what you ship is what gets indexed and what gets read - no cloaking, no hidden tricks. Modern algorithms catch cloaking reliably, and the tactics only ever delayed the inevitable deranking; we skipped the detour.
Related terms
- Black-Hat SEO - the broader category cloaking is one of the more serious examples of
- Google Penguin - the algorithm update that hardened detection of manipulative tactics including cloaking
- Duplicate Content - an adjacent SEO problem with overlapping detection mechanisms
- Spam - the broader webmaster-guideline category cloaking falls under
- White-Hat SEO - the practitioner-guideline-compliant approach cloaking is the antithesis of