← Insights

Shopify FAQ schema: Google dropped the rich result, so what is it for now?

Google stopped showing the FAQ rich result on 7 May 2026. What that means for Shopify FAQ markup, and how to write FAQ blocks that still help.

7 min read

Contents · 8 sections

Does FAQ schema still give a Shopify store rich results?

No. Google's Search documentation updates log a "Deprecating the FAQ rich result feature" entry dated May 8, which says the feature "will no longer appear in Google Search starting May 7, 2026". A later entry, dated June, says Google removed the documentation for the FAQ rich result feature because it "is no longer shown in Google Search results". The old FAQ structured data page now lands on that changelog.

The same log holds an older entry, listed under September 2023, that reads: "Updated the FAQ structured data documentation to state that the feature is only shown for well-known, authoritative government and health websites." So for a typical online store the expandable question list under a result was already out of reach for years before it was switched off for everyone.

If an agency, an app or a checklist told you FAQ markup gets a store extra space in search results, that advice is out of date. Ask what it is based on.

Is the markup itself still valid?

Yes. schema.org defines FAQPage as "a WebPage presenting one or more 'Frequently asked questions'", and it sits beside QAPage for pages built around user-submitted answers. The vocabulary did not change because one search feature ended. Other consumers of structured data may read it, and we do not know which ones do, so we will not promise any.

What we can say from the sources above is narrow:

  • Google no longer shows the FAQ rich result, and no longer documents how to qualify for it.
  • Nothing we read says FAQ markup is penalised. A page that keeps correct FAQPage markup carries no known cost beyond the upkeep.
  • Nothing we read says it helps rankings either. We found no source that supports that claim, so we leave it out.

Should you add it anyway?

Our view, which is a judgement and not something Google states: do not spend development time on the markup for a store. Spend it on the questions.

If your theme already prints FAQPage from an app, you do not need to rip it out in a hurry. Check it stays truthful: every question and answer in the markup must still be visible on the page, and any answer you edit on the page must change in the markup too. Markup that describes text no longer on the page is a bug you created yourself.

If you are choosing between building new markup and fixing something that affects revenue or the rich results that do still exist, fix the second. For a store those are the Product data on every product page, covered in the product schema guide, and the collection markup in the collection page schema guide.

What makes a good FAQ block on a Shopify page?

The content is the part that still works, with or without a search feature attached. A few rules we use when reading a store:

  1. Questions come from real customers. Pull them from support email, chat transcripts and returns notes. If you have none, you probably do not have enough traffic for an FAQ to matter yet.
  2. Answer the objection in the first sentence. "Yes, returns are free within the window listed in our policy" beats a paragraph that circles it. Link the policy page for the details instead of copying them.
  3. Put the FAQ where the doubt happens. Shipping and returns questions belong on the product and cart pages, near the button. A single FAQ page that nobody opens is the weakest placement.
  4. Keep it short. Five questions that are asked often beat twenty that are not.
  5. Never put a price or a promise in an answer you do not control. Anything that changes, such as delivery times, should link to the one page that owns it, so there is a single source to update.

How do you build the block in a theme?

Keep it plain HTML. Questions and answers in <details> and <summary> elements need no JavaScript and keep the answer in the initial HTML so crawlers and shoppers both get it. A theme section with repeating blocks can render them, so merchants edit questions in the theme editor and do not touch code.

Two cautions. First, closed <details> content is part of the page source, but test your theme before relying on any custom accordion: some accordions build the answer only after a click. Second, if you previously added FAQPage JSON-LD through an app or a theme snippet, open the page source (not the inspector) and search for application/ld+json to see what is actually printed. Compare it with what a shopper sees.

What about FAQ content for AI answers and other search features?

You will see claims that FAQ blocks and markup are the way to get quoted by AI assistants. We have not read a primary source that says so, and Google's changelog, the document we did read, says nothing of the kind about FAQ markup. What the changelog does show is that the feature people optimised for was removed, which is a good reason to be careful with promises built on markup alone.

The safer position is the unglamorous one. Write answers that stand on their own in two or three sentences, name the product or policy they refer to, and keep them accurate. A reader, a crawler and an assistant that summarises your page all get the most from text that is specific and true. If you want the longer argument on that, see our note on getting a store recommended by AI.

How do you check what your pages print today?

Five minutes and a browser:

  1. Open a page that has an FAQ and view its source.
  2. Search for FAQPage. If it is absent, you have nothing to maintain.
  3. If it is present, compare each question and answer with the visible text. They should match exactly.
  4. Remove markup for pages whose FAQ you deleted, so no markup describes absent content.
  5. Do not expect anything to change in Search Console afterwards. The rich result report for a deprecated feature is not a measure of success.

What to do with this

Decide per page. If an FAQ answers questions your customers actually ask, keep it, keep it visible, and update it when policies change. If you were building FAQ markup purely for search results, stop. If you want someone to read your store and say which structured data and page content are worth your time, that is what the Store Teardown is for, and the services page lists the rest of what we do.

Next step

Own your growth.Start with the teardown.

Read it, then decide whether you want us to fix what it finds.