FAQ Schema for Shopify: Markup That Validates

FAQ schema marks up question-and-answer content on your Shopify pages so search engines and AI systems can parse it directly. The implementation is straightforward. The validation pitfalls are not.

This guide covers the working JSON-LD template, where to add it across different Shopify page types, the validation errors that trip up most implementations, and an honest assessment of what FAQ schema actually gets you in 2026.

For the broader structured data overview, see Structured Data for Shopify. For the complete schema strategy, see the Shopify Schema Markup Guide.

What FAQ Schema Does (and What Changed in 2023)

FAQ schema uses two Schema.org types: FAQPage and Question. You wrap your Q&A pairs in a FAQPage entity with a mainEntity array containing each Question and its acceptedAnswer.

When FAQ schema was fully supported, Google displayed expandable question-and-answer dropdowns directly in search results. Your listing could take up significantly more SERP real estate. It was one of the highest-ROI schema types to implement.

Then Google changed the rules.

In August 2023, Google restricted FAQ rich results to well-known, authoritative government and health websites. The announcement was explicit: for all other sites, FAQ rich results will no longer be shown regularly.

This means most Shopify stores will not see FAQ dropdown displays in Google search results, regardless of how perfectly the schema validates.

Google also clarified that you don't need to remove existing FAQ markup. Valid schema that isn't being used for rich results doesn't cause problems — it just has no visible effect in Google Search.

Why FAQ Schema Still Matters in 2026

The loss of FAQ rich results is real. But writing off FAQ schema entirely would be a mistake. Here's why it still earns its place:

AI systems actively parse FAQ schema. ChatGPT, Perplexity, and Google's AI Overviews extract structured Q&A data when answering product-related questions. If someone asks an AI assistant "What's the return policy for [your brand]?" and you have that FAQ in schema markup, the AI has structured data to pull from rather than trying to parse your page's HTML.

Google AI Overviews use FAQ data. Even without the traditional FAQ rich result, Google's AI Overviews can pull from FAQ structured data when generating answer cards. Your Q&A content becomes machine-readable source material.

Content clarity for search engines. FAQ schema explicitly marks the relationship between questions and answers on your page. This helps search engines understand your content structure, even without a dedicated rich result display.

Zero downside. Adding valid FAQ schema costs nothing and risks nothing. Google has confirmed that unused structured data doesn't cause penalties. The effort is minimal — typically 15 minutes per page.

Future-proofing. Google has expanded and restricted rich result types multiple times. FAQ schema might regain broader eligibility. Having clean, valid markup in place means you're ready if that happens.

FAQ Schema JSON-LD Template for Shopify

Here's a complete, validated FAQPage template. This works on any Shopify page type.

{% comment %}
  FAQ Schema JSON-LD for Shopify
  Place in: template or section where FAQ content appears
  Works on: product pages, collection pages, custom pages
{% endcomment %}

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your shipping policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer free standard shipping on all orders over $50. Standard shipping takes 3-7 business days. Express shipping is available for $12.99 with 1-2 business day delivery."
      }
    },
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We accept returns within 30 days of purchase. Items must be unworn and in original packaging. Return shipping is free for US orders. Refunds are processed within 5-7 business days."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer international shipping?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we ship to over 40 countries. International shipping rates are calculated at checkout based on destination and order weight. Delivery typically takes 7-14 business days."
      }
    }
  ]
}
</script>

The structure is rigid. FAQPage contains mainEntity, which is an array of Question objects. Each Question has a name (the question text) and an acceptedAnswer of type Answer with a text property.

Get any of this nesting wrong and the schema fails validation.

Where to Add FAQ Schema on Shopify

Product Pages

Product pages are the highest-value location for FAQ schema. Common product-level questions:

• Shipping and delivery times
• Return and exchange policies
• Sizing and fit guidance
• Material and care instructions
• Warranty information

Place the FAQ schema in your product template, after the main product section. Only include questions that are actually visible on the page — schema must match visible content.

{% comment %} In sections/main-product.liquid or templates/product.liquid {% endcomment %}

{% if product.metafields.custom.faq_questions != blank %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {% assign faqs = product.metafields.custom.faq_questions.value %}
    {% for faq in faqs %}
    {
      "@type": "Question",
      "name": {{ faq.question | json }},
      "acceptedAnswer": {
        "@type": "Answer",
        "text": {{ faq.answer | strip_html | json }}
      }
    }{% unless forloop.last %},{% endunless %}
    {% endfor %}
  ]
}
</script>
{% endif %}

This approach uses Shopify metafields to store FAQ data per product. You manage the questions in Shopify admin; the schema generates automatically.

Collection Pages

Collection pages can include category-level FAQs (e.g., "What makes organic cotton different?" on a collection page for organic products). The schema structure is identical — just place it in your collection template.

Standalone FAQ Pages

If your store has a dedicated FAQ page, this is the most natural fit for FAQ schema. Create a page template (page.faq.liquid) or use a custom Liquid section:

{% comment %} templates/page.faq.liquid {% endcomment %}

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {% for block in section.blocks %}
      {% if block.type == 'faq_item' %}
      {
        "@type": "Question",
        "name": {{ block.settings.question | json }},
        "acceptedAnswer": {
          "@type": "Answer",
          "text": {{ block.settings.answer | strip_html | json }}
        }
      }{% unless forloop.last %},{% endunless %}
      {% endif %}
    {% endfor %}
  ]
}
</script>

