Product and FAQPage schema for Shopify in 2026

Schema markup used to be a nice-to-have. For classic organic SEO, the practical benefit of adding Product and Review schema was a richer result snippet and a small tiebreak advantage over competitors with incomplete markup. For AI retrieval, the calculus changes completely. The ranker does not browse your page like a human; it ingests your HTML, extracts the structured data, and uses that structured data as the most authoritative facts to quote. A page with no Product schema is forced to rely on natural-language parsing for its specs — and natural-language parsing is brittle, slow, and produces lower-confidence outputs that get deprioritized in the answer.

That measurement is narrow in scope (US English queries, mid-market Shopify stores) but the direction is consistent across every audit we have run. FAQPage schema in particular punches far above its weight because each question-answer pair is a pre-formatted citation candidate — the ranker does not have to extract it, it just has to quote it.

Every modern Shopify theme (Dawn, Sense, Craft, and the third-party majors) renders a ProductJson block on the PDP that exposes SKU, title, description, variants, and images. That is enough for classic Google rich results. It is not enough for AI retrieval — the specific gaps are GTIN, MPN, brand as a linked entity, aggregateRating, and FAQPage. Here is the delta between what Shopify ships and what the AI engines want.

What Shopify ships by default

• Product @type with name, description, and url.
• Offers with price, priceCurrency, availability, and itemCondition.
• Image array with 1-3 images.
• SKU and productGroupID (on variant products).

What you need to add

• GTIN (UPC / EAN / ISBN) — via product metafield, exposed in schema.
• MPN (manufacturer part number) — same mechanism, when GTIN is unavailable.
• Brand as a linked Brand entity, not a plain string.
• aggregateRating with ratingValue, reviewCount, bestRating, and worstRating.
• Full Review array (not just the aggregate) with at least 3-5 reviews for sites with review volume.
• FAQPage schema as a separate @type block covering the 5-8 most-asked shopper questions.
• BreadcrumbList schema linking PDP back to collection and home.

The example below emits Product, FAQPage, and BreadcrumbList as three separate @type blocks inside a single script tag. That is the structurally-cleanest form and the one that plays best with both classic search and AI retrievers. If you need to emit multiple products on a category page, wrap them in an ItemList @type.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Product",
      "@id": "https://kloira.com/products/kairos-chronograph#product",
      "name": "Men's 42mm Moissanite Chronograph — Kairos",
      "description": "A 42mm stainless-steel chronograph watch with a full moissanite-set bezel, Swiss quartz movement, sapphire crystal, and a 10-year limited warranty.",
      "sku": "KAIROS-CHR-42-SS",
      "gtin13": "0850023457892",
      "mpn": "KLR-KAIROS-42",
      "brand": {
        "@type": "Brand",
        "name": "Kloira",
        "@id": "https://kloira.com/#organization"
      },
      "image": [
        "https://cdn.shopify.com/products/kairos-1.jpg",
        "https://cdn.shopify.com/products/kairos-2.jpg",
        "https://cdn.shopify.com/products/kairos-3.jpg"
      ],
      "offers": {
        "@type": "Offer",
        "priceCurrency": "USD",
        "price": "399.00",
        "priceValidUntil": "2026-12-31",
        "availability": "https://schema.org/InStock",
        "itemCondition": "https://schema.org/NewCondition",
        "url": "https://kloira.com/products/kairos-chronograph",
        "shippingDetails": {
          "@type": "OfferShippingDetails",
          "shippingRate": { "@type": "MonetaryAmount", "value": "0", "currency": "USD" },
          "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US" },
          "deliveryTime": {
            "@type": "ShippingDeliveryTime",
            "handlingTime": { "@type": "QuantitativeValue", "minValue": 0, "maxValue": 1, "unitCode": "DAY" },
            "transitTime": { "@type": "QuantitativeValue", "minValue": 2, "maxValue": 5, "unitCode": "DAY" }
          }
        }
      },
      "aggregateRating": {
        "@type": "AggregateRating",
        "ratingValue": "4.7",
        "reviewCount": "142",
        "bestRating": "5",
        "worstRating": "1"
      },
      "review": [
        {
          "@type": "Review",
          "reviewRating": { "@type": "Rating", "ratingValue": "5" },
          "author": { "@type": "Person", "name": "Jordan P." },
          "datePublished": "2026-03-14",
          "reviewBody": "Solid weight, the moissanite catches light beautifully under direct sun. Wore it daily for three months with no visible wear."
        }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Is this watch waterproof?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The Kairos is rated to 5 ATM — suitable for handwashing, rain, and brief swimming, but not for showering or diving."
          }
        },
        {
          "@type": "Question",
          "name": "What size wrist does the 42mm case fit?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The 42mm case fits wrists from 160-210mm comfortably. The stainless-steel band has 12 adjustable links for finer sizing."
          }
        },
        {
          "@type": "Question",
          "name": "How long is the warranty?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Every Kloira watch carries a 10-year limited warranty covering the movement and a lifetime warranty on the moissanite stones."
          }
        }
      ]
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://kloira.com" },
        { "@type": "ListItem", "position": 2, "name": "Men's Watches", "item": "https://kloira.com/collections/mens-watches" },
        { "@type": "ListItem", "position": 3, "name": "Kairos Chronograph" }
      ]
    }
  ]
}
</script>

