Why cloaking matters
Search engines crawl your site to build their index. If their crawler sees something different from what users see, they can demote or deindex the page, even when the intent is harmless. Serving any variant to Googlebot, including a “better” one, crosses that line.Guarantee 1: search crawlers always get your real page
These crawlers always receive your normal page, exactly as a human visitor would:
This check runs before anything else. It is not a setting: changing your serve mode or enabled purposes cannot turn it off. Bluemoon maintains the list, and your install picks up changes without a redeploy.
Why Google’s AI answers are covered too
Google AI Overviews run on the same Googlebot and the same index as Google Search. There is no separate crawler to target. A different page served to Googlebot would be what both Search and AI Overviews see, so there is no way to optimize for one without cloaking the other. That is why the rule has no exceptions.Guarantee 2: same substance, different form
The optimized version changes the form of your content, never the substance.What changes
Form. Your content is reorganized answer-first, with structured data, so answer engines can pick out facts without parsing your HTML.
What stays the same
Substance. Every claim comes from your page. If Bluemoon can’t produce a version that sticks to your page, none is served. When your page changes, you regenerate it.
Who gets what
Answer-engine crawlers power AI-generated answers, not organic search results, so serving them a different format of the same content is not cloaking.
You choose which purposes are eligible with the
ENABLED setting. See Serve modes.
Related
Serve modes
How to go from logging only to serving verified crawlers.
Agent analytics
See which crawlers visit your site, how they were verified, and what they were served.