FAQPage Schema for Google Rich Results: The Honest 2026 Guide

TL;DR

• FAQPage schema is structured data (JSON-LD) that labels your questions and answers so search engines and AI assistants can read them precisely.
• Since August 2023, Google only shows the classic blue FAQ rich result for well-known authoritative government and health sites, so most sites no longer get that expanded snippet.
• It is still worth adding, because it helps Google, ChatGPT, Perplexity, and Google AI Overviews understand and quote your answers, and good help-center tools add it automatically.

If you searched for FAQPage schema hoping to win the expanded blue accordion in Google search results, you deserve a straight answer: for almost every site, that result is gone. Google narrowed it sharply in 2023. But that does not make the markup useless. It quietly does a different and arguably more valuable job now, helping machines understand exactly what your answers are and where they live. This guide explains what FAQPage schema is, what actually changed, how to add valid JSON-LD in a few minutes, and why it still earns its place in 2026.

What FAQPage schema is

FAQPage schema is a small block of structured data, usually written in JSON-LD, that you place on a page containing a list of frequently asked questions and their answers. It uses the schema.org vocabulary: a FAQPage type that contains one or more Question items, each with an acceptedAnswer.

The point is precision. Plain HTML tells a browser how to display text. Structured data tells a search engine or an AI model what the text means: this string is a question, that string is the official answer to it. Instead of guessing, machines get an explicit map of your Q&A content.

You add it once per page, it sits invisibly in the source code, and it never changes what human visitors see. If you want the bigger picture on how structured data fits into ranking, read our guide on knowledge base SEO for Google.

The 2023 reality: who still gets FAQ rich results

Here is the part most outdated articles get wrong.

In April 2023 Google began limiting FAQ rich results, and in August 2023 it confirmed the change as permanent. The FAQ rich result, that expandable list of questions shown directly in search, now appears only for what Google calls well-known, authoritative government and health websites. Think national health services or official government portals.

For everyone else, including SaaS companies, e-commerce stores, agencies, and blogs, the FAQ rich result usually does not display anymore. Your FAQPage markup can be perfectly valid and pass every test, and you will still not see the blue accordion in your own search listing. That is expected behavior, not a bug in your markup.

So if an article promises you that adding FAQPage schema gets everyone an expanded snippet and more clicks, it is describing 2022, not 2026. Be skeptical of that claim. The honest framing is that the visible rich result is largely off the table for most sites, while the underlying value of clean, machine-readable Q&A data has grown.

How to add FAQPage schema (step by step)

You can add FAQPage schema by hand or let a help-center platform generate it. Here is the manual path so you understand what is happening under the hood.

1. Confirm the content qualifies. Use FAQPage markup only for genuine frequently asked questions written by you, where one answer follows each question. Do not use it for a forum thread with multiple user answers, that is a different type (QAPage).
2. Make sure every question and answer is visible on the page. Google requires that the marked-up content is the same content a human visitor can see. Never mark up hidden or different text.
3. Write the JSON-LD. Create a FAQPage object with a mainEntity array. Each entry is a Question with a name (the question) and an acceptedAnswer of type Answer with a text value. The answer text may contain limited HTML such as links and lists.
4. Place it in the page head or body. Drop the script tag into the page source. JSON-LD is the format Google recommends, and it does not need to wrap your visible HTML.
5. Validate it. Run the page through Google's Rich Results Test and the Schema Markup Validator. Fix any errors or warnings before publishing.
6. Submit and monitor. Make sure the page is indexable, then watch Search Console for structured data reports over the following weeks.

Here is a valid example for two questions:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Helpable host data in the EU?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Helpable is EU-built and hosts all customer data in Frankfurt and Amsterdam, so your help center stays inside the European Union."
      }
    },
    {
      "@type": "Question",
      "name": "Do I need a credit card to start a Helpable trial?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "You can try Helpable free for 7 days and explore every feature, including AI answers, custom domains, and automatic schema markup, before you decide on a plan."
      }
    }
  ]
}

