FAQ Schema in 2026: What It Does Now and How to Add It

FAQ schema is FAQPage structured data: a block of JSON-LD code that labels the questions and answers on a page so machines can read them as Q&A pairs. It no longer earns FAQ rich results in Google, because Google stopped showing them for every site on May 7, 2026, but the markup is still valid Schema.org vocabulary and the visible FAQ it describes can still pull its weight for shoppers.

This guide is for e-commerce and Shopify teams deciding what to do with FAQ schema now. You'll get a plain explanation of what changed and when, an honest answer on whether it helps in Google or in AI answers (with the sources), a decision table for FAQPage versus QAPage, a copy-ready JSON-LD example, and a testing workflow that still works after Google removed FAQ support from its own tools. If you already know you want the markup on a Shopify store, our walkthrough on how to add FAQ schema to Shopify covers the theme code.

What is FAQ schema?

FAQ schema is the common name for the FAQPage type on Schema.org, which defines it as a WebPage presenting one or more frequently asked questions. It sits under Thing, CreativeWork and WebPage in the Schema.org hierarchy, so it inherits the general page properties. The questions themselves are Question items listed in the page's mainEntity, and each question points to an Answer through acceptedAnswer.

There are two layers people mix up, and keeping them apart answers most questions about FAQ schema:

• The markup. The FAQPage JSON-LD in your page source. This is vocabulary, maintained by Schema.org, and it is still valid.
• The search feature. The expandable question dropdowns Google used to show under a result. This was Google's display choice, and it has been retired.

The markup never did the persuading. The questions and answers did. Structured data just made them easier for software to read, which is why the content decision and the markup decision deserve separate answers.

Which formats work

Google supports JSON-LD, Microdata and RDFa, and its introduction to structured data says it generally recommends JSON-LD if your setup allows it. JSON-LD lives in its own script tag, so you can add or remove it without touching your visible template, which is why every example in this guide uses it.

What happened to FAQ rich results?

Google removed them in two steps, about three years apart. If you read an older guide that promises bigger listings from FAQ schema, it was written before one or both of these changes.

The 2023 change was framed as a way to give a cleaner, more consistent search experience. In the same post, Google said you could drop the structured data but had no need to remove it proactively, because structured data that isn't used does not cause problems for Search. The 2026 retirement removed the last exception: government and health sites lost the feature too.

FAQ was not alone. Google's changelog shows How-to rich results deprecated in September 2023, seven more structured data features phased out from June 2025 (including course info, ClaimReview and vehicle listings) and practice problems retired in January 2026. Google keeps simplifying its results, so build your structured data plan on the features it still documents, not on screenshots from 2022.

Does FAQ schema still help in 2026?

For Google's search results, the markup on its own no longer produces a visible feature. That doesn't make the page section useless. It moves the value from the markup to the content, and the content case is strong.

The visible FAQ still converts

The questions shoppers ask before they buy (shipping times, sizing, returns, compatibility, ingredients) are the same questions that stall a purchase when they go unanswered. In QCK's A/B testing, FAQ sections are the only page type where every test won.

That result is about the on-page accordion that shoppers read, not about the JSON-LD behind it. It's the strongest argument for keeping a real FAQ on your homepage, collections and product pages whether or not you mark it up.

How FAQ sections compare with other page types

Across all 197 tests, FAQ sections had the smallest sample but the cleanest record. Product pages added the most revenue because they get the most traffic, but if you want a low-risk first test, an FAQ accordion is hard to beat.

Where the markup still earns a place

• Accuracy and consistency. Marking up the answers you show makes your page's Q&A explicit for any system that reads Schema.org, and the cost is a few lines of code.
• Other consumers of Schema.org. FAQPage remains part of the shared vocabulary that many search engines and tools parse. No search engine we know of currently promises a display feature for it, so treat this as a small, low-cost benefit, not a growth lever.
• Clean data for your own tools. Some site search, chat and help-center tools can read structured Q&A. Check your own stack before you count on this.

Does FAQ schema help with AI answers?

Not in any way Google has documented. Google's guide to optimizing for generative AI features, last updated July 10, 2026, says structured data isn't required for generative AI search and that there's no special Schema.org markup you need to add. It also says Google Search doesn't use special machine-readable files or markup made for AI. You can read it in full in Google's AI optimization guide.

The same guide still recommends structured data as part of your overall SEO strategy, because it helps with eligibility for the rich results Google does support. That's the honest position: FAQPage is not a ticket into AI Overviews or AI Mode, and nobody can show you a published rule from an AI platform saying it is.

What actually helps AI systems use your answers

