Cloaking & Content Parity

01 The Rule

Never serve different content to search engine crawlers than to users. The content, structure, and links visible to Googlebot must be identical to what users see. Dynamic rendering is acceptable only when the rendered output is equivalent.

02 Rationale

Cloaking — showing different content to crawlers — is a violation of search engine guidelines that can result in manual penalties and deindexation. Even unintentional cloaking (geo-based content, A/B tests visible to crawlers) can trigger quality issues.

03 Implementation

• Serve identical HTML to all user agents including Googlebot
• If using dynamic rendering, ensure output matches client-side render exactly
• Don't serve different content based on IP geolocation to crawlers
• A/B tests must serve the original to crawlers, not variants
• Use the URL Inspection tool to compare rendered vs served content

04 Common Violations & Consequences

05 The Fix

Audit your server configuration for any user-agent or IP-based content switching. Verify with Google's URL Inspection tool that what Googlebot sees matches user experience. Remove any crawler-specific content overrides.