Shopify product FAQ schema: what it does and how to add it

Two separate things: the FAQ and the schema

It helps to separate two ideas that are often mixed together.

• A product FAQ is visible content on the page: a short list of questions and answers about sizing, delivery, materials, compatibility or care.
• FAQPage schema is structured data, usually JSON-LD in the page’s code, that describes those same questions and answers in a format machines can read.

The visible FAQ is useful on almost every product page because it answers objections at the moment of decision. The schema is optional and only appropriate when it describes questions that are actually displayed.

What Google shows today

For several years, FAQPage markup could make a search result expand with questions underneath it. In 2023 Google announced it would show FAQ rich results only for a limited set of well-known, authoritative government and health websites. For a typical Shopify store, adding FAQPage markup will therefore not produce that expanded result in Google Search.

That does not make the markup harmful or useless. It remains valid schema.org vocabulary, other search engines and tools may read it, and it describes your content clearly. But the main reason to add a product FAQ in 2026 is the shopper, not the rich result. Plan your effort accordingly.

Write questions customers actually ask

The best FAQ questions come from your own inbox, chat logs, reviews and returns reasons. Look for questions that:

• Come up repeatedly for this product or category.
• Block a purchase if unanswered (“Will this fit a 15-inch laptop?”).
• Lead to returns when misunderstood (“Does it run small?”).

Answer in two or three sentences, directly, starting with the answer. “Yes, the sleeve fits laptops up to 15.6 inches; it measures 38 × 26 cm inside.” is more useful than a paragraph that hides the answer at the end.

Avoid questions that exist only to repeat keywords (“Why is this the best leather wallet?”). They add nothing for shoppers and read as filler.

Step-by-step: adding a product FAQ in Shopify

1. Decide where the answers live. For FAQs that differ by product, store them per product — typically in a metafield or metaobject list — so you are not editing theme code for each item. For shared questions (shipping, returns), one shared block is fine.
2. Display them on the product template. Many Online Store 2.0 themes include a collapsible content or accordion block. Connect it to your metafield using dynamic sources in the theme editor.
3. Check the result on mobile. Accordions should be easy to tap, and answers should not push the add-to-cart button far down.
4. Add structured data only if it matches. If you add FAQPage JSON-LD, generate it from the same data that renders the visible questions, so the text never drifts apart.
5. Validate. Test the URL with Google’s Rich Results Test or the Schema Markup Validator to confirm the JSON-LD parses without errors.

Example JSON-LD structure

FAQPage markup is a list of Question items, each with an accepted Answer. Simplified, it looks like this:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Does the backpack fit a 15-inch laptop?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. The padded sleeve fits laptops up to 15.6 inches."
    }
  }]
}

In a Shopify theme you would output this in a Liquid snippet, looping over the same metafield that renders the visible questions. Keep your theme’s existing Product structured data as it is; FAQPage is an additional block, not a replacement.

Rules to stay within the guidelines

• Only mark up visible content. Every question and answer in the JSON-LD must appear on the page.
• Match the text. The marked-up wording should match the displayed wording.
• No advertising in answers. Answers should inform, not sell.
• One FAQPage per page. Avoid both an app and the theme emitting separate FAQ blocks for the same questions.
• Do not mark up user-submitted Q&A as FAQPage. Questions answered by multiple users fit the QAPage type instead.

Where else FAQ content helps

Clear question-and-answer content is easy for search engines and AI-driven answers to understand, because each answer is self-contained. It also reduces customer service load and returns. Those benefits apply whether or not any rich result appears. If a question becomes important enough, consider moving its answer into the product description itself (see writing product descriptions that rank).

Choosing which products get an FAQ

You do not need a custom FAQ on every product. Prioritise products where questions actually block purchases: items with sizing uncertainty, technical compatibility, assembly, or care requirements, and higher-priced products where shoppers research longer. For simple, low-price items, a shared FAQ block about delivery and returns is often enough.

A practical way to decide is to sort products by sessions and look at which ones generate the most pre-sales messages or returns. Those pages benefit most from specific answers, and the time you spend writing them reduces support work directly.

Review the questions every few months. Delivery times change, new variants raise new questions, and an answer that was accurate at launch can become wrong. Outdated FAQ answers do more harm than missing ones because shoppers trust them.

Checklist

• Three to six real customer questions per product or category.
• Short, direct answers that start with the answer.
• Questions stored per product (metafield or metaobject) where they vary.
• Visible accordion on the product page, tested on mobile.
• Optional FAQPage JSON-LD generated from the same data.
• Validated, with no duplicate FAQ blocks.

See the full product page SEO checklist for the rest of the structured data on a product page.

Frequently asked questions