Tools Guide
E-Commerce Schema Markup Audit Tools
A complete comparison of schema markup audit tools for e-commerce stores — what each tool checks, what it misses, and which one to use for each audit scenario.
The Core Schema Audit Tools for E-Commerce
1. Google Rich Results Test
The primary tool for checking whether a product page qualifies for Google's rich results (Product rich results, shopping graph inclusion). It fetches the URL, executes JavaScript, and then parses the resulting DOM for JSON-LD, Microdata, and RDFa.
What it checks: Product type validity, required vs. recommended properties for rich results eligibility, Offer price and availability, AggregateRating ratingValue and reviewCount, image dimensions, GTIN field presence (not accuracy).
What it does not check: Whether your GTIN value is valid and matches a real product, /products.json accessibility, robots.txt AI crawler rules, description word count, Organization sameAs signals, Merchant Center feed consistency.
Best use case: After implementing a new JSON-LD block or updating your Liquid snippet, run the Rich Results Test on one representative product page to confirm the markup renders correctly and passes all required property checks.
2. Google Search Console — Enhancements Report
The catalog-wide view of structured data health. Google Search Console crawls all your indexed pages over a rolling window and aggregates schema errors, warnings, and valid items into the Enhancements section under Products.
What it checks: Same schema rules as the Rich Results Test, but across every crawled page. Surfaces errors you would never catch testing individual URLs — variant pages with broken Offer blocks, collection pages accidentally emitting Product markup, pages where app scripts delete the JSON-LD block after a theme update.
What it does not check: AI-specific signals, /products.json, Merchant Center feed accuracy, robots.txt AI crawler config.
Best use case: Weekly monitoring. Set up email alerts for new schema errors. Treat any spike in error count as a trigger to re-run the Rich Results Test on the affected page template.
3. Schema.org Validator (validator.schema.org)
The authoritative JSON-LD syntax validator maintained by the Schema.org community. Does not apply Google-specific rules — it validates against the Schema.org vocabulary definition only. Useful for checking that custom schema types (e.g., adding gtin14 vs gtin13 for a specific product) are correctly structured before adding Google-specific requirements on top.
Best use case: When implementing new schema types not covered by the Rich Results Test (MerchantReturnPolicy, ShippingDeliveryTime, OfferShippingDetails), use Schema.org validator to confirm the type structure is valid before testing in Google's tools.
4. Bing Markup Validator
Microsoft's equivalent of Google's Rich Results Test. Validates structured data for Bing's index, which powers ChatGPT Shopping's product retrieval layer. Bing applies slightly different requirements than Google — notably, it places higher weight on GTIN presence and penalizes missing priceValidUntil more harshly in freshness scoring.
Best use case: Any store targeting ChatGPT Shopping visibility should validate with Bing's tool in addition to Google's. The most common Bing-specific failure mode is priceValidUntil being absent or set to a past date, which causes Bing to mark the offer as stale.
5. CatalogScan
AI-agent readiness scoring that goes beyond standard structured data validation. CatalogScan checks the 18 signals that determine AI shopping agent citation rates, including several not covered by any standard SEO schema tool:
- GTIN presence and format validity (EAN-13, UPC-A, ISBN-13 pattern matching)
- /products.json accessibility and product count
- robots.txt rules for OAI-SearchBot, PerplexityBot, Google-Extended, and ClaudeBot
- Product description word count in body_html (stripped of HTML tags)
- JSON-LD description field presence and consistency with visible body_html
- AggregateRating presence and review injection method (static Liquid vs. JavaScript)
- Organization sameAs entity signals
Tool Comparison Matrix
| Signal checked | Rich Results Test | Search Console | Schema.org | Bing Validator | CatalogScan |
|---|---|---|---|---|---|
| Product JSON-LD syntax | Yes | Yes | Yes | Yes | Yes |
| Offer price + availability | Yes | Yes | Yes | Yes | Yes |
| AggregateRating structure | Yes | Yes | Yes | Yes | Yes |
| JavaScript rendering | Yes | Yes | No | Yes | Partial |
| GTIN format validity | No | No | No | Partial | Yes |
| /products.json availability | No | No | No | No | Yes |
| robots.txt AI crawler rules | No | No | No | No | Yes |
| Description word count | No | No | No | No | Yes |
| Organization sameAs entities | No | Partial | Yes | No | Yes |
| Catalog-wide coverage | No | Yes | No | No | Yes |
| priceValidUntil freshness | No | Partial | No | Yes | Yes |
Browser Extensions for Schema Auditing
For one-off page inspection during development, browser extensions provide a faster workflow than copy-pasting into online validators.
| Extension | Best for | Key capability |
|---|---|---|
| Structured Data Testing Tool (Chrome extension by Merkle) | Quick on-page JSON-LD inspection | Highlights structured data in the DOM; click any schema block to inspect properties |
| Schema Builder for Structured Data (Chrome) | Building new schema blocks interactively | GUI editor that outputs valid JSON-LD; useful for drafting new schema types |
| Detailed SEO Extension (Chrome) | Meta tags + schema in one panel | Shows title, meta description, canonical, og tags, and structured data types detected on page |
| JSON-LD Validator (Firefox) | Raw JSON-LD syntax debugging | Flags JSON parse errors that appear as invisible failures in online validators |
Audit Workflow: What to Run and When
| Trigger | Tool to use | What to check |
|---|---|---|
| After implementing new JSON-LD | Google Rich Results Test | All required properties pass; no errors on Product, Offer, AggregateRating |
| After a theme update | Rich Results Test + Search Console | JSON-LD still renders; no spike in Search Console errors within 2 weeks |
| After bulk product import | CatalogScan | GTIN coverage on new products; description word count; /products.json count matches admin |
| Monthly health check | Search Console Enhancements | No new error types; valid item count stable or growing |
| Before a new AI channel launch | CatalogScan + Bing Markup Validator | Full 18-signal AI readiness score; Bing Offer freshness; robots.txt AI crawler rules |
| Investigating a sudden drop in product rich results | Search Console → Rich Results Test | Identify which page template introduced the error; isolate to specific property |
Common Errors Audit Tools Surface on Shopify Stores
| Error | Detected by | Root cause on Shopify |
|---|---|---|
Missing price in Offer |
Rich Results Test, Search Console | Liquid {{ variant.price | money_without_trailing_zeros }} outputs currency symbol — JSON-LD price must be a number only |
Invalid priceCurrency |
Rich Results Test, Bing Validator | Using "USD $" instead of the ISO 4217 code "USD" |
| AggregateRating with zero reviews | Rich Results Test | Emitting AggregateRating with reviewCount: 0 — must be ≥1 or omit the block entirely |
| JSON-LD block deleted by app | Search Console (spike in errors) | A review or page-builder app overwrites the <head> section and removes native Liquid JSON-LD |
| Duplicate Product blocks | Schema.org validator, Rich Results Test | Native theme JSON-LD + a schema app both output separate Product blocks for the same page |
| GTIN fails format check | CatalogScan, Bing Validator (partial) | Barcode stored without leading zeros (12-digit UPC instead of 13-digit EAN-13) |
Related Resources
- E-Commerce Structured Data Validation Errors: Fix Guide — step-by-step remediation for the most common schema errors on Shopify stores.
- Shopify Schema Markup Guide — complete JSON-LD implementation reference for all Product schema types.
- Shopify Structured Data Testing Tools — Shopify-specific testing workflow including the Storefront API and theme preview URL patterns.
- Shopify Catalog Completeness and AI Visibility — how schema coverage across your full catalog affects AI agent citation rates.
Frequently Asked Questions
What is the best free schema markup audit tool for e-commerce?
Google's Rich Results Test is the best free single-URL tool for e-commerce schema markup because it renders JavaScript before parsing structured data, mirrors how Googlebot reads your page, and shows property-level errors and warnings for Product, Offer, AggregateRating, and BreadcrumbList types. For bulk catalog audits, CatalogScan provides automated AI-agent signal scoring. For raw JSON-LD syntax validation, the Schema.org validator at validator.schema.org is the authoritative reference.
Why does Google Search Console show schema errors that the Rich Results Test doesn't catch?
The Rich Results Test checks a single URL at the moment you run it. Google Search Console aggregates schema errors across all crawled pages over time, surfacing errors on pages never tested individually, errors introduced by theme updates, errors on specific variant URL states, and soft errors like missing recommended properties that suppress rich results without triggering test failures.
Do schema markup audit tools check AI agent visibility as well as Google rich results?
Standard SEO schema tools audit against Google and Bing requirements, which overlap significantly with AI agent requirements but are not identical. AI agents additionally care about GTIN presence and accuracy, /products.json availability, robots.txt configuration for AI crawlers, description word count, and Organization sameAs entity signals. CatalogScan audits specifically for AI agent readiness including these additional signals.
How often should I run a schema markup audit on my Shopify store?
Run a full schema audit after any theme update, after installing or uninstalling a Shopify app that touches product pages, after bulk product imports, and after changes to your JSON-LD Liquid snippets. For ongoing monitoring without manual effort, Google Search Console's Enhancements report flags new errors within 2–4 weeks of a crawl cycle.
Audit Your Store's AI-Agent Schema Coverage
CatalogScan checks all 18 AI-agent readiness signals in one scan — structured data completeness, GTIN coverage, description quality, /products.json access, and robots.txt AI crawler configuration — and scores your store against the top-100 DTC benchmark.
Scan your store free