Is FAQ schema still worth adding after Google retired FAQ rich results?
Last reviewed
Short answer
Google fully retired FAQ rich results in May 2026, so FAQPage markup no longer produces rich snippets for any site. The markup is still cheap to maintain and still machine-readable for other consumers, but the honest reason to write FAQs now is that question-shaped content is easy for AI systems to extract.
What actually happened
Google restricted FAQ rich results to well-known authoritative government and health sites in August 2023. That was a restriction, not a removal. The full retirement came later: Google added a deprecation notice in May 2026 saying the feature had stopped appearing, and removed the documentation entirely the following month.
So an article telling you FAQ schema will win you rich results is out of date regardless of when it was written. It will not, for anyone.
Why write FAQs anyway
Because the format matches how people ask and how assistants extract. A question as a heading with a direct answer immediately underneath is the single most extractable structure on the web. It requires no markup at all to work, which is rather the point.
The markup is still worth including. It is cheap, it is unambiguous for any parser, and it costs nothing to be machine readable. Just do not expect it to render as anything in Google, and do not let anyone sell it to you as a rich-result play.
How to write an answer that gets used
Answer in the first sentence. Not context, not a preamble, not a restatement of the question. Forty to sixty words, self-contained enough to make sense if it is lifted out of the page entirely, because that is exactly what happens.
Then add the nuance underneath for the human who kept reading. The Entitled FAQ is written this way, as is every page in this section: a direct answer block at the top, detail below it.
What Google says about schema and AI answers
Google's documentation for AI Overviews and AI Mode is blunt: there is no special schema.org structured data you need to add, and no new machine-readable files or markup. A page has to be indexed and eligible to show in Search with a snippet. That is the whole technical requirement.
The same page lists one structured data habit that still counts: markup that matches the visible text. Google's structured data guidelines say the same, so if you use FAQPage, it has to describe questions actually on the page.
What nobody has documented
As of November 2026, we found no documentation from OpenAI, Perplexity or Anthropic saying FAQPage markup changes whether a page is used in an answer. Not a ban, not an endorsement, nothing. A claim that FAQ schema gets you into ChatGPT is a guess with a sales pitch attached.
For products, OpenAI's feed spec excludes question-and-answer lists from its discovery data entirely. Product FAQs reach ChatGPT the way everything else does, as text in your description, which is why the description structure ends with real buyer questions answered plainly.
Product FAQs for Google AI Mode: the Merchant Center attribute
The one documented FAQ channel for AI shopping is a feed attribute, not page markup. Google says Merchant Center's question_and_answer attribute is primarily intended for conversational experiences such as AI Mode. It is optional, works in all countries, and Google recommends a supplemental data source for it.
It is one of the conversational attributes, and Google does not say it affects ranking or will always be used.
- Up to 30 question and answer pairs per product
- Each question and each answer up to 1,000 characters, 10,000 in total per product
- Product information only: no prices, dates or other time-bound details
- No keyword lists, and no repeating the title or description
How to add FAQ schema to a Shopify product page
Shopify does not generate it. The structured_data Liquid filter outputs schema.org Product or ProductGroup for products, not FAQPage. The job is to store the questions once and use them twice, on the page and in the markup, so the two cannot drift apart.
- Store the questions as data. Shopify's metaobjects documentation uses this exact example: an FAQ metaobject with question and answer fields, one entry per question.
- Show them on the page by connecting a section or block setting to it as a dynamic source in the theme editor. Support varies by theme.
- Output the JSON-LD from the same data in the product template.
- Skip products with no FAQs. Generic markup repeated on every product helps nobody.
A sample FAQPage block for a product
A minimal FAQPage block for one product question. Keep the text identical to what the page shows, and add one Question to mainEntity per extra question.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Is the Kiln & Co stoneware mug dishwasher safe?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. The glaze is dishwasher safe on the top or bottom rack. Avoid metal scourers, which can mark the matte finish." } } ] } </script>
JSON-LD is the format Google recommends. It will not render as a rich result in Google now. Its job is to state the answer in a form no parser has to guess at.
Frequently asked questions
Does FAQPage schema still produce rich results in Google?
No. Google fully retired FAQ rich results in May 2026 and removed the supporting documentation. The markup is still valid and still machine readable, but it will not render as a rich result for any site.
Should I remove FAQ schema from my pages?
No reason to. It is valid structured data, costs nothing to keep, and remains readable to parsers other than Google Search. Removing it gains you nothing.
Does FAQ content help with AI assistants?
Question-and-answer structure is unusually easy to extract, which helps regardless of markup. The gain comes from the writing pattern, a direct answer in the first sentence, more than from the schema wrapper around it.
How do I add FAQ schema to Shopify product pages?
Store the questions in a metaobject, show them on the page through a dynamic source in the theme editor, and output FAQPage JSON-LD from the same data in the product template. Shopify's structured_data filter does not produce FAQPage.
Does ChatGPT use FAQ schema?
Not that anyone has documented. As of November 2026, OpenAI publishes nothing saying FAQPage markup affects answers, and its product feed spec excludes question-and-answer lists from discovery data. Product FAQs reach ChatGPT as text in your description.
Do I need structured data to appear in Google AI Overviews?
No. Google says there is no special schema.org structured data needed for AI Overviews or AI Mode. A page must be indexed and eligible to show with a snippet. If you do add markup, it must match the visible text.
Sources
- Google Search Central: FAQPage structured data (deprecated)
- Google Search Central blog: HowTo and FAQ changes
- Google Search Central: AI features and your website
- Google Search Central: general structured data guidelines
- Google Search Central: documentation updates (FAQ rich result removal)
- Google Merchant Center Help: question_and_answer
- Google Merchant Center Help: conversational attributes
- OpenAI: product feed specification
- Shopify Help: metaobjects
- Shopify Dev: dynamic sources
- Shopify Dev: structured_data Liquid filter
Keep reading
Score your own catalog
Entitled grades every product against the rules on this page, explains each failure, and fixes them with AI you approve. The score is free forever.
