On May 20, 2026, Google added hasAdultConsideration to its Product merchant listing and Product variant structured data documentation. The property labels products that Google treats as adult-oriented, and it brings page markup in line with the adult field in a Merchant Center feed.
The label is for products covered by Google's adult-oriented content policy: sexually suggestive content, nudity, or merchandise meant to enhance sexual activity. It is not an age group or an adult clothing size, so adult shoe sizes and other products made for grown-ups, without that content, do not get it.
If you sell products that fit the policy, add "hasAdultConsideration": "https://schema.org/SexualContentConsideration" to their Product markup and set adult to yes in your Merchant Center feed. If none of your products fit, this update asks nothing of you.
What Google changed on May 20, 2026
Google's Search documentation updates page records the change in one line: "Added hasAdultConsideration to product-related structured data types." The entry points to the merchant listing structured data page, the Product variant structured data page and the Merchant Center adult attribute page.
Google gives the reason as parity. It says the addition "brings parity with the Merchant Center feed specification for the adult property." In practice, the page markup and the feed can now describe an adult-oriented product in the same way.
Schema.org defines the vocabulary separately. The property takes a value from AdultOrientedEnumeration, and Schema.org lists several members, including AlcoholConsideration, TobaccoNicotineConsideration and SexualContentConsideration. Google Search documents only one value for this property: https://schema.org/SexualContentConsideration. Use that exact value for products that qualify, and read the hasAdultConsideration definition for the vocabulary side.
Which products get the label
Add the property to a product page when Google's adult-oriented content policy applies to the product and shoppers can buy it from that page. Google's merchant listing documentation says products considered adult-oriented under that policy must be labeled with this property. A store that sells a mix of products labels the ones that qualify and leaves the rest alone. Merchant Center also offers an account-level adult-content setting for sites that are adult-oriented overall.

Leave the property off in these cases:
- "Adult" describes only an age group or a clothing size. Merchant Center has a separate
age_groupattribute for demographic sizing and age targeting. - The product is ordinary merchandise with no adult-oriented content.
- The label would not match what the page visibly shows.
- Google's policy prohibits the product. A label does not make prohibited content eligible.
Product variants follow the same rule. Google's Product variant documentation covers the label for variants described with ProductGroup and nested Product items, so label each variant that qualifies. Google also says eligible adult-oriented products can appear in Shopping ads and free listings, subject to age and country restrictions.
Product JSON-LD before and after
The two examples below describe the same fictional product. The first is the markup a page might have carried before the May 20 update. The second adds hasAdultConsideration beside the name, image, description, brand and SKU, with the offer after it. They are for reading and adapting in your own template; replace every value with your own product's details and keep the demonstration values out of your real pages.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Velvet Nightwear Set",
"image": [
"https://example.com/images/velvet-nightwear-set.jpg"
],
"description": "A fictional velvet nightwear set sold through Example Store.",
"sku": "EX-NIGHT-001",
"brand": {
"@type": "Brand",
"name": "Example Brand"
},
"offers": {
"@type": "Offer",
"url": "https://example.com/products/velvet-nightwear-set",
"price": 49.99,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
}
}The version below is the same product with the new property added.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Velvet Nightwear Set",
"image": [
"https://example.com/images/velvet-nightwear-set.jpg"
],
"description": "A fictional velvet nightwear set sold through Example Store.",
"sku": "EX-NIGHT-001",
"brand": {
"@type": "Brand",
"name": "Example Brand"
},
"hasAdultConsideration": "https://schema.org/SexualContentConsideration",
"offers": {
"@type": "Offer",
"url": "https://example.com/products/velvet-nightwear-set",
"price": 49.99,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
}
}Google's documentation places the property on Product, so the example does the same. Write the value as the full URL string in straight quotes. For Google's merchant listing feature, name, image, offers, price and priceCurrency are required, while description, brand, sku, availability, url and itemCondition are recommended. Every value should match what the visible page shows.
If your theme or a plugin already prints Product JSON-LD, add the property to that output instead of adding a second Product block for the same item. The guide to adding schema markup and the guide to schema markup on WordPress cover where that output usually comes from. For complete examples of other types, see the JSON-LD schema examples and the guide to types of schema markup. The Product schema generator builds Product JSON-LD from the details you enter, and you can compare its output with your own markup.
Match the Merchant Center feed
Merchant Center's adult attribute accepts yes, true, no and false. Google says the attribute is required when an individual product is adult-oriented, and an affected product uses adult: yes. In a plain feed or a spreadsheet, the value looks like this:
adult: yesIn an XML feed, the same value is written as a tag:
<g:adult>yes</g:adult>Merchant Center's adult attribute page maps the feed field to Offer.hasAdultConsideration, which is why the property exists on both sides. The product data specification lists the attribute among the others a feed can carry. Keep the page and the feed in step, so a product marked adult-oriented in one is marked the same way in the other.

