The Shopify Structured Data Checklist: Schema Markup That Makes Products Visible to ChatGPT and Perplexity

Most Shopify store owners have no idea whether their structured data is working. They installed a theme, maybe added a schema app, and assume it's fine. Then they wonder why ChatGPT recommends a competitor's product instead of theirs.

I've checked structured data on over 50 Shopify stores in the past few months. Roughly 60% had broken or incomplete schema markup. Not "could be improved" — actually broken. The JSON-LD was malformed, the product data was incomplete, or multiple schema blocks were conflicting with each other.

Here's the checklist I use when auditing a Shopify store for AI search visibility. If you follow it, your structured data will be ahead of most ecommerce sites on the internet.

Why structured data matters more for AI search than traditional SEO

Traditional SEO uses structured data primarily for rich results — star ratings in search results, FAQ dropdowns, product carousels. These are nice, but they're supplementary.

AI search is different. When ChatGPT or Perplexity tries to answer "what's the best wireless headphone under $200," the model needs to extract specific facts: price, features, ratings, availability. Structured data is the fastest, most reliable way for AI systems to pull those facts from your page.

According to recent testing, pages with valid JSON-LD schema see AI crawler parse success rates jump from around 37% to over 90%. That's not a small improvement. It's the difference between being readable and being invisible to AI systems.

The schema types that matter most for ecommerce AI visibility are Product, Offer, AggregateRating, Review, FAQPage, Organization, and BreadcrumbList. Let me walk through each one.

The essential schema types for Shopify product pages

Product and Offer schema

This is the foundation. Every product page should have a Product schema block that includes the product name, brand, description, images, SKU or GTIN, and an Offer with price, currency, and availability.

Here's what a complete Product schema looks like in JSON-LD format:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Merino Wool Crew Neck Sweater",
  "image": [
    "https://yourstore.com/cdn/images/sweater-front.jpg",
    "https://yourstore.com/cdn/images/sweater-back.jpg"
  ],
  "description": "Ultra-fine 17.5 micron merino wool crew neck sweater. Machine washable. Available in 6 colors. Fits true to size with a slim athletic cut.",
  "brand": {
    "@type": "Brand",
    "name": "Your Brand Name"
  },
  "sku": "MWS-CREW-NAV-M",
  "gtin13": "9421035678901",
  "offers": {
    "@type": "Offer",
    "url": "https://yourstore.com/products/merino-crew-neck",
    "priceCurrency": "USD",
    "price": "89.00",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

The most common mistakes I see: missing brand field, no SKU or GTIN, availability not matching actual stock status, and description that's either empty or copied from the visible page text without cleanup.

AggregateRating and Review schema

If your store has product reviews — and it should — those reviews need to be exposed through AggregateRating schema. This is how AI systems know your product has social proof.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Merino Wool Crew Neck Sweater",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "128",
    "bestRating": "5",
    "worstRating": "1"
  }
}

Critical rule: your AggregateRating values must match real reviews on the page. If your schema says 4.7 stars from 128 reviews but there are no visible reviews on the page, AI systems will flag this as misleading. Google's Rich Results Test will also catch this.

FAQPage schema

Any product page with question-and-answer content should have FAQPage schema. This is the single most effective schema type for appearing in AI-generated answers, because the Q&A format directly maps to how AI systems construct responses.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is this sweater machine washable?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. This merino wool sweater is machine washable on a gentle cycle with cold water. Use a wool-specific detergent for best results. Lay flat to dry. The sweater maintains its shape and softness for 50+ washes when cared for properly."
      }
    }
  ]
}

Keep each answer between 40 and 60 words. Long enough to be complete and citable, short enough for AI systems to extract without reformatting. This is the sweet spot for AI extraction.

BreadcrumbList schema

BreadcrumbList schema tells AI crawlers how your product fits into your catalog structure. It seems minor, but it helps models understand your site's information architecture and surface related products correctly.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://yourstore.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Men's Clothing",
      "item": "https://yourstore.com/collections/mens"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Sweaters",
      "item": "https://yourstore.com/collections/mens-sweaters"
    },
    {
      "@type": "ListItem",
      "position": 4,
      "name": "Merino Wool Crew Neck",
      "item": "https://yourstore.com/products/merino-crew-neck"
    }
  ]
}

