SEO Guide · 2026

Shopify Structured Data Testing Tools: How to Validate Your JSON-LD

Shopify themes emit Product JSON-LD automatically, but the default implementation has well-documented gaps that block rich results and reduce AI agent visibility. This guide covers the five validation tools, what each one catches, and how to read their output for Shopify-specific errors.

The five structured data testing tools for Shopify

Google Rich Results Test: reading the Shopify output

Paste a product page URL into the Google Rich Results Test. You should see a "Product" rich result detected. If you don't, the page's JSON-LD has a blocking error or the theme is deferring script execution until after the renderer's JavaScript timeout.

The three most common Shopify-specific errors flagged by this tool:

Schema Markup Validator: what it catches that Google doesn't

The Schema Markup Validator checks full Schema.org compliance. It validates types that Google ignores, which is why it matters for AI agent compatibility beyond Google. Key Shopify-specific findings from this tool:

• ProductGroup missing: If your theme emits one Product per page (rather than a ProductGroup with hasVariant children), AI agents that use ProductGroup for variant aggregation (Perplexity, some Google AI Mode paths) see only the first variant's price and availability.
• Brand type missing: The vendor field is often emitted as a plain string ("brand": "Acme") rather than a Brand object with a URL and sameAs. AI agents use the Brand object for entity disambiguation.
• Offer eligibleQuantity absent: Schema.org allows specifying minimum order quantities and maximum per-customer limits — AI agents that handle B2B queries read this field.

Google Search Console Shopping Enhancements report

The GSC Shopping Enhancements report aggregates structured data errors across all crawled product pages. It is slower than single-URL tools (GSC crawls on Google's schedule) but more authoritative — it reflects what Googlebot actually renders, not what a browser renders. Key differences from the Rich Results Test:

• GSC reports what Googlebot's rendering service (WRS) sees after JavaScript execution — so a deferred JSON-LD injection that passes the Rich Results Test may still fail in GSC if it takes too long to render.
• GSC shows the count of affected URLs, not just one URL — useful for understanding whether errors are template-wide or only on specific products.
• GSC errors appear with a 2–7 day lag after you deploy a fix — it re-crawls on its own schedule.

CatalogScan: catalog-wide coverage check

Single-URL tools are necessary but not sufficient. A Shopify store with 800 products has 800 product pages. The 5% of products with missing GTINs, blank descriptions, or broken image URLs will not appear in a single-URL test. CatalogScan reads the full /products.json catalog and checks 18 signals including:

• GTIN coverage across all variants (not just page-level JSON-LD)
• AggregateRating presence across all product pages
• Description length distribution (under 150 chars = poor AI agent signal extraction)
• Image alt text coverage (blank alt text = moderate quality penalty)
• ProductGroup vs. flat Product JSON-LD detection

Testing structured data from the command line

For bulk spot-checks without manual tools, curl can verify JSON-LD presence and catch obvious syntax errors:

# Extract JSON-LD from a product page
curl -s "https://yourstore.com/products/your-product" \
  | python3 -c "
import sys, re, json
html = sys.stdin.read()
blocks = re.findall(r'', html, re.DOTALL)
for b in blocks:
    try:
        obj = json.loads(b)
        if obj.get('@type') in ('Product','ProductGroup'):
            print(json.dumps(obj, indent=2))
    except json.JSONDecodeError as e:
        print(f'JSON parse error: {e}')
"

FAQ