Google has made its requirements for adult-oriented ecommerce products much more explicit. Its Search Central guidance now tells merchants optimizing for Google Shopping features to identify adult products through either the Merchant Center adult attribute or the hasAdultConsideration property in Product structured data, giving ecommerce teams a clear machine-readable route for declaring content that is subject to age and country restrictions.
The requirement appears in Google's SEO guidelines for explicit content, where a dedicated ecommerce section now says adult-oriented products should be labeled in ecommerce feeds or markup. This connects Google's explicit-content guidance directly with its Shopping and merchant-listing systems rather than leaving adult-product identification as a concern confined to Merchant Center feed documentation.
Merchants now have two explicit labeling routes
For merchants using Merchant Center feeds, Google points to the existing adult attribute. For sites relying on on-page structured data, the corresponding mechanism is hasAdultConsideration within Product markup. Google's current merchant listing structured data documentation states that merchants selling products considered adult-oriented under Google's policy must use this property to label them appropriately.
Google Search currently supports https://schema.org/SexualContentConsideration as the relevant value for hasAdultConsideration. Schema.org defines a broader AdultOrientedEnumeration vocabulary, but Google's merchant-listing documentation specifically identifies SexualContentConsideration as the supported value for this Shopping use case. The same requirement is documented for individual products within Google's Product variant structured data guidance.
This is important because feed data and structured data can serve overlapping merchant-discovery workflows. A retailer that does not rely exclusively on a Merchant Center feed can still communicate the adult-oriented status of a product directly on the product page in a format Google understands.
The label is about Shopping eligibility and restrictions, not an organic Search penalty
Google makes a crucial distinction in the explicit-content guidance: labeling an adult product for Shopping does not affect the site's visibility in ordinary organic web search results. The purpose is to let Google identify which commercial items require the restrictions associated with adult-oriented content when those items participate in Shopping experiences.
Google says properly labeled adult-oriented products can still be eligible for Shopping ads and free listings, subject to age- and country-based restrictions. The structured signal therefore should not be interpreted as a blanket exclusion mechanism. It is a classification mechanism that allows Google to decide when and where the product can legally and appropriately be shown to shoppers.
That distinction matters for ecommerce SEO teams that may otherwise hesitate to mark content accurately out of concern that the label itself will suppress normal rankings. Google's documentation explicitly separates the Shopping labeling requirement from organic web-search visibility.
Google introduced hasAdultConsideration to close the feed-markup gap
The structured-data side of this system is relatively recent. Google's Search documentation changelog records the addition of hasAdultConsideration to merchant-listing and Product-variant structured data on May 20, 2026. Google said the reason was to bring Product markup into parity with the Merchant Center feed specification for the adult attribute.
That change established the technical property. The explicit-content guidance now makes the operational expectation easier for merchants to understand: if an ecommerce site is optimizing adult-oriented products for Shopping features, those products need to be identified in the feed or in the markup. The result is a more coherent rule across Merchant Center and Search Central documentation.
This is a structured-data compliance issue, not just a content warning
Historically, adult-content SEO guidance has often focused on page-level signals, SafeSearch, age gates and the organization of explicit content on a site. Those considerations remain relevant. Google's explicit-content documentation recommends, among other things, allowing Googlebot to crawl without an age gate, grouping explicit pages appropriately and marking explicit pages with metadata.
Ecommerce introduces an additional layer because Google is not merely indexing a page; it may be transforming structured product information into merchant-listing and Shopping experiences. Price, availability, product identifiers and other attributes can be consumed as machine-readable commerce data. Adult status now sits clearly inside that structured product-data model as well.
For retailers, that means a visual “18+” badge on the page should not be treated as a substitute for the data signal Google requests. Human-readable disclosure and machine-readable classification solve different problems. Google needs the latter to apply its Shopping restrictions consistently.
Product feeds and page markup should agree
Merchants using both Merchant Center and Product structured data should audit the consistency of the two sources. If a product is declared adult-oriented in a feed but the corresponding page markup omits or contradicts that classification, the retailer is creating unnecessary ambiguity in a system where Google can consume information from both channels.
A practical implementation is to make adult status a first-class field in the ecommerce catalog rather than adding it manually at the export stage. The same internal product flag can then drive the Merchant Center adult attribute, the appropriate hasAdultConsideration markup and any customer-facing age or content controls required by the merchant's own compliance process. That reduces the risk that newly added products bypass one of the required data outputs.
Sites with product variants deserve particular attention because Google explicitly documents hasAdultConsideration in its variant guidance. Ecommerce platforms generating ProductGroup and nested Product entities should make sure the adult classification reaches the relevant product records instead of being lost in variant-generation logic.
Google is making ecommerce markup increasingly operational
The update also illustrates how Product structured data is evolving beyond decorative rich-result optimization. Google has steadily aligned on-page product markup with Merchant Center concepts, including categories, sale-price timing and other commerce attributes. Adult classification follows the same pattern: information once associated primarily with a merchant feed now has an explicit schema-based equivalent on the website.
That makes structured data part of ecommerce operations and compliance, not merely an SEO enhancement. A malformed or missing property can affect Google's understanding of whether a product should participate in a particular Shopping experience and under what restrictions, even though correct markup never guarantees that Google will display a specific rich result or merchant feature.
Adult ecommerce sites should audit their catalog data now
For merchants selling products covered by Google's adult-oriented content policy, the action is relatively clear. Check whether those products are explicitly identified in Merchant Center with the adult attribute, in Product structured data with hasAdultConsideration, or through both systems where both are used. Then verify that the classification remains consistent across variants and new catalog additions.
The update is easy to overlook because it lives in documentation rather than a major product announcement, but it creates a concrete technical requirement for a category of ecommerce sites. Google no longer leaves adult-product identification as an implicit Shopping-policy concern: it now tells merchants exactly where to declare it in the data layer. For adult ecommerce SEO, that turns compliance into a structured product-data task that belongs alongside price, availability and other core catalog attributes.