Schema.org's Product type has 60+ optional fields. You do not need most of them. The five below are the ones that drive AI-retrieval behavior; the rest are a mix of classic-SEO hygiene and Google-Merchant-Center-specific formatting.

1. name

Must be shopper-query shaped, not branded. 'Men's 42mm moissanite chronograph' outranks 'Kairos Chronograph' on unbranded queries. This field alone is the #1 product-page ranking factor on ChatGPT Shopping.

2. description

300-800 characters, answer-first. Describe what the product is, who it is for, and its key specifications. Avoid marketing adjectives; lean on concrete specs.

3. gtin (gtin13 / gtin14 / gtin8)

The universal product identifier. Google Shopping Graph and ChatGPT Shopping deprioritize products without a GTIN on transactional queries. Store as a Shopify metafield and render into schema.

4. offers (price, priceCurrency, availability)

All three are required for Shopping carousel eligibility. Currency must be ISO 4217. Availability must be a schema.org URL (not a plain string like 'in stock').

5. aggregateRating

Drives the star-count badge on Google and carries significant weight on ChatGPT Shopping's trust signal. Shopify's default themes often skip this; your review app (Judge.me, Stamped, Okendo) typically injects it, but verify.

FAQPage schema is the single highest-leverage addition most Shopify stores can make — but only if the questions are the ones shoppers genuinely ask. A PDP that emits FAQPage schema with the questions 'Why choose us?' and 'What makes our product special?' is worse than a PDP with no FAQPage at all, because the schema signals authority but the content signals marketing noise. Here is the rule set we apply.

1. 1Mine the actual shopper questions. The source is your customer-support inbox, Shopify's product-page Q&A app if you run one, Reddit threads about your category, and the 'People Also Ask' block on Google for your target query. You need 5-8 real questions per product.
2. 2Phrase the question the way a shopper would. 'Is this waterproof?' beats 'What is the water resistance rating of this watch?' — because the former is how a human types into ChatGPT, and the ranker matches literal phrasing.
3. 3Answer in 40-80 words. Long enough to be complete, short enough to be quotable as a single citation block.
4. 4Front-load the direct answer. First sentence answers the question; subsequent sentences expand. 'The Kairos is rated to 5 ATM — suitable for handwashing, rain, and brief swimming, but not for showering or diving.' The first clause is the quotable part.
5. 5Cover five categories: product fit (size, color, compatibility), use case (activities, occasions, conditions), specifications (materials, power, water resistance), policies (shipping, returns, warranty), and pairing (what goes with what).

Broken schema is worse than no schema — it signals low quality to every ranker that parses it. Before any schema change goes live, run three validators in order: schema correctness, rich-result eligibility, and AI-retrieval-ready verification.

Schema.org Validator

validator.schema.org — checks your JSON-LD against the schema.org vocabulary. Catches typos like 'availabiliy' and type mismatches like a price string where a number is required.

Google Rich Results Test

search.google.com/test/rich-results — checks Google's rich-result eligibility specifically. Catches missing fields Google requires for rich results even if schema.org says they are optional.

Per-URL audit for AI retrieval

Run an AI-ready audit that checks for the five AI-critical fields (name shape, description length, GTIN presence, offers completeness, aggregateRating). Surfient's Audit Engine does this automatically per product.

The most common schema errors on Shopify PDPs

1. 1Availability as a string instead of a schema.org URL. 'in stock' fails; https://schema.org/InStock passes.
2. 2Price as a number with currency symbol. 399 passes; '$399' fails.
3. 3Brand as a string instead of a Brand entity. 'Kloira' passes in classic SEO but loses entity linking for AI.
4. 4aggregateRating with a reviewCount of 0. Emit the field only when there are actual reviews.
5. 5Duplicate @id values across @graph entries. Each entity needs a unique @id within the document.