Shopify schema markup — which structured data to implement and how

Where Product schema commonly fails in Dawn and popular themes

Shopify’s Dawn theme (the default free theme) outputs Product schema in templates/product.json via the main-product section. The schema it generates covers the minimum required fields but leaves several enhancement fields empty.

The gaps consistently found in Dawn and most commercial Shopify themes:

Missing GTIN. Dawn doesn’t output gtin, gtin8, gtin13, mpn, or isbn fields. Google uses these identifiers to match products in the Shopping index and to serve rich seller results. If your products have barcodes, GTINs should be stored as Shopify product metafields and injected into the schema.

Missing shippingDetails. Google’s Product rich results guidelines increasingly require shippingDetails for eligibility in enhanced Shopping displays. Dawn doesn’t include it. The schema needs a OfferShippingDetails object with shippingRate, shippingDestination, and deliveryTime.

Missing hasMerchantReturnPolicy. Return policy schema (MerchantReturnPolicy) is required for the “Free returns” badge in Shopping results. Dawn doesn’t output it.

Missing aggregateRating when using review apps. If star ratings are displayed by a review app (Yotpo, Judge.me, Okendo), those apps typically inject their own aggregateRating into a separate schema block rather than into the theme’s Product schema block. Google may or may not combine them. Test with Rich Results Test — if aggregateRating doesn’t appear in the Product schema output, the rating won’t appear in organic rich results even if reviews are visible on the page.

Complete Product schema JSON-LD example

A complete Product schema for a Shopify product page including all recommended fields for Google Shopping and rich results eligibility:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "{{ product.title | escape }}",
  "description": "{{ product.description | strip_html | escape | truncate: 500 }}",
  "url": "{{ shop.url }}{{ product.url }}",
  "sku": "{{ product.selected_or_first_available_variant.sku }}",
  "gtin13": "{{ product.selected_or_first_available_variant.barcode }}",
  "brand": {
    "@type": "Brand",
    "name": "{{ product.vendor | escape }}"
  },
  "image": [
    {% for image in product.images limit: 3 %}
      "{{ image | image_url: width: 1200 }}"{% unless forloop.last %},{% endunless %}
    {% endfor %}
  ],
  "offers": {
    "@type": "Offer",
    "url": "{{ shop.url }}{{ product.url }}",
    "priceCurrency": "{{ cart.currency.iso_code }}",
    "price": "{{ product.selected_or_first_available_variant.price | money_without_currency | remove: ',' }}",
    "availability": "{% if product.available %}https://schema.org/InStock{% else %}https://schema.org/OutOfStock{% endif %}",
    "seller": {
      "@type": "Organization",
      "name": "{{ shop.name | escape }}"
    },
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": {
        "@type": "MonetaryAmount",
        "value": "0",
        "currency": "{{ cart.currency.iso_code }}"
      },
      "shippingDestination": {
        "@type": "DefinedRegion",
        "addressCountry": "GB"
      },
      "deliveryTime": {
        "@type": "ShippingDeliveryTime",
        "businessDays": {
          "@type": "OpeningHoursSpecification",
          "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"]
        },
        "cutoffTime": "17:00:00Z",
        "handlingTime": {
          "@type": "QuantitativeValue",
          "minValue": 1,
          "maxValue": 2,
          "unitCode": "DAY"
        },
        "transitTime": {
          "@type": "QuantitativeValue",
          "minValue": 1,
          "maxValue": 3,
          "unitCode": "DAY"
        }
      }
    },
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "GB",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    }
  }
}

Adjust addressCountry, returnPolicyCategory, merchantReturnDays, and shipping values to match your actual store policies. This schema goes in the <head> of your product template as a <script type="application/ld+json"> block.

How to implement FAQPage schema in Shopify

FAQPage schema is the highest-value schema type for AI Overviews and FAQ rich results on non-product pages. Guide pages, collection pages with descriptive content, and blog posts with Q&A sections are all candidates.

Shopify doesn’t support FAQPage schema natively. The implementation approach depends on how FAQ content is managed:

Approach 1: Hardcoded JSON-LD in the template. For pages where FAQ content is fixed, add a JSON-LD block directly to the page template. In templates/page.json, or in a section used by that page, add:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How do I return a product?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Returns are accepted within 30 days. Use the returns portal at [URL] to generate a free return label."
      }
    },
    {
      "@type": "Question",
      "name": "How long does delivery take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard delivery takes 2-3 business days. Express delivery (next day) is available at checkout."
      }
    }
  ]
}
</script>

Approach 2: Metafield-driven JSON-LD. Store FAQ question/answer pairs in page metafields (page.metafields.custom.faq_items) as a JSON list, then render JSON-LD using Liquid. This allows non-technical editors to manage FAQ content without touching theme code.

BreadcrumbList schema: why it matters for AI systems

