FAQPage Schema: Still Worth It?

#01What happened to FAQ rich results?

For most sites, FAQ rich results had already disappeared in 2023. The 2026 change ended them for the remaining government and health sites too.

#02Is FAQPage markup now invalid?

No. FAQPage remains a schema.org type (schema.org). Google's change is about a search feature, not the vocabulary. Validators will still parse it.

#03Does FAQPage markup help in Google's AI features?

Google says you don't need special markup to appear in AI Overviews or AI Mode (Google), and its AI optimization guide focuses on helpful content and the basics (Google). We found no Google statement that FAQPage markup affects AI features. Our view: assume it doesn't.

#04Do other AI engines use it?

We found no public statement from OpenAI, Anthropic or Perplexity that FAQPage markup affects their answers, as of 30 Oct 2026. Their crawler documentation focuses on access controls (OpenAI, Anthropic, Perplexity). Our view: structured data is machine-readable, so some systems may read it, but there's no evidence it gives an advantage. Treat claims that "FAQ schema gets you into ChatGPT" with caution unless they come with a method and dates.

#05Why is FAQ content still worth writing?

Our view:

• It matches how people ask. AI prompts are often full questions, and a heading that mirrors the question plus a direct answer is easy to extract.
• It handles objections. Pricing, limits, integrations and comparisons are where AI answers often go wrong; answering them on your own page gives engines a clear source.
• It's useful to readers. Google's people-first guidance asks whether content answers the reader's needs (Google).

The important part is the visible text. A hidden accordion of thin answers written for markup adds little.

#06How should you write FAQ sections now?

1. Use real questions from sales calls, support tickets and search queries.
2. Put the answer in the first sentence, then add detail.
3. Keep answers specific: numbers, limits, dates and links to the full page.
4. Avoid duplicating the same FAQ across dozens of pages.
5. Review answers when prices or features change.

Google's general structured data rules still apply if you keep the markup: it must match visible content and mustn't be misleading (Google).

#07What should you do with existing markup?

#08What about QAPage?

QAPage is a different type for pages where users submit answers to a single question, such as forums. It's not a replacement for FAQPage on company pages. Google still documents QAPage markup for those pages, so check its current documentation before using any type, since features change.

#09Did dropping FAQ rich results change clicks?

We don't have verified data on traffic effects, and we haven't seen primary-source studies. Our view: because most sites lost FAQ rich results in 2023, the 2026 change mainly affected government and health sites. If you saw a change, compare Search Console data before and after 7 May 2026.

#10How do you audit FAQ content across a site?

Our view: export every page with an FAQ section and list its questions. Look for three problems. First, duplicated questions with different answers on different pages, which give engines conflicting facts. Second, answers with outdated prices, limits or product names. Third, generic questions nobody asks, added only to fill a template. Merge duplicates into one canonical answer and link to it, update stale facts at the source, and delete filler. Then test a handful of real prompts in the assistants your buyers use and note which pages, if any, are cited, with the date.

#11Checklist

• Don't add FAQPage expecting Google rich results
• Keep visible, specific Q&A content
• Remove markup for content that isn't visible
• Review FAQ answers when facts change
• Audit plugins that add FAQ markup automatically

#12From MentionX data: how often brands appear by prompt typeOriginal data

Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

FAQ sections often answer brand-specific and comparison questions. In the MentionX sample, those prompts mention brands far more often than others:

Engines also differ in how often they cite pages:

Our view: FAQ sections that answer real brand-specific questions, such as pricing, integrations and limits, can provide the direct answers engines need for these prompts, with or without markup.

Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

#13Worked example: Ledgerline reviews its FAQ markup

Ledgerline is a fictional accounts-payable tool. Figures are illustrative.

Ledgerline added FAQPage markup to 30 pages when FAQ rich results were widely shown. After Google's change, the SEO lead asks whether to keep it.

The team checks each page. On 22, the FAQ answers real questions and the markup matches the visible text, so it stays. On five, the FAQ repeats marketing copy, so the team rewrites the questions using support tickets and updates the markup. On three, the questions are hidden in a collapsed widget that doesn't render in the HTML, so the team fixes the template.

It adds new FAQ sections to the pricing and integration pages, based on what prospects ask sales.

#14How many questions should an FAQ section have?

Our view: three to eight is usually enough. Each question should be one a real customer asks, with an answer that's short and complete. Avoid padding the section with questions nobody asks just to add markup.

#15Where should FAQ sections go?

Put FAQs near the end of a page, after the main content, or on pages where questions naturally arise, such as pricing and product pages. Avoid a single FAQ page that tries to cover everything, because answers are easier to find on the page they relate to.

#16How should answers be written?

Start with a direct answer, such as yes, no or a figure, then add the detail. Keep answers to a few sentences. Link to a fuller explanation where needed. Make sure each answer matches the rest of the page and your other pages.

#17How do you keep FAQs current?

Review FAQ answers when pricing, features or policies change. Add questions that come up repeatedly in support and sales. Remove questions that no longer apply.

#18How do you choose which questions to answer?

Use support tickets, sales call notes, search queries and prompts customers ask assistants. Pick questions that are common and that your page can answer well. Avoid questions that are really marketing statements in question form, such as "Why is our product the best?" Our view: the most useful FAQ questions are the ones customers ask before they buy.

#19How should FAQ markup match the page?

Each question and answer in the markup must appear in the visible text. Don't mark up content that's hidden from users or that differs from what they see. Use one FAQPage per page. Keep answers in the markup in sync with the visible answers when they change.

#20How do FAQs relate to the main content?

FAQs should add follow-up answers, not repeat the main content. If a question needs a long answer, cover it in the main content and link to it. Make sure FAQ answers don't contradict the rest of the page.

#21How do you measure FAQ impact?

Track whether engines cite pages with FAQ sections for the questions they answer. Check support tickets for the same questions, and see whether they fall after the FAQ is published.

#22What's the difference between FAQPage and QAPage?

FAQPage is for pages where the site provides both the questions and the answers. QAPage is for pages where users ask a question and other users submit answers, such as community forums. Use the type that matches how the content is created. Our view: most business sites only need FAQPage.

#23How do you write questions customers recognise?

Use the customer's words, not internal terms. Start questions with how, what, can or does. Keep them short and specific, such as "Can I cancel at any time?" rather than "Cancellation policy information".

#24How do you handle sensitive questions?

Answer questions about pricing, contracts and data honestly and clearly. If the answer depends on the situation, say what it depends on and link to the full policy.

#25How do you audit an FAQ page by page?

For each page with an FAQ, check that the questions are real, the answers are accurate and current, the markup matches the visible text and the content renders without JavaScript. Mark each page as keep, rewrite or remove. Our view: most of the value comes from rewriting weak answers, not from the markup itself. Record the decision for each page and the date, so the next audit can start from where this one ended.

#26Common questions

Should we remove FAQPage markup? Our view: not if it's accurate. It does no harm and keeps the content clearly structured.

Do AI engines read FAQPage markup? There's no published evidence that most do. Visible, well-written answers matter more.

Can FAQs be hidden in accordions? Yes, if the text is in the HTML. Check that it renders without JavaScript.

#27Related

• HowTo schema after Google's changes
• Schema markup for AI search