• Write the question the way people ask it, as a heading or accordion label, then answer it in the first sentence.
• Keep answers specific. "Orders ship within 2 business days from Ohio" is quotable. "We pride ourselves on fast shipping" is not.
• Make the page crawlable and indexable. If a crawler can't load the answer, no markup will fix it. Our robots.txt and AI crawler tester shows which AI bots you allow.
• Put answers in the HTML. An FAQ that only loads after a click through JavaScript is harder for every system to read than one in the page source.

To see how answer-ready a page is, run it through our AEO checker. For the wider strategy, our AI search optimization team works on getting e-commerce brands cited in ChatGPT, Perplexity and Google AI answers.

When to use FAQPage (and when not to)

Pick the markup that matches who wrote the answers and how many questions the page holds. Google's QAPage documentation draws the line clearly: QAPage is for a page focused on a single question where users can submit answers, and it should not be used for FAQ pages or pages with multiple questions.

Four rules that keep FAQ markup safe

• Mark up only what readers can see. Google's general structured data guidelines say not to mark up content that is not visible to readers, and structured data issues can lead to a manual action that removes rich result eligibility.
• Match the words. The answer text in the JSON-LD should match the answer on the page, not a longer or keyword-stuffed version.
• Use one FAQPage block per page. Put every question in a single mainEntity list instead of scattering several FAQPage blocks across theme sections and apps.
• Don't repeat a sitewide FAQ everywhere. If the same shipping FAQ appears in your footer on every page, it adds nothing to each page's meaning. Mark it up on the page where it lives in full.

How to add FAQ schema, step by step

This works on any platform. On Shopify, the same JSON-LD goes in your theme or a metafield-driven section, as covered in our Shopify FAQ schema guide.

1. Write the visible FAQ first. Pull real questions from support tickets, reviews, chat logs and Search Console queries. Answer each in one to three sentences, starting with the answer.
2. Generate the JSON-LD. Paste your questions and answers into our free FAQ schema generator, or write it by hand using the pattern below.
3. Place one script block on the page. Add it to the template or section that renders the FAQ, so the markup and the visible answers come from the same source and can't drift apart.
4. Remove duplicates. Check whether your theme, an FAQ app or an SEO app already outputs FAQPage. Two generators often mean two conflicting blocks.
5. Validate the syntax and vocabulary. Run the live URL through our schema validator or the Schema Markup Validator.
6. Check what Google rendered. Use URL Inspection in Search Console to confirm the indexed page contains the FAQ text and the markup.
7. Re-check after theme or app updates. Template changes are the most common way markup and visible answers fall out of sync.

A copy-ready FAQPage example

<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "How long does shipping take?", "acceptedAnswer": {"@type": "Answer", "text": "Orders ship within 2 business days and arrive in 3 to 5 business days in the US."}}, {"@type": "Question", "name": "Can I return an item?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Unworn items can be returned within 30 days for a full refund."}}]}</script>

Replace the sample questions with your own, keep the text identical to what's on the page, and add more Question objects inside the same mainEntity list.

How to test FAQ schema now

Testing changed with the retirement. Google's Rich Results Test checks markup against the rich result features Google supports, and with FAQ removed from Google Search, you shouldn't expect it to report an FAQ result. Use tools that check what you actually need to know.

• Syntax and vocabulary: the Schema Markup Validator checks any Schema.org type, including FAQPage. Our schema validator pulls every JSON-LD block from a live page so you can spot duplicates.
• What Google saw: URL Inspection in Search Console shows the indexed HTML and the Google-selected canonical, so you can confirm the right version of the page was crawled.
• Supported features on the same page: keep using the Rich Results Test for Product, review snippets and breadcrumbs, which Google still documents. Our Product schema guide for Shopify covers those.

If your FAQ markup looks fine but something about the page seems off in Google, our diagnosis guide on FAQ schema not showing in Google walks through the symptoms one at a time.

What to do with your FAQ markup next

You don't need a cleanup project. Google said in 2023 that unused structured data causes no problems for Search, and nothing since has changed that. Spend the time on the visible FAQ and on the structured data Google still rewards.

• Keep accurate FAQPage markup on pages with a real, visible FAQ. It's cheap and harmless.
• Fix markup that doesn't match the visible answers, or that duplicates across apps. Inaccurate markup is the only version with real downside.
• Stop adding FAQ blocks to pages purely for search space. That trade ended in Google on May 7, 2026.
• Invest in Product, Organization and breadcrumb markup, which still feed supported features. Our schema markup generator and schema markup guide cover them.
• Test the on-page FAQ accordion if you don't have one. It's the most consistent winner in QCK's test data.

If you'd like a second pair of eyes on your structured data and FAQ content, our technical SEO team can review it, or you can book a free call.