FAQ Sections That AI Actually Quotes (2026 Guide)

If ScoutRival’s Site Audit flagged “Question-form headings & FAQ blocks,” it means your pages aren’t phrased the way real buyers ask AI — so the query-to-heading match that gets you quoted isn’t happening. This guide shows you how to build FAQ content AI actually lifts, and explains what changed in 2026 so you don’t waste effort chasing a SERP feature that no longer exists.

The big 2026 change: FAQ rich results are gone

For years, the pitch for FAQ schema was the star-studded dropdown under your search listing — those expandable questions that made your result taller. That’s over. On 7 May 2026, Google stopped showing FAQ rich results in Search, completing a wind-down that started back in 2023 when it restricted them to government and health sites. The Search Console FAQ report and the Rich Results Test lost FAQ support shortly after.

Here’s the part that matters: the FAQPage schema type itself is not “broken.” It’s still valid Schema.org markup, Google still parses it, and leaving it on your pages causes no harm. What died is the visible SERP decoration. So if you added FAQ schema purely to get the dropdown, that reason is gone.

But there’s a much better reason to write FAQs in 2026, and it has nothing to do with Google’s blue links: AI engines love FAQ content. A question-and-answer block is one of the most-extracted units in ChatGPT, Perplexity and Google AI answers, because its shape already matches how people ask and how models answer. The lesson isn’t “stop writing FAQs” — it’s “write FAQs for the visible text and the AI quote, not for a rich result that no longer appears.”

Why question-form content matters for AI visibility

People don’t type keywords into ChatGPT. They ask full questions: “how long does a roof replacement take?”, “is laser hair removal safe for dark skin?”, “do you offer same-day dental crowns?” When your page uses that exact question as a visible heading, you create a clean match between the prompt and your content — and the answer directly beneath it is a self-contained unit the engine can quote without hunting.

This is a MEDIUM-evidence lever: it’s universally advised and mechanically sound, but it isn’t backed by a controlled study, so we won’t dress it up with a fake percentage. What we can say plainly is that FAQ blocks are consistently among the formats AI engines pull from, and that a question-shaped heading with a tight answer beneath it is exactly the “chunk” retrieval systems are built to grab.

One more reason it works: FAQs naturally cover the sub-questions buyers ask around a service — cost, timing, safety, process. That overlaps with how Google AI Mode decomposes a single prompt into many sub-queries (“query fan-out”) and assembles the answer from multiple sources. Good FAQ coverage puts you in more of those sub-answers. (For the bigger version of that idea, see our guide on topic clusters and query fan-out.)

How to build FAQ content AI quotes

1. Collect the real questions people ask

Don’t invent questions from thin air — mine the ones buyers actually ask:

• Your live-chat and email logs
• Your Google Business Profile Q&A section
• Google’s “People Also Ask” boxes for your service
• The questions your sales or front-desk staff hear every day
• Reddit and forum threads in your niche

Aim for 5–10 genuine questions per service page.

2. Turn generic headings into questions

Rename vague section headings into the literal question they answer:

• “Our Process” → “How long does a roof replacement take?”
• “Pricing” → “How much does Botox cost in Austin?”
• “Aftercare” → “What can I eat after a tooth extraction?“

3. Answer in 40–80 words, and repeat the subject

Under each question, write a direct answer of 40–80 words that answers in the first sentence and repeats the subject noun so the paragraph stands alone when quoted. Compare:

• Weak (pronoun-dependent): “It usually takes two to three days.”
• Strong (self-contained): “A standard asphalt-shingle roof replacement usually takes two to three days for an average home, depending on size, weather and tear-off complexity.”

The second one can be lifted straight into an AI answer and still make sense.

4. Keep the answer visible and in your raw HTML

Collapsed accordions are fine only if the answer text is still present in the page source (AI crawlers don’t click). If your FAQ widget injects answers with JavaScript after load, the engine may never see them — check with View Source (see our raw-HTML guide).

