Overcloakovercloak
SEOMarch 20, 2026·11 min read

SEO Cloaking Explained: How to Rank Without Getting Deindexed

Show Google one thing, show users another. The complete technical guide to SEO cloaking in 2026.

Overcloak

Overcloak Team

@overcloak

share

SEO cloaking is showing search crawlers content optimized for ranking, while showing real visitors a different page (typically the actual product or offer). It's been around since 1998. Google explicitly bans it. People still do it — at scale, profitably.

This guide is the technical playbook. We don't take a moral position. If you're going to do it, do it correctly.

Why it works

Search ranking signals are heavily weighted on text content + link authority. If you write 5,000 words of perfectly-optimized content for 'best crypto exchange,' Google ranks the page. But your real business is sending visitors to your affiliate exchange — not reading 5,000 words. So you serve the long content to Googlebot and redirect humans to the exchange.

How Google detects cloaking

Three primary signals:

  1. 1Crawler diversity — Google crawls from multiple IP ranges (66.249.x is the famous one but they also crawl from residential IPs masquerading as users).
  2. 2Live snapshot diff — they compare what Googlebot sees against what a regular Chrome instance sees. Major differences flag manual review.
  3. 3User behavior — high bounce rate from search, very short dwell, no scroll depth = Google starts re-checking the page.

The two cloaking modes

User-Agent based (cheap, weak):

  • Check User-Agent header for Googlebot string
  • Serve different content if matched
  • Easy to bypass: Google crawls from real Chrome with real UAs to verify

IP + reverse DNS based (proper):

  • Verify request IP is in Google's range
  • Reverse-DNS lookup must return *.googlebot.com or *.google.com
  • Forward-DNS lookup of that hostname must return the original IP
  • Only then serve crawler content

Mode 2 is what we do at Overcloak. UA-only cloaking gets caught in weeks.

What to serve crawlers vs users

Crawler view: long-form, keyword-dense article that answers the search intent. 2,000-5,000 words. Internal links to other crawler pages. Schema.org structured data. Outbound links to authoritative sources. The works.

User view: your offer page. Or a thin pre-sell with a CTA to the offer. Or a redirect (some do this — but redirects on first paint are themselves a flag).

Risk of deindexation

If caught, Google deindexes the page (best case) or the entire domain (worst case). Recovery takes 6-12 months and is not guaranteed. The math:

  • Set up cloaking on cheap domains you don't care about
  • Run them until they get caught (typical: 3-12 months)
  • Move to a fresh domain
  • Rotate

This is why authority infrastructure (PBN backlinks, link rotation) matters — you need new domains ranking constantly to replace burned ones.

When to use SEO cloaking vs ad cloaking

  • Ad cloaking — paid traffic, runs while platforms tolerate the ads. Lifetime: weeks to months per campaign.
  • SEO cloaking — organic traffic, builds slowly but compounds. Lifetime: months to years per page until caught.
  • Combined — top operators run both, treating them as different acquisition channels.
Run this in production

Stop running cloaking on duct tape.

Overcloak ships the 11-layer detection stack described above out of the box. $97/mo locked forever for the first 50 customers — only 13 founder seats left.

// keep reading