Redirect cloaking is when a URL sends crawlers to one page and real visitors, through a redirect, to a different page. Google’s name for it is “sneaky redirects”.
What Google says
Sneaky redirecting is “the practice of doing this maliciously in order to either show users and search engines different content or show users unexpected content”. Examples: showing search engines one type of content while redirecting users to something significantly different; showing desktop users a normal page while redirecting mobile users to a completely different spam domain (Google spam policies).
Google Ads adds click trackers: using them “to redirect people to websites with content prohibited by Google Ads’ policies” is an example of cloaking (Google Ads policy).
How it works
The redirect is the delivery step. The decision comes from the usual signals (IP, user agent, referrer, country). The Google study of cloaking notes that detection approaches fetch pages through multiple browser profiles and examine divergent redirects, including JavaScript, 30X and meta-refresh (Cloak of Visibility).
How to spot it
Compare the redirect chain per view: the hops, status codes and final URL. Run the views with the website cloaking checker, or by hand:
curl -s -o /dev/null -L -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" -w '%{num_redirects} %{url_effective}\n' "$URL"
More in the curl guide.