BreadcrumbList schema tells search engines the navigation path to the current page. For Shopify, a product page on a store with clear navigation would have:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://store.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Running Shoes",
      "item": "https://store.com/collections/running-shoes"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Nike Air Zoom Pegasus 41",
      "item": "https://store.com/products/nike-air-zoom-pegasus-41"
    }
  ]
}

For AI systems (ChatGPT, Perplexity, Google AIO), BreadcrumbList helps establish site hierarchy and content categorisation. An AI trying to determine whether a product belongs to a specific category can use BreadcrumbList to confirm the navigation path rather than inferring it from URL structure alone.

Dawn theme outputs breadcrumb HTML navigation but typically doesn’t output BreadcrumbList JSON-LD schema. Adding it to the product and collection templates requires a small addition to the main-product.liquid and main-collection-product-grid.liquid sections.

Schema audit workflow

A complete schema audit for a Shopify store follows this sequence:

Step 1: Rich Results Test. Test the homepage, one product page, one collection page, and one blog post. For each, note: which schema types are present, any errors or warnings, and whether Product schema includes all required fields.

Step 2: Count JSON-LD blocks in page source. View the source of a product page and count the number of <script type="application/ld+json"> blocks. There should typically be one Product schema block, one BreadcrumbList block, and optionally one Organization block. If there are two or more Product blocks, there’s a conflict — usually between the theme and a review or SEO app.

Step 3: Check for duplicate schemas. If multiple Product schema blocks exist, note which fields each one contains. The conflict needs to be resolved — either by disabling one source or by ensuring only the most complete schema is output.

Step 4: Fix app conflicts. If a review app outputs its own Product schema, check whether it can be configured to add aggregateRating to the theme’s existing Product schema rather than outputting a separate schema block. Some review apps (Judge.me, Okendo) have settings for this. If not, disable the app’s schema output and manually add aggregateRating to the theme schema using Liquid.

Step 5: Validate after changes. Re-run the Rich Results Test and Schema Markup Validator after any schema changes. Validation errors in JSON-LD syntax (missing commas, unclosed brackets) prevent schema from being parsed — even a single syntax error disables the entire schema block.

Google Merchant Center vs Product schema: the relationship

Merchant Center feeds and Product schema serve different purposes but reference the same data.

Product schema is for organic search rich results — the star ratings, prices, and availability shown in Google’s organic search results (not Shopping ads). Google crawls the schema from your pages directly.

Merchant Center product feed is for Google Shopping results — both organic Shopping listings and paid Shopping ads. The feed is submitted directly to Merchant Center, either via the Shopify Google & YouTube app or a manual feed.

Both require consistent product data. Discrepancies between your Product schema (what’s on your page) and your Merchant Center feed (what you submitted) can cause Shopping disapprovals or rich result ineligibility. If your price in schema is $29.99 but your feed shows $27.99, Google will flag the mismatch.

For GTINs specifically: Merchant Center requires GTINs for products with barcodes. The same GTIN should appear in both the feed and the Product schema gtin13 field.

Article schema for Shopify blog posts

Blog posts and guide content should have Article schema to signal content type to AI systems and search engines. The schema goes in the article.liquid template or equivalent:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "{{ article.title | escape }}",
  "author": {
    "@type": "Person",
    "name": "{{ article.author }}"
  },
  "datePublished": "{{ article.published_at | date: '%Y-%m-%dT%H:%M:%S' }}",
  "dateModified": "{{ article.updated_at | date: '%Y-%m-%dT%H:%M:%S' }}",
  "image": "{{ article.image | image_url: width: 1200 }}",
  "publisher": {
    "@type": "Organization",
    "name": "{{ shop.name | escape }}",
    "logo": {
      "@type": "ImageObject",
      "url": "{{ settings.logo | image_url: width: 200 }}"
    }
  },
  "description": "{{ article.excerpt_or_content | strip_html | escape | truncate: 200 }}"
}

The author field in Article schema is particularly important for AI systems evaluating content credibility. Google’s E-E-A-T guidelines place increasing weight on author authority. A named, verifiable author with an author page outperforms anonymous or company-attributed authorship for ranking in expert query categories.

Tools for schema testing

Google Rich Results Test (search.google.com/test/rich-results): The primary tool. Paste any URL to see which schema types are parsed and whether any errors prevent rich result eligibility.

Schema Markup Validator (validator.schema.org): Validates schema syntax against schema.org specifications. Catches JSON syntax errors and property naming mistakes that the Rich Results Test may not flag.

Screaming Frog: In Spider mode, extract all JSON-LD from a site crawl (Extraction > Custom Extraction > CSS Path: script[type="application/ld+json"]). This allows you to audit schema across all pages rather than testing one at a time.

Google Search Console Rich Results report (under Enhancements): Shows which pages have valid rich result schema, which have errors, and which have warnings. Updated based on Google’s crawl, so reflects the live indexed state rather than a simulated test.