November 2, 2026
Add FAQ schema to a Shopify product page by writing the questions visibly on the page first, in a metafield driven accordion, then outputting a JSON-LD block in the same template that reads those exact metafields. If the schema and the visible text match, the markup is valid and eligible. The common failure is schema injected by an app for questions that appear nowhere on the page; that pattern was deprecated by Google for most sites and can be ignored or flagged.
FAQ schema on product pages attracts store owners for the right reason: real product questions, sizing, shipping, care, compatibility, are exactly what buyers type into search, and a page that answers them visibly is a better page even before any markup exists. The markup is the easy part. The discipline is keeping the structured data an honest copy of what the page says.
This setup uses metafields so each product carries its own questions, and a single Liquid block in the product template so the schema is generated from the same source as the visible accordion. One source, two outputs, no drift. Drift is what breaks these implementations over time.
Create product metafields for question and answer pairs; three to five pairs cover most products without bloating the page. A simple structure is a list of single line texts alternating question and answer, or a small JSON metafield if your team is comfortable editing it. Simpler wins for stores where staff update products: a format a merchandiser can edit at midnight beats an elegant one only a developer can touch.
Render the metafields visibly in the product template as an accordion or a plain stacked section below the description, styled to match the theme. This visible block is not optional decoration. It is the content the schema describes, and it does the customer facing work: a buyer whose question is answered on the page is a buyer who does not need a support ticket or a competitor's tab.
Add a Liquid snippet that loops over the same metafield list and prints a script tag of type application/ld+json containing an FAQPage object whose mainEntity entries take their name and text directly from the metafield values. Strip HTML from the answer text in the schema output; structured data answers should be plain text. Escape quotes properly, Liquid's json filter handles most of this cleanly, and resist hand writing schema per product in the theme editor, which is how mismatches are born.
Validate before you scale it. Run one product URL through Google's Rich Results Test and a JSON validator, check that the questions detected match the visible accordion word for word in substance, then roll the snippet to every product template. One verified product proves the mechanism. Skipping validation and trusting the loop is how stores ship ten thousand pages of malformed JSON with total confidence.
Google restricted FAQ rich results to well known authoritative sites, mainly government and health, so most stores should not expect the expanded FAQ display in results anymore. Set expectations accordingly: the value now is a clearer page, better answers for AI driven search surfaces that read structured data, and content that earns its place by helping buyers. Stores still promised rich result magic by an app are buying a 2021 feature at 2026 prices.
Keep the questions product specific and genuinely asked. Pull them from support tickets, product reviews, and returns reasons for that product or its close family. Generic questions pasted across the catalog, same shipping question on four hundred products, dilute the value and look exactly like what they are. Five real questions beat twenty templated ones, and they take less maintenance when the answers change.
Related reading: Add a Backorder Notice on a Shopify Product Page That Buyers Actually Read, How to Add Recently Viewed Products to a Shopify Store, and Sticky Add to Cart on Shopify: Setup and Limits.
It no longer wins the expanded FAQ display for most commercial sites, since Google narrowed that feature. It still structures your answers for search and AI systems that parse pages, and the visible Q and A block improves the product page itself. Treat schema as documentation of good content, not as a ranking trick, and the investment holds up.
A mismatch between the schema and the visible page, usually from an app injecting markup for content that is not rendered, or from answers edited in one place and not the other. Generating both from the same metafield removes the mismatch structurally. The second common break is HTML left inside the JSON answers, which plain text output prevents.
Three to five genuine ones. Fewer looks thin and misses real buyer questions; more turns the product page into a support document and pushes the buy button into exile. If a product honestly generates ten questions, the top five belong on the page and the rest belong in a linked buying guide.
A site level FAQ page with its own visible content is the right home for global questions. Putting identical shipping schema on every product page adds noise and maintenance without adding product value. Keep product schema product specific, and let the policy pages carry the policies.