SEO Cloaking
Presents search engine crawlers with different content or URLs than what human visitors see, typically to manipulate rankings.
If you have ever accidentally served a different page to a crawler during testing, you know that the line between cloaking and legitimate dynamic serving is thinner than most tutorials admit.
Key points
- Check your site with an SEO cloaking checker before changing any serving logic.
- Do not use IP or User-Agent detection to serve different SEO-critical content.
- If your page varies by device, location, or login, ensure primary content is equivalent.
- Treat any hidden bot-only text or links as a policy violation, not a tactic.
- Use Search Console's URL Inspection tool to compare what Google sees with what you see.
A travel site loses its ranking overnight
A hotel booking site used User-Agent detection to show Google a page full of keyword-rich descriptions, while human visitors saw a simple booking form with no text. This website cloaking technique is a classic black hat seo tactic, often combined with doorway pages. After Google's algorithms updated to render JavaScript more thoroughly, the mismatch was detected. The site lost all organic traffic from Google within two weeks and received a manual action. The owner had to remove the cloaking logic and rebuild the visible pages with equivalent content, a process that took months.
Three ways cloaking is detected
- IP address check Google may compare the IP of the crawler versus the IP of a typical user; a mismatch in content served to different IPs flags cloaking.
- User-Agent headers Serving different content to different User-Agent strings (e.g., Googlebot vs. Chrome) is a direct red flag and easily tested.
- Page source comparison Tools fetch the page as Googlebot and as a browser, then compare the rendered HTML for differences in text, links, or metadata.
Three things cloaking is not
- Responsive design The same main content, just rearranged for screen size. Users and crawlers see equivalent text and links, so it does not violate Google's spam policies.
- Dynamic serving Content that changes based on device but is equivalent in meaning and value. Google's guidelines allow this if the main content matches.
- A/B testing Showing different variants to users for testing, but the crawler sees the same or a control version; not intended to manipulate rankings.
Common questions
Is cloaking ever legitimate?
No, cloaking is never legitimate under Google's guidelines; it violates spam policies and can lead to penalties.
Is the 'cloaked' app related to SEO cloaking?
No, the 'cloaked' app is unrelated to SEO cloaking; it is a separate privacy tool.
Sources
- Google Search Essentials / Spam policies Official policy on cloaking and other deceptive practices.
- Google Search Central - Cloaking and sneaky redirects Specific section on cloaking definition and examples.
- Google Search Console Help - URL Inspection How to use the tool to check what Google sees.