Visibility guide

Structured Data for E-commerce and AI Search

Treat product, offer, shipping, and return markup as a governed commerce-data contract. It can support eligibility and understanding, but it never guarantees a rich result, ranking, or AI citation.

Published: Jul 15, 2026
Updated: Jul 15, 2026
Reading time: 14 min read

On this page

Structured data is machine-readable information that helps search systems interpret eligible pages. For ecommerce, the durable work is aligning visible product data, JSON-LD, feeds, policy pages, and operational source systems. Google explicitly states that its AI features have no extra technical requirements or special schema type, and inclusion is not guaranteed.

Overview

Outcome

Establish a release-tested schema program for Product, Offer, variants, shipping, returns, and organisation data that remains accurate when price, availability, policy, or rendering changes.

Model the product and commercial offer separately

Use Product for the item and Offer for its purchasable state: price, currency, availability, condition, and canonical offer URL. Where variants have distinct commercial attributes, model the group and variant-specific products truthfully rather than emitting one misleading price or availability.

The commerce data contract

Commerce source
Price, availability, identifiers, shipping, returns, and variant state are maintained.
Rendered product page
A shopper sees the same material information used in markup.
JSON-LD and feed
Structured representations are generated from the approved contract.
Validation
Rendered output, Search Console, and data-quality checks expose drift.

One governed source should drive the product page, JSON-LD, feed, policy content, and monitoring checks.

Publish policy data at the right level

Use organisation-level return and shipping policy markup for the standard merchant policy. Use offer-level markup only for genuine product-specific exceptions. Keep countries, fees, methods, delivery windows, and seasonal changes aligned with visible policy and Merchant Center data; Google documents a precedence order when these sources disagree.

Data	Preferred scope	Release owner
Product identity and variants	Product page	Commerce/catalogue team
Price and availability	Offer	Pricing and inventory system
Standard shipping and returns	Organisation policy	Operations and legal review
Product exception	Offer	Product and fulfilment owner

Representative release check

product=SKU-101
visible_price=129.00 EUR  jsonld_price=129.00 EUR  status=match
visible_availability=in_stock  jsonld_availability=in_stock  status=match
return_policy=EU-30-day  policy_source=approved  status=match
rendered_jsonld=present  rich-results-test=valid

Validate rendered output, not application intent

Google supports JSON-LD and recommends it because it is easier to maintain at scale. JavaScript may inject it, but Google processes crawling and rendering separately. Validate representative rendered HTML in Rich Results Test and URL Inspection, confirm a 200 indexable canonical URL, and ensure critical data is not hidden behind session, geolocation, consent, or blocked API calls.

Use content-fingerprinted JavaScript assets. Googlebot may use cached resources, so a changed asset should receive a changed URL rather than relying on cache-control alone. Do not use FAQPage as a new ecommerce-rich-result tactic: Google's FAQ rich-result feature was deprecated in 2026.

Measure eligibility without promising AI visibility

Monitor Merchant Listings and structured-data reports, errors, manual actions, feed parity, and affected landing pages. Use before-and-after analysis with a documented release date. Say that accurate visible structured data can support eligible merchant and rich-result experiences; do not say it guarantees AI Overviews, AI Mode links, rankings, citations, or sales.

Troubleshooting

Structured-data failure modes

JSON-LD price, availability, shipping, or return policy disagrees with visible content.
Variant markup collapses distinct offers into one incomplete product.
Client rendering leaves crawlers without the fields present in a browser session.
A team adds hidden, stale, or review markup that is not representative of the page.

Authoritative references

Make commerce data consistent across search surfaces

Optimi can help connect rendered-page checks, edge delivery, crawl evidence, and technical SEO governance around your product data.

Review structured data