Platform-by-platform setup

WordPress — Rank Math or Yoast FAQ block

The tidiest route on WordPress is a dedicated FAQ block. It renders visible Q&A and adds the FAQPage JSON-LD (harmless to keep, even post-deprecation).

Rank Math:

1. Go to Rank Math → Dashboard and confirm the Schema module is enabled.
2. Edit your page, click + to add a block, and choose “FAQ by Rank Math.”
3. Add each question and its 40–80-word answer. The block outputs visible text plus schema automatically.

Yoast:

1. Edit your page and add the Yoast FAQ block (part of Yoast’s structured-data blocks).
2. Fill in each question/answer pair. Yoast handles the visible rendering and the markup.

Either way, remember: the visible text is what earns the AI quote now — the schema is just a small, optional bonus.

Wix

1. Wix has a native FAQ element — add it from Add Elements → List → FAQ, or simply use heading + text blocks.
2. Write each question as a heading and the answer beneath it. Wix renders this server-side, so it lands in your HTML.

Squarespace

1. Use an Accordion block (questions as titles, answers as content) or plain heading + text blocks.
2. Confirm answers appear in View Source — Squarespace’s accordion content is generally present in the HTML.

Webflow

1. Build questions as headings (H2/H3) with paragraphs beneath, or use an accordion component.
2. If you use an interactions-based accordion, make sure the answer text exists in the DOM at publish, not only after a click.

Shopify

1. Add an FAQ section via your theme (many themes include one) or an FAQ app, or write question headings and answers directly in the page’s rich-text editor.
2. Prefer solutions that output real HTML text over ones that fetch answers via JavaScript.

Any other site

Plain semantic HTML is all you need: an H2 or H3 phrased as the question, followed by a <p> answer. Optionally wrap it in FAQPage JSON-LD — but the visible text does the heavy lifting.

How to confirm it’s fixed

1. View Source (Ctrl-U) and search for one of your questions. It should appear as real on-page text (a heading), not something injected by JavaScript.
2. Read one answer in isolation — does it make sense without the question above it? If it leans on “it” or “they,” rewrite it to name the subject.
3. Re-run your ScoutRival Site Audit — the “Question-form headings & FAQ blocks” item should go green.
4. Ask ChatGPT or Google AI Mode your exact question plus your city or brand, and see whether your answer’s wording is echoed. (It varies run to run — one echo is a good sign, not a guarantee.)

Common mistakes to avoid

• Adding FAQ schema to chase the rich result. That dropdown is gone as of May 2026. Don’t add schema for the snippet — add visible Q&A for the AI quote.
• Removing all your FAQ schema in a panic. You don’t need to. FAQPage is still valid markup and causes no harm; just don’t expect a SERP feature from it.
• Invented, keyword-stuffed questions. “What is the best premier trusted roofer near me?” isn’t how anyone talks. Use the real questions from chat logs and People Also Ask.
• Pronoun-only answers. “It takes two days” can’t be quoted cleanly. Repeat the subject so the answer stands alone.
• Answers hidden behind JavaScript. If the text only loads after a click and isn’t in the source, AI can’t read it. Keep it in the raw HTML.
• Marketing fluff instead of answers. An FAQ that says “We pride ourselves on excellent service!” answers nothing. Give the actual number, timeframe, or yes/no — pair it with specific facts and figures.

The bottom line

FAQ rich results are history, but FAQ content has never mattered more for AI. Write your headings as the exact questions buyers ask, answer each in a tight 40–80 words that repeats the subject, and keep the text visible in your HTML. The schema is an optional footnote now; the visible Q&A is what gets quoted.

Want to know which questions your pages are missing? Run a free Site Audit with ScoutRival. It shows the sub-questions buyers ask AI that your site doesn’t answer yet — and BlogCraft can draft the FAQ section for you to review before you publish.