Opens in a new tabSkip to content
Agent LighthouseAgent Lighthouse

    Searches the text of every published page. The evidence sources themselves are not in this index — search all of them on the trusted sources page.

    GitHub ↗
    Browse checks and page contents
    agentic-commerce/offer-schema

    Offer schema on pricing pages

    What it checks

    AI agents use Offer schema to answer pricing queries with exact numbers. Without price and priceCurrency in structured data, agents must scrape and guess pricing from page text, which often produces inaccurate or outdated results in AI-generated comparisons.

    Why it matters

    Google’s product data extractors parse price and priceCurrency out of the schema.org Offer in a product page’s markup. They use those exact values for merchant listing eligibility, and for Merchant Center automatic item updates. A page without them cannot supply a machine-read price to that pipeline.

    Evidence

    • Google merchant listing structured data — required properties are Product name, image, offers, and on the Offer price (or priceSpecification.price) plus priceCurrency (or priceSpecification.priceCurrency); availability, priceValidUntil, hasMerchantReturnPolicy are recommended — developers.google.com/…/merchant-listing (verified 2026-08-21)
    • Automatic item updates: “We automatically read the structured data markup on your website using our advanced data extractors and directly pull product data from your HTML into Merchant Center”. It names price and priceCurrency directly on the Offer, or via priceSpecification — support.google.com/…/3246284 (verified 2026-08-21)
    • “Structured data lets Google and other web platforms automatically read your site and directly pull product data from your HTML”; markup also powers the website-crawl feed input method — support.google.com/…/6069143 (verified 2026-08-21)
    • Merchant Center price attribute: “Accurately submit the product’s price and currency, and match with the price from your landing page, structured data, and at checkout” — support.google.com/…/7052112 (verified 2026-08-21)
    • Product snippets accept offers as either Offer or AggregateOffer — developers.google.com/…/product-snippet (verified 2026-08-21)
    • schema.org defines AggregateOffer with lowPrice/highPrice/offerCount for the multi-offer case; no price is mandated — schema.org/AggregateOffer (verified 2026-08-21)

    Limits

    No LLM-assistant vendor documents reading on-page Offer markup. Google states of its AI features: “You don’t need to create new machine readable files, AI text files, or markup to appear in these features. There’s also no special schema.org structured data that you need to add” (developers.google.com/…/ai-features, verified 2026-08-21). OpenAI’s commerce documentation routes product price and availability into ChatGPT through a product feed: “Provide a structured product feed so ChatGPT accurately indexes and displays your products with up-to-date price and availability”. It never mentions schema.org page markup (developers.openai.com/commerce and developers.openai.com/…/feed, verified 2026-08-21). The proven consumer path is Google’s search/shopping pipeline, not a chat agent parsing the page.

    How it scores

    offers.price and offers.priceCurrency are the only required Offer properties in Google’s merchant listing structured-data spec, and Google separately documents crawling that markup off the page HTML to correct price data.

    Sources