Cloaking

Definition: Google's spam policies define cloaking as presenting different content to users and search engines with the intent to manipulate search rankings and mislead users. It includes serving materially different topics or inserting text only for search-engine requests.

Key facts

• As of 17 October 2026, Google's spam policies list cloaking as a violation; sites that violate those policies may rank lower or disappear from search results.
• Google's dynamic rendering documentation accepts crawler-specific rendering that produces similar content, while treating completely different content as potential cloaking.
• Google's paywalled content documentation uses structured data to help distinguish subscription content from cloaking.
• The URL Inspection tool provides page code and, after a successful live test, a screenshot of the page seen by Google-InspectionTool, Google's inspection crawler.

What does Google's policy identify as cloaking?

Google's cloaking policy gives an example of a page about travel destinations shown to search engines while visitors receive a page about discount drugs. It also identifies inserting text or keywords only when the request comes from a search engine.

The policy includes intent in its definition: manipulating search rankings and misleading users. It also warns that hackers may use cloaking to conceal a compromise from the site owner. A suspected mismatch therefore warrants checking for unauthorized changes as well as reviewing deliberate crawler-specific content rules.

Google describes automated detection and human review that can result in a manual action, meaning a policy enforcement action following human review. Its stated consequences include lower rankings or exclusion from results.

How do rendering and paywalls differ from cloaking?

Dynamic rendering means detecting crawlers and serving them a rendered version of a page while visitors receive a version rendered in their browser. Google's dynamic rendering guidance says similar content is acceptable. Its contrasting example serves cats to users and dogs to crawlers. Google describes dynamic rendering as a workaround with additional complexity and resource requirements.

A paywall restricts content to people with subscription or registration access. Under Google's spam policies, this arrangement falls outside cloaking when Google sees the full content available to authorized readers and the publisher follows its linked Flexible Sampling guidance.

Google's paywall markup guide identifies restricted sections through structured data, machine-readable descriptions embedded in the page. This fragment from its article example marks a section selected by the CSS class .paywall:

"isAccessibleForFree": false,
"hasPart": {
  "@type": "WebPageElement",
  "isAccessibleForFree": false,
  "cssSelector": ".paywall"
}

The fragment belongs inside the article's structured data. The guide requires class selectors for cssSelector and a corresponding class around the restricted content.

How can a website check for a mismatch?

Google's URL Inspection documentation describes Test live URL, followed by View tested page. The additional response data includes returned HTML, HTTP headers, JavaScript output and loaded resources; the Screenshot tab shows the rendered page after a successful live test.

A practical review compares that output with the content available to visitors at the same URL. For a subscription page, the relevant comparison includes the article available to an authorized reader. Review crawler-only text and topic changes against Google's examples. The live test checks access and rendering; it does not check compliance with quality guidelines or the presence of manual actions.

Related terms

• Dynamic rendering
• Subscription content markup
• Googlebot
• Rendered DOM

FAQ

Is serving static HTML to a crawler cloaking?

Google's dynamic rendering documentation says Googlebot accepts similar content produced through dynamic rendering. Compare the substantive content available to the crawler and to visitors.

Can a paywalled article give Google full access?

Yes. Google's spam policies allow this when Google sees the full content available to authorized readers and the publisher follows its Flexible Sampling guidance.

Can cloaking indicate a hacked site?

Yes. The same spam policies warn that hackers use cloaking to make unauthorized changes harder for site owners to detect.

Sources

1. Google Search Central, "Spam policies for Google web search", updated 28 August 2026
2. Google Search Central, "Dynamic rendering as a workaround", updated 10 December 2025
3. Google Search Central, "Subscription and paywalled content", updated 8 September 2026
4. Google Search Console Help, "URL Inspection tool", accessed 17 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer