Last updated: October 3, 2026
These eight JSON-LD templates cover the structured data a Shopify store actually needs: Organization, WebSite with SearchAction, Product, BreadcrumbList, FAQPage, BlogPosting, Store for physical locations, and Person for a founder or author. Each one uses Liquid variables so it fills itself from your store data, and each notes exactly which template or section it belongs in. 7SEA Marketing uses these blocks on client stores and on this site. Before pasting any of them, check what your theme already outputs, because one clean entity per type per page beats two conflicting ones.
Across the Shopify stores 7SEA Marketing audited in 2026, the most common structured data problem was not missing markup. It was duplicate Product markup from a theme and an app on the same page, with different prices. Run the Rich Results Test on a product page before adding anything, and if you see two Product entities, fix that first using our guide to structured data without a developer.
How to use these templates

Where to paste: a Custom Liquid block in the theme editor for template-specific markup (product, collection, page), or a Custom Liquid section in the footer group for sitewide markup (Organization, WebSite). Never edit the live theme directly; duplicate it, paste, preview, then publish.
The one filter that matters: every variable ends in | json. That filter wraps the value in quotes and escapes anything that would break the JSON, which is what breaks hand-written schema most often. Do not add your own quotes around a | json value.
Validate every page type after pasting with Google's Rich Results Test and the Schema.org validator. Then check Search Console, Enhancements, a week later.
| Template | Paste in | Add only if |
|---|---|---|
| 1. Organization | Footer section, sitewide, once | Theme does not already output Organization, or outputs a thin one you cannot edit |
| 2. WebSite with SearchAction | Homepage template only | Theme does not output WebSite |
| 3. Product | Product template | Theme Product markup is missing or broken. Most current themes already have it; do not duplicate |
| 4. BreadcrumbList | Product and collection templates | Theme shows breadcrumbs visually but does not mark them up |
| 5. FAQPage | Any template with a visible FAQ | Always safe if the questions are visible on the page |
| 6. BlogPosting | Article template | Theme article markup lacks author, publisher or dates |
| 7. Store | Location pages | You have physical locations |
| 8. Person | Founder or author page | Always safe |
1. Organization (sitewide)
Replace the sameAs URLs, logo path, founder and contact details with your own. The more real profiles in sameAs, the stronger the entity.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "{{ shop.url }}/#organization",
"name": {{ shop.name | json }},
"url": {{ shop.url | json }},
"logo": "{{ shop.url }}/cdn/shop/files/your-logo.png",
"email": {{ shop.email | json }},
"foundingDate": "2020",
"founder": {
"@type": "Person",
"name": "Founder Name",
"url": "{{ shop.url }}/pages/founder"
},
"address": {
"@type": "PostalAddress",
"streetAddress": "Street address",
"addressLocality": "City",
"addressRegion": "State",
"postalCode": "00000",
"addressCountry": "US"
},
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer service",
"email": {{ shop.email | json }},
"availableLanguage": ["English"]
},
"sameAs": [
"https://www.instagram.com/yourbrand",
"https://www.facebook.com/yourbrand",
"https://www.linkedin.com/company/yourbrand",
"https://www.tiktok.com/@yourbrand"
]
}
</script>
2. WebSite with SearchAction (homepage)
Shopify's search URL pattern is /search?q=, which is what makes the SearchAction valid.
{% if template.name == 'index' %}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"@id": "{{ shop.url }}/#website",
"name": {{ shop.name | json }},
"url": {{ shop.url | json }},
"publisher": { "@id": "{{ shop.url }}/#organization" },
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "{{ shop.url }}/search?q={search_term_string}"
},
"query-input": "required name=search_term_string"
}
}
</script>
{% endif %}
3. Product (product template, only if your theme does not output it)
This outputs one Offer per variant with live price and availability. GTIN comes from the barcode field, SKU from the SKU field, brand from vendor. Delete this block if your theme already outputs Product markup.
{% if template.name == 'product' %}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "{{ shop.url }}{{ product.url }}#product",
"name": {{ product.title | json }},
"description": {{ product.description | strip_html | truncate: 500 | json }},
"url": "{{ shop.url }}{{ product.url }}",
"image": [
{%- for image in product.images limit: 3 -%}
{{ image | image_url: width: 1200 | prepend: 'https:' | json }}{% unless forloop.last %},{% endunless %}
{%- endfor -%}
],
"brand": { "@type": "Brand", "name": {{ product.vendor | json }} },
"sku": {{ product.selected_or_first_available_variant.sku | json }},
{%- if product.selected_or_first_available_variant.barcode != blank -%}
"gtin": {{ product.selected_or_first_available_variant.barcode | json }},
{%- endif -%}
"offers": [
{%- for variant in product.variants -%}
{
"@type": "Offer",
"url": "{{ shop.url }}{{ product.url }}?variant={{ variant.id }}",
"priceCurrency": {{ cart.currency.iso_code | json }},
"price": "{{ variant.price | money_without_currency | remove: ',' }}",
"sku": {{ variant.sku | json }},
"itemCondition": "https://schema.org/NewCondition",
"availability": "{% if variant.available %}https://schema.org/InStock{% else %}https://schema.org/OutOfStock{% endif %}"
}{% unless forloop.last %},{% endunless %}
{%- endfor -%}
]
}
</script>
{% endif %}
If you sell used or refurbished goods, change itemCondition to UsedCondition or RefurbishedCondition. If you use a review app that outputs aggregateRating, make sure it attaches to this entity rather than creating a second Product.
4. BreadcrumbList (product and collection templates)
For products, this uses the collection the visitor came from when available, otherwise the first collection the product belongs to.
{% if template.name == 'product' or template.name == 'collection' %}
{%- assign crumb_collection = collection -%}
{%- if template.name == 'product' and collection == blank -%}
{%- assign crumb_collection = product.collections.first -%}
{%- endif -%}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": {{ shop.url | json }} }
{%- if crumb_collection != blank -%},
{ "@type": "ListItem", "position": 2, "name": {{ crumb_collection.title | json }}, "item": "{{ shop.url }}{{ crumb_collection.url }}" }
{%- endif -%}
{%- if template.name == 'product' -%},
{ "@type": "ListItem", "position": {% if crumb_collection != blank %}3{% else %}2{% endif %}, "name": {{ product.title | json }}, "item": "{{ shop.url }}{{ product.url }}" }
{%- endif -%}
]
}
</script>
{% endif %}
5. FAQPage (any page with visible FAQs)
This version reads from product metafields so non-technical staff can manage questions in the admin. Create metafields custom.faq_question_1, custom.faq_answer_1 and so on, or adapt the keys to a metaobject list. The questions must also be visible on the page.
{%- assign faqs = '' -%}
{%- for i in (1..6) -%}
{%- assign qkey = 'faq_q' | append: i -%}
{%- assign akey = 'faq_a' | append: i -%}
{%- assign q = product.metafields.custom[qkey] -%}
{%- assign a = product.metafields.custom[akey] -%}
{%- if q != blank and a != blank -%}
{%- capture item -%}
{ "@type": "Question", "name": {{ q | json }}, "acceptedAnswer": { "@type": "Answer", "text": {{ a | strip_html | json }} } }
{%- endcapture -%}
{%- if faqs != '' -%}{%- assign faqs = faqs | append: ',' -%}{%- endif -%}
{%- assign faqs = faqs | append: item -%}
{%- endif -%}
{%- endfor -%}
{%- if faqs != '' -%}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [ {{ faqs }} ]
}
</script>
{%- endif -%}
For a static FAQ on a page template, replace the loop with hand-written Question objects. Keep answers to 40 to 60 words; AI engines quote them verbatim.
6. BlogPosting (article template)
Adds the author as a Person entity linked to an author page, the publisher as your Organization, and both dates. This is the E-E-A-T signal most Shopify themes leave out.
{% if template.name == 'article' %}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"@id": "{{ shop.url }}{{ article.url }}#article",
"headline": {{ article.title | json }},
"description": {{ article.excerpt_or_content | strip_html | truncate: 160 | json }},
"url": "{{ shop.url }}{{ article.url }}",
{%- if article.image -%}
"image": {{ article.image | image_url: width: 1200 | prepend: 'https:' | json }},
{%- endif -%}
"datePublished": {{ article.published_at | date: '%Y-%m-%dT%H:%M:%S%z' | json }},
"dateModified": {{ article.updated_at | date: '%Y-%m-%dT%H:%M:%S%z' | json }},
"author": {
"@type": "Person",
"name": {{ article.author | json }},
"url": "{{ shop.url }}/pages/founder"
},
"publisher": { "@id": "{{ shop.url }}/#organization" },
"mainEntityOfPage": "{{ shop.url }}{{ article.url }}"
}
</script>
{% endif %}
7. Store (physical location pages)
For a metaobject-based location page, pull fields from the metaobject. For a single store, hard-code the values.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Store",
"name": {{ metaobject.name.value | json }},
"image": {{ metaobject.photo.value | image_url: width: 1200 | prepend: 'https:' | json }},
"telephone": {{ metaobject.phone.value | json }},
"url": "{{ shop.url }}{{ request.path }}",
"address": {
"@type": "PostalAddress",
"streetAddress": {{ metaobject.street.value | json }},
"addressLocality": {{ metaobject.city.value | json }},
"addressRegion": {{ metaobject.region.value | json }},
"postalCode": {{ metaobject.postal_code.value | json }},
"addressCountry": {{ metaobject.country.value | json }}
},
"openingHours": {{ metaobject.hours.value | json }},
"parentOrganization": { "@id": "{{ shop.url }}/#organization" }
}
</script>
Use a more specific type than Store when one fits: ClothingStore, JewelryStore, HealthAndBeautyBusiness, Restaurant. Match name, address and phone exactly to your Google Business Profile.
8. Person (founder or author page)
Links the person to the organization and to external profiles. Pair it with a visible bio and credentials on the same page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "{{ shop.url }}/pages/founder#person",
"name": "Founder Name",
"jobTitle": "Founder",
"url": "{{ shop.url }}/pages/founder",
"image": "{{ shop.url }}/cdn/shop/files/founder.jpg",
"worksFor": { "@id": "{{ shop.url }}/#organization" },
"knowsAbout": ["Shopify", "Ecommerce SEO", "Google Ads"],
"alumniOf": { "@type": "CollegeOrUniversity", "name": "University Name" },
"sameAs": [
"https://www.linkedin.com/in/yourprofile",
"https://x.com/yourhandle"
]
}
</script>
Common errors after pasting

