Step-by-Step Schema Markup Implementation for Shopify (Product, FAQ, Organization)

Key Takeaways

• ✓ JSON-LD injected via Liquid is the recommended schema approach for Shopify.
• ✓ Check for existing schema before adding your own, as duplicate or conflicting markup can create validation issues.
• ✓ Schema must reflect content that is actually visible and accurate on the page.
• ✓ Use the Schema Markup Validator for syntax; use Google's Rich Results Test for rich-result eligibility.
• ✓ Liquid variables keep Product Schema accurate automatically. No manual updates needed.

1Product Schema

Location: sections/main-product.liquid (filename varies by theme)

Search the file for "@type": "Product" first. If found, your theme already outputs Product Schema, so skip this step. If not, paste the block below at the bottom of the file, before the {% schema %} tag (never inside it).

This example uses selected_or_first_available_variant, the safest single-offer approach for stores with multiple variants. Exposing all variants as separate offers requires a looped offers array and is beyond the scope of this guide.

{% if product %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": {{ product.title | json }},
  "url": {{ shop.url | append: product.url | json }},
  "description": {{ product.description | strip_html | truncate: 500 | json }},
  "brand": {
    "@type": "Brand",
    "name": {{ product.vendor | json }}
  },
  "image": {{ product.featured_image | image_url: width: 1200 | prepend: 'https:' | json }},
  "offers": {
    "@type": "Offer",
    "price": {{ product.selected_or_first_available_variant.price | divided_by: 100.0 | json }},
    "priceCurrency": {{ shop.currency | json }},
    "availability": {% if product.selected_or_first_available_variant.available %}"https://schema.org/InStock"{% else %}"https://schema.org/OutOfStock"{% endif %},
    "url": {{ shop.url | append: product.url | json }}{% if product.selected_or_first_available_variant.sku != blank %},
    "sku": {{ product.selected_or_first_available_variant.sku | json }}{% endif %}{% if product.selected_or_first_available_variant.barcode != blank %},
    "gtin": {{ product.selected_or_first_available_variant.barcode | json }}{% endif %}
  }
}
</script>
{% endif %}

2FAQPage Schema

Location: Your FAQ section or page template

Only use FAQPage schema when the questions and answers are visibly rendered on the page. Do not mark up hidden, collapsed, or fabricated content. Google has significantly restricted FAQ rich-result display compared with earlier years, and valid markup does not guarantee a rich result. Implement it because your page genuinely contains FAQ content, not solely to gain a SERP feature.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "REPLACE: Your first FAQ question, exactly as it appears on the page",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "REPLACE: Your first FAQ answer, matching the visible text on the page."
      }
    },
    {
      "@type": "Question",
      "name": "REPLACE: Your second FAQ question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "REPLACE: Your second FAQ answer."
      }
    }
  ]
}
</script>

3BreadcrumbList Schema

Location: Your breadcrumb snippet or section

The schema must reflect your actual visible navigation hierarchy. The collection object is not always available on a product page, since a customer can arrive directly from search without passing through a collection. The example below handles both cases safely.

{% if product %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": {{ shop.url | json }}
    },
    {% if collection %}
    {
      "@type": "ListItem",
      "position": 2,
      "name": {{ collection.title | json }},
      "item": {{ shop.url | append: collection.url | json }}
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": {{ product.title | json }},
      "item": {{ shop.url | append: product.url | json }}
    }
    {% else %}
    {
      "@type": "ListItem",
      "position": 2,
      "name": {{ product.title | json }},
      "item": {{ shop.url | append: product.url | json }}
    }
    {% endif %}
  ]
}
</script>
{% endif %}

4Organization Schema

Location: layout/theme.liquid, homepage only

Add this once, on the homepage only. sameAs links your business to profiles you actually own, so do not include platforms where you don't have a presence. For the logo, use a stable public URL rather than a Shopify CDN URL that may change. Replace every REPLACE value before publishing.

{% if request.page_type == 'index' %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": {{ shop.name | json }},
  "url": {{ shop.url | json }},
  "logo": "REPLACE: https://yourdomain.com/your-logo.png",
  "description": "REPLACE: A brief, accurate description of your business.",
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "REPLACE: support@yourdomain.com"
  },
  "sameAs": [
    "REPLACE: https://www.instagram.com/your-handle",
    "REPLACE: https://www.facebook.com/your-page"
  ]
}
</script>
{% endif %}