How to Add FAQ Schema to Shopify in 2026—and When Not To

How should visible questions map to Question and Answer?

Each marked-up Question must match one question visibly present on that URL, and its accepted Answer must contain the complete visible answer, including material limits. Preserve meaning rather than exact formatting. Never mark up hidden content, reviews, forum threads, customer submissions, or answers found only elsewhere.

Schema.org defines FAQPage, Question, and Answer. A collapsed accordion qualifies only when its complete answer is rendered and accessible; content on another URL does not match.

How can Liquid produce safe illustrative JSON-LD?

Liquid should serialize the strings used by the visible FAQ, not copies that can drift. Shopify’s json filter handles quoting and escaping for string values. The one-question pattern below is illustrative: replace its placeholder settings and wire it to the store’s actual visible section data.

Shopify documents the json filter and theme sections. This example assumes plain-text settings rendered by that section.

{% assign faq_question = section.settings.faq_question_1 %}
{% assign faq_answer = section.settings.faq_answer_1 %}
{% if faq_question != blank and faq_answer != blank %}
  <section class="faq-item">
    <h3>{{ faq_question | escape }}</h3>
    <p>{{ faq_answer | escape | newline_to_br }}</p>
  </section>
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [{
      "@type": "Question",
      "name": {{ faq_question | json }},
      "acceptedAnswer": {
        "@type": "Answer",
        "text": {{ faq_answer | json }}
      }
    }]
  }
  </script>
{% endif %}

Do not add this beside an app graph. Production needs its real block loop, accessible headings, and complete answers. A FAQ schema generator can frame a draft; the owner must map and verify the output.

How should you validate FAQPage after rich-result removal?

Validate JSON syntax, Schema.org vocabulary, and equality with the rendered page separately. After Google removed FAQ rich results, its Rich Results Test may not list FAQ as a supported appearance. That absence is not a syntax verdict, and a valid graph is not a display promise.

Check the Schema.org validator, a JSON parser, JSON-LD 1.1, and RFC 8259, then compare final HTML with visible wording. Rich Results Test silence cannot prove valid or invalid JSON.

What should the pre-publish validation checklist include?

A pre-publish review should prove one maintained source produces the visible FAQ and JSON-LD, without a duplicate owner or unsupported claim. Test representative templates and markets, not one hand-picked URL. Save rendered output and validator evidence so later theme or app changes can be compared.

• One owner and one FAQPage graph per page
• Complete visible question-answer pair on the same URL
• Equivalent rendered content and JSON-LD
• Valid JSON and Schema.org relationships; no hidden or user-submitted content
• No invented Person credentials, FAQs, reviews, ratings, prices, policies, or outcomes
• Representative mobile, desktop, market, and template checks with dated evidence

How do you maintain FAQ answers after publishing?

FAQ maintenance is policy and catalog maintenance, not a one-time SEO task. Assign an owner and review whenever shipping, returns, prices, compatibility, warranties, availability, or referenced policies change. Update both outputs from the shared source, or remove the stale question and its graph entry together.

1. Inventory marked URLs and owners.
2. Watch policy, product, market, and app changes.
3. Edit the shared visible answer.
4. Compare rendered content with the graph.
5. Validate representative templates after releases.
6. Log date, owner, evidence, and next trigger.

Do not add dates merely to imply freshness. Record what changed, why the answer is accurate, and which templates were checked.

What can StoreCited check?

StoreCited can flag public issues such as duplicate FAQPage graphs, missing visible counterparts, malformed JSON-LD, or inconsistent entities at scan time. It cannot edit Shopify, identify every private app source, monitor live citations, generate publish-ready schema or FAQs, or guarantee search or AI outcomes.

StoreCited is an Organization, not an invented Person. Run the free StoreCited readiness scan to prioritize public checks; assign code ownership and verify implementation. See adding Product schema to Shopify for adjacent markup.