You did everything the old guides told you to do. FAQ schema, live on your Shopify store, validating clean in every testing tool you tried. And still, nothing changes in Google’s search results. That’s not a bug on your end — Google switched the feature off.
Two other guides on this blog already cover schema markup. Our structured data guide walks through the full set your theme is probably missing — Product, Organization, WebSite, BreadcrumbList, and FAQPage among them. Our product schema guide is a deep-dive on the one that gets star ratings and pricing showing in search. Neither one tells you what actually happened to the FAQ rich result, because it changed after both were written. This post is specifically about FAQ schema on Shopify: what it used to do, what it can’t do anymore, and whether it’s still worth having on your store.
Plug In SEO still adds FAQPage JSON-LD to your store automatically, alongside Product, Organization, and BreadcrumbList schema. That part hasn’t changed. What changed is what Google does with it once it arrives — read on before you assume something’s broken.
Why your FAQ schema isn’t showing up as a rich result
The bottom line: it’s not your markup, your page structure, or how many questions you have. Google turned the FAQ rich result off entirely, for every site, starting May 7, 2026.
Google’s own Search Central changelog documents the timeline plainly. A May 2025 entry added a deprecation notice to the FAQ rich result documentation: the feature “will no longer appear in Google Search starting May 7, 2026”. A June 2026 entry confirms the follow-through. That entry removed the documentation itself, with the note: “The FAQ rich result feature is no longer shown in Google Search results”. From there, the teardown kept going. The Rich Results Test and the Search Console rich-result report dropped FAQ support that same month. Search Console API support for it drops in August 2026. Check Google’s current structured data gallery today, and FAQPage isn’t even on the list of supported types.
Maybe you added FAQPage schema before this year and it briefly worked. Maybe you’ve been troubleshooting a setup that looks technically correct but produces nothing. Either way, that’s the reason. There’s nothing left to debug. The feature your schema used to unlock doesn’t exist in Google Search right now.
Google Search Central, “Latest documentation updates,” changelog entries dated May 2025 and June 2026
It was never available to most Shopify stores anyway
Even before the May 2026 cutoff, this rich result was already out of reach for almost every Shopify merchant. Google had restricted it back in 2023 to “well-known, authoritative government and health websites”. That was never going to include a store selling candles or camping gear. For most merchants reading this, the honest history is two-part. The feature you were chasing had already narrowed to almost nobody, and now it’s gone for everybody. Neither part of that story is about something you did wrong.
Is FAQPage schema still worth adding to your store?
The bottom line: yes, but not for the reason the old advice gave you. It’s a small, low-effort addition — not a growth lever on its own.
FAQPage is still a valid schema.org type, and Google turning off its own search feature doesn’t erase that. Bingbot, DuckDuckGo, PerplexityBot, and the general crawl of bots feeding AI answer engines can all still read FAQPage JSON-LD the same way they always could. This is Google’s own product decision, not an industry-wide retirement of the schema.
What the markup does (and doesn’t) prove about AI citations
Where the honest caveat comes in: the evidence that the markup itself drives AI citations is weaker than a lot of current advice implies. One industry analysis of AI-platform citations found no measurable correlation between how much schema markup a site had and how often it got cited. Microsoft has said schema markup helps its own models understand a page’s content for Copilot. That’s a real statement, but a narrower one than “adding FAQPage schema gets you quoted more”. Neither point proves markup is worthless. Both point the same direction: don’t expect the JSON-LD by itself to move the needle.
What actually seems to matter is the visible content underneath the markup. A real question, a real direct answer, formatted so a person or a crawler can read it without effort — that’s the part AI engines actually have to work with when they generate an answer. The schema is a cheap, structured restatement of content that should already exist on your page for your customers. Add it because it costs nothing once the content’s there, not because it’s a strategy on its own. Our guide to optimizing for AI Overviews covers this same content-first principle in more depth.
Industry analysis, “FAQ Rich Results Deprecated: Google’s May 2026 Change,” getpassionfruit.com
Common FAQ schema mistakes worth fixing anyway
The bottom line: none of these get you a rich result back. All three are still worth fixing — they’re either a duplicate-content risk, a structured-data policy risk, or just a page that reads badly.
Reusing identical FAQ text across dozens of pages
If your FAQ block is the same six questions and six answers pasted onto every product page in a collection, you’ve built a thin, duplicate content pattern — independent of whatever schema sits on top of it. It also quietly defeats the point of the markup. If your JSON-LD says the same thing on 200 different URLs, it isn’t telling a crawler anything page-specific about any of them. Product-specific questions — does this run true to size, what’s the return window on this item — carry more weight than a boilerplate block copied everywhere.
Too many questions, or too few
There’s no official number to hit anymore — the Google documentation that might once have suggested one doesn’t exist today. Treat it as a judgment call instead of a technical limit. A product page with fifteen generic questions reads like someone built it to stuff keywords rather than answer anything. A page with one lonely question isn’t really an FAQ. Somewhere in the middle — four to eight real questions a customer would actually ask. That reads honestly and is genuinely more useful to a shopper skimming the page.
Schema that doesn’t match what’s actually on the page
This one still has teeth, rich result or not. Google’s structured data guidelines have always treated markup describing content the visitor can’t actually see as a policy violation, not just a wasted effort. That enforcement mechanism is separate from any specific rich result, and it hasn’t gone anywhere. If your FAQPage JSON-LD lists a question and answer that never appears as visible text on the page, pull it. Every question in your markup should be one a visitor can actually read and expand on that same URL.
How to check what’s on your Shopify store right now
The bottom line: this is a five-minute check, not a rebuild. You’re confirming the schema exists and matches your visible content — nothing more.
-
Open a product or FAQ page and view its source, or use Google’s Rich Results Test. It still validates FAQPage markup for syntax, even though the rich result itself no longer renders. Search for
"@type": "FAQPage"in the page source. - Read every question and answer in the JSON-LD against the visible page. If a question sits in the markup but isn’t visible anywhere on the page, that’s the mismatch to fix first.
- Check how many pages share identical FAQ text. If it’s the same block on every product page, trim it down to genuinely shared questions (shipping, returns) and add page-specific ones only where they’re real.
- If you’re using Plug In SEO, the FAQPage JSON-LD is already generated from whatever FAQ content you’ve added to the page. There’s no separate schema setting to toggle. The fix, if there is one, is in the content itself, not in the app.
Frequently asked questions
Why isn’t my FAQPage schema showing as a rich result in Google?
Because the feature doesn’t exist in Google Search anymore. Google stopped showing FAQ rich results on May 7, 2026, and removed the supporting documentation in June 2026. It’s not a markup error or a page-quality issue on your end. No Shopify store, and no site of any kind, currently gets this rich result from Google.
Is it still worth adding FAQ schema to a Shopify store?
Yes, as a low-effort addition on top of real FAQ content you’d want on the page anyway. Bing, DuckDuckGo, and various AI crawlers still read FAQPage markup. What’s not proven is that the markup itself increases how often AI engines cite you. One analysis found no correlation between schema coverage and AI citation rates. Treat the schema as cheap insurance, not a strategy.
Does Plug In SEO still handle this automatically?
Yes. Plug In SEO generates the FAQPage JSON-LD from your page’s FAQ content automatically, the same as it always has, alongside Product, Organization, and BreadcrumbList schema. What changed is downstream of that — Google no longer turns valid markup into a rich result, on any site.
How many questions should a Shopify FAQ section have?
There’s no official minimum or maximum anymore. Somewhere between four and eight genuine questions — ones a real customer would actually ask about that specific product or policy — reads well to both shoppers and crawlers. Padding a page with generic questions to hit a number is a worse outcome than having fewer, real ones.
Can I reuse the same FAQ text across multiple product pages?
You can for genuinely shared questions, like shipping and returns. It becomes a problem when the entire FAQ block — same questions, same answers, word for word — appears on every product page in your catalogue. That reads as thin, duplicate content, and it makes the schema on each page say nothing specific about that page.
Do AI engines like ChatGPT or Perplexity still use this markup?
They can still crawl and parse it. PerplexityBot and other AI/RAG crawlers aren’t affected by Google’s decision to drop its own rich result. But the evidence that the markup itself drives more citations is weak. The visible Q&A content on the page is what actually gets extracted and quoted. The schema is a structured echo of that content, not a substitute for it.
How is FAQ schema on Shopify different from the structured data and product schema guides on this blog?
Those two guides cover the full schema set your theme is likely missing: Product, Organization, WebSite, BreadcrumbList, and FAQPage among them. They were written before Google discontinued the FAQ rich result. This post is specific to FAQ schema on Shopify: what changed, whether it’s still worth having, and the content mistakes worth fixing regardless. Read the structured data guide first if you haven’t touched schema at all; come back here once you’re specifically trying to understand your FAQ setup.
Let Plug In SEO handle the schema, so you can focus on the content
Plug In SEO adds Product, FAQPage, Organization, and BreadcrumbList schema to your store automatically. The rich result Google used to offer for FAQ pages is gone — but the markup itself, and the FAQ content underneath it, are still worth getting right.
Related reading: FAQ schema is one piece of the picture — see our guide to metafields and SEO for another source of structured data most stores leave unused.