Google now requires labeling "adult" products in feeds — and what it has to do with iGaming

Google rolled out a requirement that most people will scroll past. That's a mistake.

Products falling under the adult-oriented content policy now need to be explicitly flagged in your Merchant Center feed — either through the adult attribute in your XML feed, or through the hasAdultConsideration structured data markup. Source: Search Engine Roundtable, confirmed as Google's official position. On the surface, this looks narrow — it only touches Google Shopping and shopping features, organic search isn't affected. But I wouldn't be so quick to write it off.

Why this isn't "just another attribute"

The mechanics here are simple. Google wants to know in advance what it's showing users, so it can filter by age, region, and safe search settings. Without the markup, your product either never makes it into Shopping results, or gets rejected after a manual or automated review. This isn't a suggestion you can skip. It's an entry condition.

I've seen e-commerce projects lose their spot in shopping features more than once — not because of content quality, but because of formal mismatches in the feed: wrong attribute, wrong category, a missing required field. Google Merchant Center has zero tolerance for ambiguity. Either you follow the rules to the letter, or your product disappears silently, with no real explanation. The adult content markup works exactly the same way.

What to actually do

If you run or manage e-commerce with 18+ products — here's the order of operations.

First, check whether your catalog falls under Google's adult-oriented content policy. The policy is written broadly, and it doesn't just cover the obvious stuff like lingerie or adult products — sometimes adjacent categories get swept in too. Next, add the adult attribute to your Merchant Center XML feed for every item that qualifies. At the same time, it's worth adding hasAdultConsideration structured data to the product pages themselves. That's not duplication — it's insurance. Different Google systems read different signal sources.

And here's the last step people somehow always skip: after making the changes, verify the markup actually made it into the live feed — not just the test version. Rejected products don't come back to Google Shopping instantly. There's a delay, and that delay means real lost traffic and lost sales while you wait.

What this has to do with iGaming

There's no direct link to gambling or betting here — Google Shopping doesn't sell bets. But the principle behind this requirement should feel painfully familiar if you work in igaming. Google is methodically pushing for explicit, honest labeling of content in sensitive categories. That's the exact same logic behind the requirements for gambling content markup, age disclaimers, and responsible gambling blocks on affiliate sites.

Google doesn't tolerate ambiguity. The clearer your signal to both the search engine and the user about what category your content belongs to, the lower your odds of manual penalties and rejections — whether that's a product feed or a betting affiliate site. The rule works exactly the same way in e-commerce and in affiliate marketing.

Bottom line

On paper, this is a narrow technical requirement about Merchant Center. In reality, it's one more confirmation that Google is building an increasingly strict system of explicit signals for sensitive content. Ignore changes like this, and you lose traffic quietly, with no warning — simply because your feed or markup didn't keep up.

If you're running e-commerce with 18+ products, or a project in an adjacent niche — check your markup now, before products start dropping out of search results. If you need help with a structured data audit or the technical side of SEO, that's a dedicated part of what we do — you can check it out here.