FAQ Schema in 2026: What It Is, What Google Changed and How to Use It

FAQ schema was for years one of the easiest SEO wins: a few lines of code, and your questions appeared as expandable answers under your result. That era is over. Google's Search Central documentation updates record the deprecation of the FAQ rich result in May 2026 and the removal of its documentation in June 2026. This guide explains what the markup is, what changed, when it is still worth adding, and how to write FAQs that get cited.

What is FAQ schema?

FAQ schema is a block of schema markup that describes a list of questions and their answers in a machine-readable format. It relies on three types from the shared schema.org vocabulary, created by Google, Microsoft, Yahoo and Yandex:

• FAQPage: the page type, a web page that presents one or more frequently asked questions.
• Question: each question, with its text in the name property.
• Answer: the answer, attached to the question through acceptedAnswer, with its content in the text property.

The questions are listed in the mainEntity property of the page. Google recommends JSON-LD for structured data whenever the site allows it, because the code sits in one block, separate from the visible HTML.

FAQPage or QAPage?

The two types are often confused. The difference depends on who writes the answers.

What happened to FAQ rich results in Google?

FAQ rich results showed questions as dropdowns directly in the search results, which made a result taller and pushed competitors down. Their decline happened in two steps.

In its August 2023 announcement, Google stated that there is no need to remove the markup proactively: "Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search." The same logic applies after the 2026 retirement. Google also specified that the change was not a ranking change: losing the rich result can lower click-through rate, but not the position itself.

Is FAQ schema still worth adding in 2026?

Yes, when the page already has a real FAQ, because the cost is close to zero. No, if you expect a visual result or a ranking boost. Here is what the markup still does, and what it does not do.

What it still brings

• Explicit meaning: Google's introduction to structured data states that it uses structured data found on the web to understand the content of a page. Marking which text is a question and which is its answer removes ambiguity.
• A shared vocabulary: schema.org is read by other search engines and by any crawler that parses JSON-LD, not only by Google.
• Writing discipline: maintaining the markup forces you to keep short, self-contained answers, the format that wins featured snippets and "People also ask" boxes.

What it does not do

• It no longer produces rich snippets in Google.
• It does not improve rankings on its own.
• It is not required to appear in AI answers. Google's page on AI features and your website states that no special markup is needed to appear in AI Overviews or AI Mode: the page must be indexed and eligible for a snippet.

Claims that FAQ schema multiplies AI citations circulate widely, but no public study from Google, OpenAI or another primary source confirms them. What AI assistants quote is the visible text: a clear question followed by a direct answer. Our guide to structured data for AI search sorts the markup that helps from the markup that does not.

Which pages deserve an FAQ section?

An FAQ earns its place when visitors have recurring questions that the main content does not answer. It is a poor fit for pages whose content is already a single answer.

How do you add FAQ schema to a page?

1. Write a visible FAQ first

Pick 3 to 8 questions your visitors actually ask: support tickets, sales calls, the "People also ask" box, related searches (see our guide to People Also Search For). Answer each one in 2 to 4 sentences, starting with the answer itself.

2. Generate the JSON-LD

The structure is always the same. A minimal example with one question:

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "How long does delivery take?", "acceptedAnswer": {"@type": "Answer", "text": "Orders ship within 24 hours and arrive in 2 to 4 business days."}}]}

Each additional question is a new Question object in the mainEntity list. The block goes inside a script tag of type application/ld+json, in the head or the body of the page. To avoid syntax errors, a free FAQ schema generator builds the code from your questions, and a general schema generator covers the other types (Article, Product, Organization).

3. Add it through your CMS

On WordPress, SEO plugins such as Yoast offer an FAQ block that outputs the markup automatically; the same logic applies to the WordPress optimization options we document. On Shopify, Webflow or Wix, paste the JSON-LD into a custom code field of the template or page.

4. Validate

Since June 2026, Google's Rich Results Test no longer checks FAQ markup. Use the Schema Markup Validator from schema.org or our structured data validator to catch syntax errors, missing properties and mismatches with the visible text.

What are the most common FAQ schema mistakes?

1. Marking up invisible content. Google asks not to add structured data about information that is not visible to the user. Every question in the JSON-LD must appear on the page.
2. Different text in the code and on the page. The answer in the markup should match the visible answer.
3. Using FAQPage for user content. Forums and community answers belong to QAPage.
4. Copying the same FAQ on hundreds of pages. A delivery FAQ repeated on every product page adds no information.
5. Turning answers into ads. An answer that only says "Contact us" or pushes an offer answers nothing.
6. Invalid JSON. A missing comma or an unescaped quote silently breaks the whole block.
7. Keeping obsolete answers. Prices, delays and policies change: an outdated answer misleads readers and AI assistants alike.

How do FAQs help with SEO and GEO in 2026?

The rich result is gone, but the FAQ format remains one of the most useful blocks on a page, for search engines and for generative engine optimization (GEO). A good FAQ captures long-tail questions that the main text does not cover, matches the way people phrase prompts in ChatGPT or Gemini, and gives AI assistants short, self-contained passages they can quote with a link. Sorank's study of the sources Gemini cites and our explanation of how search engines work point the same way: the page must first be crawled, indexed and ranked, then a clear answer gets picked.

To check whether your markup is readable by language models, run a structured data audit for LLMs. To see whether your FAQs lead to citations, track your brand mentions in AI answers on the questions your customers ask.

FAQ schema: what to keep

FAQ schema no longer earns a visual result in Google, but a visible, well-answered FAQ still earns clicks, snippets and AI citations. Keep the markup where you have a real FAQ, remove nothing in a hurry, and invest your time in the answers themselves. If you want articles that already include sourced, question-based sections, Sorank's article generator writes and publishes them on autopilot; see how Sorank works.