Organization schema on the homepage

Your homepage should have Organization schema that establishes your brand identity: name, logo, URL, social profiles, and contact information. This helps AI systems build a consistent representation of your brand across pages.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand Name",
  "url": "https://yourstore.com",
  "logo": "https://yourstore.com/logo.png",
  "sameAs": [
    "https://www.instagram.com/yourbrand",
    "https://www.facebook.com/yourbrand",
    "https://www.youtube.com/@yourbrand"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@yourstore.com",
    "contactType": "customer service"
  }
}

How to validate your schema (and why most people skip this)

Writing schema is easy. Validating it is where most stores fall short. Here's my validation workflow:

Step 1: Google Rich Results Test. Paste each product page URL into Google's Rich Results Test. It shows you exactly what schema is detected and whether it's valid. Check for errors, not just warnings.

Step 2: Schema.org Validator. This catches structural issues that Google's tool might miss. It validates against the full Schema.org specification, not just Google-supported types.

Step 3: Manual field verification. Compare your schema data against what's visible on the page. Price in schema matches price on page? Availability in schema matches actual stock? Rating in schema matches visible reviews? Mismatches between structured data and visible content are trust violations that AI systems increasingly penalize.

Step 4: Multi-page spot check. Don't just check one product. Check 5-10 across different categories. I've seen stores where schema works perfectly on standard products but breaks on sale items, variants, or out-of-stock items.

Common Shopify schema mistakes (and how to fix them)

Mistake 1: Relying solely on your theme's default schema. Most Shopify themes output basic Product schema, but they often miss critical fields like brand, GTIN, or proper availability states. Check what your theme generates and supplement where needed.

Mistake 2: Conflicting schema from multiple apps. If you have a reviews app, an SEO app, and your theme all injecting schema, they can conflict. Duplicate Product blocks, mismatched data, or invalid nesting. Audit your page source to see how many schema blocks are present and whether they agree with each other.

Mistake 3: Static schema that doesn't update with inventory. If your schema says "InStock" but the product is sold out, AI systems that extract that data will recommend an unavailable product. Your schema needs to reflect real-time inventory. Most modern Shopify themes handle this, but if you're using a custom schema implementation, make sure it pulls from live inventory data.

Mistake 4: Missing variant-level data. If your product has variants (size, color), each variant should have its own offer with specific price, SKU, and availability. A single Offer block for a product with 20 variants is incomplete.

Mistake 5: Schema on thin content pages. Adding perfect schema to a product page with a two-sentence description doesn't help. Schema amplifies good content — it doesn't compensate for bad content. Fix your product descriptions first, then mark them up.

The complete Shopify GEO schema audit checklist

Run through this for every product template on your store:

• Product schema present with name, image, description, brand, SKU, and valid Offer block (price, currency, availability)
• AggregateRating present if reviews exist, with values matching visible reviews
• FAQPage schema on any page with Q&A content, answers between 40-60 words
• BreadcrumbList schema reflecting actual navigation path
• Organization schema on homepage with name, logo, social profiles, and contact info
• All schema validated through Google Rich Results Test with zero errors
• Schema data matches visible page content (price, availability, ratings)
• No duplicate or conflicting schema blocks from multiple apps or theme
• Variant-level offers for products with multiple options
• Inventory-aware availability that updates with actual stock levels

If you can check every box on that list, your structured data is in better shape than 90% of ecommerce sites. And when AI systems are deciding which product to recommend, the one with clean, complete, accurate structured data has a significant advantage.

I use My GEO Check to run this exact audit on every new store I work with — it catches schema errors, missing fields, and AI readability issues in about thirty seconds, which beats spending an hour digging through page source code manually.

What to do after the audit

Schema is a foundation, not the entire strategy. Once your structured data is solid, focus on the content it describes. Write detailed, factual product descriptions. Build real FAQ sections from customer questions. Earn genuine reviews. Create comparison content.

The schema makes your content readable to AI systems. The content quality determines whether AI systems trust and cite you. Both matter. Start with schema because it's the fastest fix, then build the content layer on top.

If you want to see exactly how your store's structured data looks to AI crawlers, run a free scan at My GEO Check. It checks your schema validity along with 20+ other GEO factors and gives you a prioritized fix list.