Shopify and WooCommerce notes
On each platform, the feed setting and the page markup are two separate things. Changing one does not change the other, so inspect the rendered product page after you change either.
Shopify's documentation describes how the Google and YouTube channel sends product data to Merchant Center, and its page on syncing products covers product errors after a sync. Open the channel in your store to see which Google feed fields it can send, then look at the JSON-LD your theme prints on a product page to see whether the property is there.
WooCommerce lists Adult as an available Google product attribute in its attribute mapping documentation. The documented route is:
- In WordPress Admin, open Marketing, then Google for WooCommerce.
- Open the Attributes tab and create an attribute rule.
- Select Adult as the attribute.
- Map a global WooCommerce product attribute, or set an appropriate fixed value.
- Save the rule.
- Review the Product Feed and Product Issues tabs.
That rule controls the Merchant Center feed. It does not by itself put hasAdultConsideration into the page's JSON-LD, so view the rendered product page separately and look for the property.
Check Microsoft and Yandex before you send products
Microsoft's Merchant Center products resource has its own adult Boolean field and says adult products are not supported and will be rejected. That is a product feed rule, so check it before you send adult-oriented products to Microsoft.
Bing and Yandex read Product markup too. Yandex documents Product and Offer markup and a structured data validator, and says it may skip unsupported markup. Keep the visible product details accurate and the Product markup valid. For how AI search systems treat markup, see whether AI systems use schema markup.
Test the live page
Work through the page in this order after you deploy the change:
- Confirm the visible title, description, images, price, availability and purchase path.
- Add
hasAdultConsiderationto theProductJSON-LD. - Confirm the value is exactly
https://schema.org/SexualContentConsideration. - Validate the JSON syntax.
- Run the page through Google's Rich Results Test.
- Inspect the URL in Google Search Console.
- After Google recrawls the page, check the Merchant listings report.
- Check Merchant Center diagnostics and confirm the feed's
adultvalue.
Each check answers a different question. A valid JSON syntax check says the code parses. The Schema.org vocabulary says the property and value exist. Google's feature requirements say whether the page qualifies for merchant listings. Whether Google shows the page in a given result is a fourth question that none of the earlier checks settles.
Limits to keep in mind
Correct markup does not guarantee a rich result, Shopping placement, ranking, traffic or a particular display. Google says the same about structured data in general, and the label is no exception. It describes the product so Google can apply its adult-oriented content policy, including the age and country restrictions that eligible products stay subject to.
Confirm country-specific eligibility before you assume a product can appear on a Shopping surface in every market you sell in. For a store with a single adult-oriented product line, the work is small: one property on each qualifying product page, one matching feed value, and one pass through the checks above.
Questions people ask
Is hasAdultConsideration required for every product?
No. Google requires it for products that fall under its adult-oriented content policy. A store's other products leave it out, and a store with no such products has nothing to add.
Should the property go on Product or Offer?
Schema.org lists the property for both Product and Offer. Google's documentation places it on Product, and Merchant Center maps its feed attribute to Offer.hasAdultConsideration. Follow Google's Product example on the page.
Can adult-oriented products appear in Google Shopping?
Google says eligible adult-oriented products can appear in Shopping ads and free listings, subject to age and country restrictions. Products its policy prohibits stay ineligible, with or without the label.
Does Bing accept adult products?
Microsoft's Merchant Center products resource has an adult field and says adult products are not supported and will be rejected. Read Microsoft's policy for your products before you send them, since this is a feed rule and Google's markup change does not alter it.
Will the property improve rankings?
Google does not guarantee any ranking, traffic or display from structured data. The property labels a product for policy handling, so its job is accuracy, and the visible page should say the same thing.
