Google has just clarified a fundamental rule regarding the use of structured data: it must strictly reflect what is visible to a non-logged-in user. This directive aligns with the logic of consistency between what the bot sees and what the user sees.

Concretely, if you manage an e-commerce site where prices only display after login, you must not include these prices in your Schema.org markup. The same rule applies to any conditional information: member-only stock availability, hidden complete descriptions, or any other protected content.

This requirement aims to prevent structured cloaking practices, where search engines would receive enriched information while users would see impoverished content. Google considers this a form of manipulation likely to mislead.

• Transparency principle: structured data = publicly visible content
• No markup for authenticated content: prices, stock, descriptions reserved for members
• Possible sanctions: loss of rich snippets, algorithmic penalties, ranking demotion
• Bot-user consistency: what Googlebot reads must match the logged-out visitor experience

This position is perfectly consistent with Google's historical philosophy on cloaking and manipulation. For years, the search engine has penalized any divergence between what is served to bots and users. Structured data is no exception to this rule.

However, an important nuance: certain business models legitimately require authentication. In these cases, the solution is not to cheat with markup, but to adapt your strategy. You can mark up only public information (product name, category, image) and omit price/availability fields. B2B or quote-based sites have operated this way for a long time.

In practice, Google's testing tools only see the logged-out version. If your rich snippets currently work with hidden content, it's probably because your implementation inadvertently exposes this data to Googlebot, which remains risky.

• Audit your structured data immediately: verify in private browsing that all marked-up information is publicly visible
• Test with Google's Rich Results Test tool to identify discrepancies between markup and public display
• Fix automatic implementations: disable Schema.org field generation for authenticated content in your CMS/plugins
• For e-commerce sites requiring login: mark up only name, public description, category, images – omit price, availability, offers
• Document your strategy: create a clear matrix defining which Schema fields are authorized according to page/content type
• Train technical teams: educate developers and integrators about this rule during site evolutions
• Monitor rich snippets: watch Search Console to detect any sudden loss of rich snippets, a potential signal of non-compliance
• Plan a redesign for complex sites: if your current architecture mixes public and private content, consider a clearer separation