Shopify product FAQ schema and the visible FAQ are different things. Shoppers read the questions on the page. Structured data is a machine-readable copy of those same questions. Product FAQs for AI Crawler emits FAQPage JSON-LD from both the product block and the global block, in the light DOM, outside the widget's shadow DOM. The script is built from the FAQ data. Question and answer text is stripped of HTML and escaped so the JSON-LD is valid. A crawler can read it without running the widget.
That markup is not a promise of a rich result. Google's Search Central changelog says the FAQ rich result no longer appears in Google Search. On 8 May 2026 the changelog recorded a deprecation notice: the feature would no longer appear starting 7 May 2026. A June 2026 entry, with the 15 June 2026 documentation updates, says Google removed the FAQ rich result documentation because the feature is no longer shown. The old FAQ structured-data URL now redirects to that changelog. Add the answers on the page because shoppers need them. A Google FAQ rich result is not the outcome the current changelog describes.
Visible FAQ versus schema
The visible list is what a person opens. In this app it renders in a shadow DOM as Accordion, Grid/cards, Boxed, or Minimal. The JSON-LD is a separate block in the light DOM, with a FAQPage type and a list of questions and accepted answers taken from the same saved FAQs. If you change an answer and save, the group write updates the fields and items, and the metafield is what the storefront serves. The structured data should match that saved text, because it is generated from it.
Guides that tell every store to paste a FAQ script into the theme are solving a different era of search results. Pasting a second copy also risks two descriptions of the same product. Prefer one source. If this app is emitting the FAQPage from the widget's data, you do not need to paste another copy into a custom liquid block, and you should not paste one into a blog article either.
What Google currently says
The current public note is Google's Search Central updates, not a live FAQ rich-result guide. The May 2026 deprecation says the feature will no longer appear in Google Search starting 7 May 2026. The June 2026 removal says the documentation was taken down because the feature is no longer shown. An older 2023 post had already limited FAQ rich results to well-known government and health sites. The 2026 changelog goes further: the feature is no longer shown, and the documentation is gone.
Other search engines and assistants are not that changelog. Some may still read FAQPage markup. The catalog's reason for putting JSON-LD in the light DOM is so crawlers can read the questions without JavaScript. Reading is not the same as citing, ranking, or showing a special treatment. This article does not claim those outcomes. Recheck Google's changelog if you are making a decision months after this was written, because search display rules move.
- 7 May 2026: Google said the FAQ rich result would no longer appear, in the 8 May 2026 changelog entry.
- June 2026: Google removed the FAQ rich result documentation because the feature is no longer shown.
- The previous FAQ documentation URL redirects to the updates page.
What a theme or another app might add
A theme accordion you typed by hand may have no structured data at all. Another FAQ app may print its own FAQPage. If two apps are enabled, view the page source and see whether two FAQ blocks describe the same products. Disagreeing answers are a content problem before they are a schema problem. Turn one system off, or point them at different pages, so a crawler does not have to choose.
This app's product block reads the product FAQ metafield. The global block prints the shop-wide group. Both emit the JSON-LD. An empty group should not invent questions. If the source view shows questions you deleted, save the group again and reload. The storefront display comes from the metafield written at save time, not from a live call to render the list.
A check in the page source
Open a product that has a saved FAQ. View the page source and look for the FAQ questions as text in the HTML, and for a JSON-LD block whose type is FAQPage. You are confirming presence, not copying the block into another page. The questions in that block should be the questions visible in the widget. If the visible accordion says one care instruction and the structured data says another, treat that as a bug and fix the saved group rather than hand-editing the theme.
Then look at Google's result for the product, if you want to see what searchers see. Expect an ordinary result. The changelog says the FAQ rich result is no longer shown. A missing dropdown of questions under the blue link is consistent with that note. It is not, by itself, evidence that the app failed to emit the script. The source view is the check for emission. The search result is the check for a rich result Google has said it no longer displays.
Questions about product FAQ schema
Does this app output FAQPage JSON-LD?
Yes. The product block and the global block emit it in the light DOM, from the FAQ data, outside the widget shadow DOM.
Will Google show FAQ rich results for my products?
Google's May 2026 and June 2026 changelog entries say the FAQ rich result no longer appears in Google Search. Do not expect that treatment.
Should I paste schema into the theme as well?
If this app is already emitting the FAQPage for those questions, a second pasted copy is another source to keep in sync. Keep one source.
The listing is Product FAQs for AI Crawler.
The app behavior is documented on Product FAQs for AI Crawler. Put the answers on the product, confirm the source contains the same words, and judge the app by that, not by a rich result Google has withdrawn.