FAQ schema in 2026: what changed, and is it still worth adding?

What FAQ schema is

FAQ schema is structured data, usually written in JSON-LD, that labels the questions and answers on a page. It uses the schema.org type FAQPage, with each question marked as a Question and its answer as an Answer. For years, Google used it to show a FAQ rich result: questions that expanded under your link in search results, taking up more space.

For the bigger picture on structured data, see schema markup and our guide to schema markup for small businesses.

What changed, and when

Google's documentation changelog records the last two steps. In plain words: no site gets FAQ rich results on Google any more, whether it's a clinic, a government department or a large brand.

Is FAQ schema still relevant?

For Google rich results, no. Valid FAQPage markup won't make your result expand on Google any more. (For the rich result types that still exist, the Rich Results Test is the tool to use.)

What Google hasn't said:

• It hasn't asked sites to remove existing FAQPage markup.
• It hasn't said the markup is used for anything else in Search.

So treat it as optional. If it's already on your pages and matches the visible questions, there's no Google guidance saying you must take it off. If you're deciding whether to add it now, spend the time on the visible FAQ content instead. FAQPage remains a valid schema.org type, and other systems that read structured data may still use it, but no search engine has promised a benefit we can point you to.

Why visible FAQs still matter

The questions themselves are valuable, rich result or not:

• They answer real objections before a customer has to call: price, timings, what to bring, refunds.
• They match how people search. Many searches are questions, and Google shows related ones in People also ask.
• They're easy for AI answers to use. A clear question followed by a direct two-sentence answer is exactly the shape AI systems summarise. See AEO.

How to write a good FAQ section

1. 1Use real questions. From phone calls, WhatsApp chats, reviews, and the People also ask box for your service.
2. 2Answer in the first sentence, then add one or two sentences of detail.
3. 3Be specific: numbers, timings, conditions, not "it depends" without saying on what.
4. 4Keep it to the page's topic. A root canal page's FAQ is about root canals, not the clinic's parking.
5. 5Don't repeat the same FAQ on every page. Each page should answer its own questions.
6. 6Keep answers current, especially prices and policies.

How to create FAQ schema (if you still want it)

If you decide to add it, keep it accurate:

• Use JSON-LD in the page, with "@type": "FAQPage" and a mainEntity list.
• Each item is a Question with a name (the question) and an acceptedAnswer of type Answer with text (the answer).
• Every question and answer in the markup must also be visible on the page, word for word or close to it. Google's general structured data guidelines say markup should describe content that's visible to users.
• Don't put advertising in answers, and don't mark up questions users can't see.
• Check it with the Schema Markup Validator at validator.schema.org, which validates any schema.org type.

On WordPress, SEO plugins such as Rank Math and Yoast can generate it from an FAQ block; on other sites, your developer can add it to the page template.

What to do with existing FAQ markup

• It matches visible content: leaving it is fine; there's no Google instruction to remove it.
• It marks up questions that aren't visible, or is copied across many pages: clean it up. Markup that doesn't match the page goes against Google's structured data guidelines.
• A plugin adds it automatically and you don't want it: switch it off in the plugin's schema settings, and test a page afterwards.

Watch out for outdated advice

Many articles and plugin settings pages still describe FAQ schema as a way to "take up more space in Google". That stopped being true for most sites in 2023, and for all sites on May 7, 2026. If a provider sells FAQ schema as a ranking or visibility win on Google, ask them to show it working on a live search today.

A worked example

A diagnostic lab in Jaipur (a made-up example) has FAQPage markup on 60 test pages, all with the same five questions about home sample collection, only some of which are visible. After the change, the lab removes the duplicated markup from its template. Instead, each test page gets its own short visible FAQ: fasting needed or not, report time, and sample type, each answered in one or two sentences. The lab stops chasing a rich result that no longer exists and puts the effort into answers patients actually need. See our page for dental and medical clinics.

Which structured data is still worth it

For most small businesses: Organization or LocalBusiness on the home or contact page, BreadcrumbList for site structure, Article on blog posts, and Product where you sell products. Our schema markup guide lists the fields that matter, and the free business schema generator writes the LocalBusiness block for you.