This uses Shopify's section blocks so store owners can add/edit FAQ items through the theme editor without touching code.

Common FAQ Schema Validation Errors

These are the errors that break FAQ schema most often. Each one will cause the Rich Results Test to flag your markup as invalid.

Missing mainEntity

The Question array must be inside a mainEntity property on the FAQPage. This is the most common structural error.

Wrong:

{
  "@type": "FAQPage",
  "question": [
    { "@type": "Question", "name": "..." }
  ]
}

Correct:

{
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question", "name": "..." }
  ]
}

The property must be mainEntity, not question, not questions, not items.

Wrong @type Nesting

The hierarchy must be exact: FAQPage > mainEntity > Question > acceptedAnswer > Answer.

Wrong:

{
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": "We accept returns within 30 days."
    }
  ]
}

Correct:

{
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We accept returns within 30 days."
      }
    }
  ]
}

acceptedAnswer must be an Answer object with a text property — not a plain string.

HTML in Answers

FAQ schema answers support limited HTML. Google allows: <h1> through <h6>, <br>, <ol>, <ul>, <li>, <a>, <p>, <div>, <b>, <strong>, <i>, <em>.

Google does not allow: <script>, <style>, <iframe>, or any JavaScript.

For Shopify Liquid templates, strip unwanted HTML:

"text": {{ faq.answer | strip_html | json }}

Use strip_html to remove all HTML tags, or selectively allow basic formatting if your answers need links or lists. The safest approach is plain text — it always validates.

Trailing Commas in Liquid Loops

This Liquid error breaks JSON syntax and is invisible until validation:

Wrong:

{% for faq in faqs %}
{
  "@type": "Question",
  "name": {{ faq.question | json }}
},
{% endfor %}

The last item in the array gets a trailing comma, which is invalid JSON.

Correct:

{% for faq in faqs %}
{
  "@type": "Question",
  "name": {{ faq.question | json }}
}{% unless forloop.last %},{% endunless %}
{% endfor %}

Always use {% unless forloop.last %},{% endunless %} to handle commas in Liquid loops.

Duplicate FAQ Schema

If you use a Shopify SEO app that adds FAQ schema and you also add it manually, Google sees duplicate FAQPage entities. This isn't catastrophic, but it creates validation noise and can confuse which version Google indexes.

How to detect: View page source and search for FAQPage. If it appears more than once, you have duplicates.

How to fix: Choose one source. Either use your app's FAQ schema or your custom implementation — not both. If your app handles it well, remove your custom code. If you need more control, disable the app's FAQ feature and manage it manually.

Run a JSON-LD Audit to detect duplicate FAQ schema across your entire site.

Validating FAQ Schema

After adding FAQ schema to any page:

Step 1: Google Rich Results Test. Paste the page URL. Look for the "FAQ" rich result type. Even though Google won't show FAQ rich results for most sites, the test still validates the schema structure.

Step 2: Schema.org Validator. For deeper validation against the full Schema.org spec. Catches issues the Rich Results Test misses, like deprecated properties or incorrect data types.

Step 3: View Page Source. Search for application/ld+json and manually inspect the generated JSON. This catches Liquid rendering issues that tools won't flag until the page is live.

Step 4: Automated validation. For stores with FAQ schema on many pages, run a JSON-LD Audit to validate FAQ markup across your site in bulk. The audit checks structure, nesting, and content compliance.

Dynamic FAQ Schema with Shopify Metafields

For stores with product-specific FAQs, hardcoding questions in templates doesn't scale. Use Shopify metafields to manage FAQ content per product, then generate schema dynamically.

Step 1: Create a metafield definition.

In Shopify Admin > Settings > Custom data > Products, create a metafield:

• Name: FAQ Questions
• Namespace and key: custom.faq_questions
• Type: JSON (or list of metaobjects for structured data)

Step 2: Add FAQ data per product.

In each product's metafields, add your Q&A pairs:

[
  {
    "question": "How should I care for this product?",
    "answer": "Machine wash cold, tumble dry low. Do not bleach."
  },
  {
    "question": "Does this product come with a warranty?",
    "answer": "Yes, all products include a 1-year manufacturer warranty."
  }
]

Step 3: Generate schema from metafields.

The Liquid template from the "Product Pages" section above handles this automatically — it reads from product.metafields.custom.faq_questions and generates validated JSON-LD.

This approach lets non-technical team members manage FAQ content through Shopify admin while the schema stays perfectly structured.

FAQ Schema and AI Visibility

Even without FAQ rich results in Google, FAQ schema is one of the most AI-friendly structured data types you can add.

When AI shopping assistants answer questions like "What's the return policy for [brand]?" or "Does [brand] ship internationally?", they look for structured Q&A data. FAQ schema provides that in an unambiguous format.

Google's AI Overviews similarly extract FAQ data when generating informational answer cards about products or brands.

The investment is minimal — a single JSON-LD block per page — and the returns are growing as AI systems become primary pathways for product discovery.

Next Steps

1. Decide which pages need FAQ schema (product pages, FAQ page, key collection pages)
2. Set up metafields if you want dynamic, per-product FAQs
3. Add the JSON-LD template from this guide
4. Validate with the Rich Results Test
5. Run a JSON-LD Audit to check all FAQ schema across your site

For implementation details on other schema types, see the Product Schema template and JSON-LD for Shopify guide. To understand what your FAQ schema actually qualifies for in search results, read our Rich Results eligibility guide.