Understanding Legacy Structured Data in Turbo

Turbo has powered fast-loading Shopify storefronts for years. However, earlier versions often rely on inline microdata spread across multiple Liquid template files. As search engines prioritize comprehensive JSON-LD, older microdata implementations can trigger warnings for missing merchant fields.

Identifying Duplicate Product Markup Conflicts

When third-party apps or custom snippets are added alongside Turbo built-in markup, search engines may encounter competing Product declarations. This can lead to conflicting pricing, stock status, or review data in Google Search Console diagnostics.

Modernizing Turbo with Consolidated JSON-LD

A clean solution involves silencing legacy theme microdata and supplying a single, verified JSON-LD payload. This ensures that Turbo stores retain their performance benefits while delivering modern schema compliance across Google Search and Google Merchant Center.

Code Example: Google-Compliant JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Turbo Performance Running Shoes",
  "sku": "TRB-RUN-42",
  "offers": {
    "@type": "Offer",
    "price": "140.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2027-12-31"
  }
}
Keep Your Product Structured Data Compliant

Help prevent Google Merchant Center warnings and maintain search snippet eligibility. Smart Schema generates compliant structured data server-side in minutes with zero theme code changes.

Start 14-Day Free Trial

Frequently Asked Questions

Can Turbo theme schema be updated without modifying core template files?

Yes, modern apps like Smart Schema inject clean, validated JSON-LD via Shopify theme app extensions, avoiding destructive edits to theme Liquid files.

Related Technical Glossary Terms
Related Troubleshooting Guides