| Error | Cause | Fix |
|---|---|---|
| Invalid JSON | A trailing comma before a closing bracket, usually from a Liquid loop | Use the unless forloop.last pattern shown above |
| Duplicate Product entity | Theme and app or pasted block both output Product | Keep one source, remove the other |
| Missing field: image | Product has no images or Liquid path wrong | Check the image_url filter output in view-source |
| Price formatted with comma | Locale formatting | The remove filter in the Product template |
| FAQ not eligible | Questions not visible on the page | Render the same questions in the page content |
| Dates invalid | Wrong date format | Use the ISO 8601 date filter shown in BlogPosting |
Prefer an app?
These templates are free and durable, but they need someone comfortable pasting Liquid. If you would rather have schema handled without touching the theme, 7SEA Marketing can implement and validate all eight on your store as part of our SEO service. For the broader picture, our Shopify SEO checklist covers where structured data sits among everything else.
Frequently asked questions
Where do I add JSON-LD schema in Shopify?
In a Custom Liquid block in the theme editor for template-specific markup such as Product, Breadcrumb and FAQ, or in a Custom Liquid section in the footer group for sitewide markup such as Organization and WebSite. Work on a duplicate theme and preview before publishing.
Does Shopify already add Product schema?
Most current themes output basic Product markup with name, image, price and availability. Check with the Rich Results Test before adding your own. If the theme already outputs it, adding a second block creates duplicate entities, which is worse than the gaps you were trying to fill.
Why does my Shopify schema show invalid JSON?
Almost always a trailing comma left by a Liquid loop, or a value pasted without the json filter so quotes or line breaks in the content break the structure. Use the unless forloop.last pattern and end every variable with the json filter.
Do FAQ answers need to be visible on the page for FAQPage schema?
Yes. Google requires the questions and answers in the markup to match visible content on the page. Schema that describes content not on the page violates guidelines and will not be used.
What schema helps most for AI citations?
One clean Product entity, FAQPage with 40 to 60 word answers, Organization with a complete sameAs list, and BlogPosting with a real Person author. These help AI engines identify the entity, the answer and the source.
Want a real number for your store?
Send us the URL and the catalog size. We will come back with a fixed quote and the template list it covers, no call required unless you want one.
Get a build quote