What is cloaking?

In Google's spam policy, cloaking means presenting different content to search engines and people to manipulate rankings and mislead users. The definition concerns deceptive purpose as well as the content difference. A pair of different screenshots is a reason to investigate, not enough evidence by itself to establish cloaking.

Google's cloaking policy includes crawler-only keyword insertion as an example. Its broader enforcement guidance describes automated detection and human review when needed; violating pages may lose visibility. It does not establish an automatic manual action for every difference a site owner observes.

Identify what changed for the reader

Start with the information someone came to find. If a product-support page promises setup instructions, compare whether those instructions remain available in each view. A collapsed navigation menu and a replacement of the instructions with unrelated material raise different questions. Record the actual difference before assigning a cause.

Separate your observations from your assumptions. “The logged-out browser showed a sign-in screen” describes a result. “Google penalized the page for cloaking” asserts both a policy finding and an enforcement outcome. The second statement needs evidence beyond the first screenshot.

Compare captures under recorded conditions

Ask the maintainer to capture the affected URL with the request conditions recorded: device or user agent, signed-in state, relevant cookies, entry URL and time. Keep the response, redirect destination and rendered view together. A screenshot without its URL or session context makes the difference harder to reproduce.

Change one condition at a time where practical. If the first capture uses a signed-in desktop browser and the second uses a clean mobile session, several explanations remain open. Write down which comparison you actually made rather than describing it as a test of crawler behavior.

Different HTML can serve a legitimate device layout

Google's mobile-first indexing guidance describes dynamic serving: one URL can return different HTML for different devices using user-agent detection and the Vary response header. It also recommends equivalent primary content across mobile and desktop. Matching every byte is not the objective of that guidance.

A fictional comparison worksheet

Imagine a support team checking a fictional appliance setup page. These observations are examples of evidence to collect, not findings about a real website or predictions of a search penalty.

Example observations and useful follow-up questions
Observed differenceRecord nextQuestion for the maintainer
Instructions appear beneath a collapsed panelThe panel state and the text available after opening it.Is the content accessible through the intended interface?
One session shows an access screenLogin state and the destination after authorized access.Which audience is this page intended to serve?
A request returns unrelated materialThe exact response, entry URL and conditions that reproduce it.Which rule, application or unauthorized change produced this response?

Check access rules in their actual context

Google's policy allows gated content under stated conditions: Google must see the full material available to authorized readers, and the publisher must follow its Flexible Sampling guidance. That exception is conditional. Use the linked policy when reviewing a paywall instead of applying a blanket rule that every visitor must receive identical access.

Write the intended behavior beside the observed behavior. Identify who owns a login rule, device template or content gate, and have that owner explain the difference. Keep policy interpretation separate from a legal assessment of access restrictions; this glossary entry does not determine whether a particular restriction is lawful.

Check the manual-action report before naming a penalty

A Google manual action follows a human review finding that pages violate its spam policies. Google reports these actions in Search Console and its message center. If an action is present, use its stated issue and scope to guide the investigation rather than inferring them from a traffic chart.

Google's review instructions call for correcting the listed issues across affected pages and documenting the changes before requesting review. Follow the instructions for the action actually reported. A glossary definition cannot establish the cause of a particular site's traffic decline or promise a recovery date.

Give the responsible team a reproducible record: affected URLs, captured differences, relevant access rules, the owner of each fix and any actual Search Console notice. After a change, repeat the same comparison and save the result. Describe what was corrected without claiming that the change restored rankings unless separate observations support that conclusion.

The JavaScript SEO entry explains content delivery and rendering questions. Those checks can help locate missing information. The policy question still requires examining the purpose and effect of the different content, rather than treating a rendering test as a verdict.

Sources and scope

This entry uses Google's public documentation and an invented support-page worksheet. It does not describe Google's undisclosed detection systems, report a customer incident or provide a forensic diagnosis. Keep the comparison record available for the people who can inspect the site's actual configuration.