Wrap that JSON in a <script type="application/ld+json"> tag when you embed it. Keep the answer text identical to what appears on the page.

Why it still matters for AI search

The visible rich result faded, but a bigger shift took its place. Search is no longer only ten blue links. People now ask ChatGPT, Perplexity, and Google AI Overviews direct questions, and those systems pull from the open web to compose answers.

Structured data is how you make your content easy for these systems to find, parse, and quote accurately. When your answers are explicitly labeled as answers to specific questions, an AI assistant has a much cleaner signal about what your page says. That raises the odds it surfaces your wording, with attribution, instead of paraphrasing a competitor.

Think of FAQPage schema as future-proofing. You are not chasing a snippet that mostly disappeared, you are making your knowledge legible to every machine that reads the web, today and as AI search keeps growing. Combined with a clear content structure, it helps your help center get picked up rather than skipped. If you are still deciding how to organize that content, our comparison of FAQ vs knowledge base is a good next read.

Common mistakes

• Marking up content that is not visible on the page. If a human visitor cannot see the question and answer, do not put it in the schema. This is the single most common reason for manual penalties on structured data.
• Using FAQPage for non-FAQ content. Product descriptions, marketing copy disguised as questions, or a single Q&A used to spam keywords do not qualify. Reserve it for real frequently asked questions.
• Confusing FAQPage with QAPage. FAQPage is for your own questions with one definitive answer each. QAPage is for community pages where users post multiple competing answers. Mixing them sends the wrong signal.
• Duplicating the same FAQs across many pages. Repeating identical question and answer blocks site-wide looks manipulative. Keep each FAQ set relevant to the specific page it sits on.
• Letting the answer text drift from the page. If you edit the visible answer but forget the JSON-LD, the two fall out of sync and validation can fail. Keep them in lockstep.
• Expecting the blue rich result anyway. After 2023, most sites will not see it. Add the schema for understanding and AI pickup, not for a snippet that is no longer offered to you.

Frequently asked questions

Will adding FAQPage schema get me the FAQ rich result in Google? Almost certainly not, unless you run a well-known government or health site. Since August 2023 Google reserves that visible result for those authoritative sources. For everyone else the markup still helps machines understand your content, but the blue accordion will not appear.

Is FAQPage schema still worth adding in 2026? Yes. It future-proofs your markup and makes your answers easier for Google and AI assistants like ChatGPT and Perplexity to read and quote accurately. The value moved from a visible snippet to machine understanding, and that understanding matters more every year.

What is the difference between FAQPage and QAPage schema? FAQPage is for a list of questions you wrote with one official answer each, like a help page. QAPage is for community pages where visitors submit and vote on multiple answers, like a forum thread. Use the one that matches how the page actually works.

Do I have to write the JSON-LD myself? No. You can hand-code it, but modern help-center platforms generate valid FAQPage and Article schema for you automatically. Helpable adds both without any manual coding, so your markup stays correct as you edit content.

How do I check that my schema is valid? Run the page through Google's Rich Results Test and the Schema Markup Validator. They flag missing fields, type errors, and mismatches between your markup and visible content. Fix every error and review the warnings before you publish.

Next step

FAQPage schema is no longer a shortcut to a flashy snippet, but it is a quiet, durable signal that helps both Google and AI assistants understand and quote your answers. The easiest way to get it right is to let your help center handle it.

Helpable is EU-built, with AI included on every plan and hosting in Frankfurt and Amsterdam. It generates a sitemap, hreflang, and schema markup, including FAQPage and Article schema, automatically, so your structured data stays valid while you focus on writing. You get a custom domain on every plan, support for 50+ languages, and a setup that takes around 30 minutes. Pricing is flat: Starter $49, Pro $149, and Scale $249 per month.

Try Helpable free for 7 days and let Helpable add FAQ and Article schema automatically.

Sources: Google Search Central, verified May 2026. Last updated: June 2026.

See also: knowledge base software and help center software.