FAQ and Q&A Formatting for AI Answers: A How-To

FAQ formatting for AI answers means writing each question the way buyers ask it, as a real heading, with a direct answer in the visible text right below it. That gives readers a fast path to the answer and gives AI tools a clean, self-contained passage to lift. This how-to is part of our AI search optimization guide. You'll need a list of real customer questions and access to your page templates.

Why FAQ sections still matter for AI search

The search feature that made FAQs popular is gone. Google stopped showing FAQ rich results from May 7, 2026, and removed the documentation in June 2026. FAQ markup now earns no special result in Google Search.

The questions themselves still matter, because people ask AI tools questions. Pew Research found in March 2025 that 60% of Google searches that began with a question word produced an AI summary. That data is U.S.-only, covers Google only and predates later changes. Google also says its AI features may run several related searches, a "query fan-out", to answer one question. A clearly answered follow-up question on your page gives those searches something to find.

FAQ section, FAQ page or Q&A page?

Three formats look similar but serve different jobs. Pick the one that matches who writes the answers.

For most businesses, the right choice is a short FAQ section at the end of each service page or guide. A separate FAQ page works for questions that don't belong to one service, such as payment or booking. Google's guidelines say QAPage markup is only for pages where users can submit answers, and list "an FAQ page written by the site itself" as an invalid use.

Steps to format FAQs for AI answers

1. 01
   Collect the questions people really ask.

   Go through sales call notes, support emails, reviews and chat logs. Add the question-style queries from Search Console. Group them by page: each question belongs on the page whose topic it's about. Drop any question you're adding only because it contains a keyword. Write what buyers ask, not what you wish they asked.

2. 02
   Write each question the way a buyer would.

   Use the customer's words, in full sentences: "How long does a website redesign take?", not "Timeline". Keep one question per heading. Avoid internal jargon and product codes a buyer wouldn't type. Short, plain questions are easier to scan and match the way people phrase questions to AI tools.

3. 03
   Answer in the first sentence, then add detail.

   Start with "Yes", "No", a number or a direct statement. Then give the reason and any exceptions in two or three short sentences. Our own rule of thumb is 40 to 80 words per answer; Google publishes no ideal length. If an answer needs a list, a table or several paragraphs, move it into the main body of the page instead.

4. 04
   Make every answer stand on its own.

   Each answer may be shown or quoted without the rest of the page. Don't write "as mentioned above" or "see the previous question". Name the service, product or policy you mean. Keep conditions in the same sentence as the fact they limit. The writing habits in how to write content LLMs can quote apply to every answer.

5. 05
   Use real headings for the questions.

   Put the section under an H2 such as "Frequently asked questions", and make each question an H3. Don't fake headings with bold text or images. Real headings let screen reader users jump from question to question, which supports WCAG 2.2 success criteria 1.3.1 and 2.4.6. Google's guide also says semantic HTML helps screen readers parse your page. Good practice, not a guarantee of legal compliance.

6. 06
   Keep every answer in the page HTML.

   An accordion is fine. Google's spam policies say content that toggles between hiding and showing doesn't break its rules. What matters is that the answer text is in the HTML when the page loads, not fetched only after a click. Google processes JavaScript when it isn't blocked, but other crawlers don't document whether they do. Check the raw HTML:

   bash

   curl -s https://example.com/services/trees | grep -c "grind stumps"

7. 07
   Add FAQPage markup only if it matches exactly.

   Markup is optional and no longer earns a Google rich result. If you keep it, generate it from the same source as the visible FAQ, so the two can't drift. Never mark up questions readers can't see. A minimal example:

   json

   {
     "@context": "https://schema.org",
     "@type": "FAQPage",
     "mainEntity": [{
       "@type": "Question",
       "name": "Do you remove tree stumps?",
       "acceptedAnswer": {
         "@type": "Answer",
         "text": "Yes. We grind stumps below ground level."
       }
     }]
   }

8. 08
   Give each question one home on your site.

   Answer each question fully on one page only. Elsewhere, link to that answer instead of rewriting it. Google's AI guide suggests reducing duplicate content, and two slightly different answers can leave readers and AI tools unsure which is right. Review your FAQs whenever a price, policy or process changes.

A weak FAQ entry, rewritten

Here is one entry from a hypothetical tree service's page, before and after the steps above.

Before. Question: "Stumps?" Answer: "We offer a full range of tree services. Contact us to learn more!"

After. Question: "Do you remove tree stumps?" Answer: "Yes. We grind stumps below ground level, either as part of a tree removal or as a separate job. Grinding leaves wood chips, which we can haul away or leave on site as mulch."

The second version uses the buyer's words, answers in the first word and still makes sense if an AI tool quotes it alone. It also answers the likely follow-up, what happens to the chips, without a second question.

FAQs work best alongside clear service pages. For questions with a local angle, such as service areas and opening hours, see AI search for local businesses. If you'd rather have your FAQs written, built and checked for you, our in-house SEO team handles it end to end, including reporting on where clients are mentioned in Google AI Overviews and ChatGPT.

Troubleshooting

Your FAQ answers are missing from the crawled HTML

Cause: the FAQ widget loads answers from the server only when someone opens a question, or a script builds the whole section after the page loads. The answers look fine in a browser, but the HTML a crawler receives contains only the questions, or nothing at all.

Fix: fetch the page with curl and search for a phrase from one answer. Then run URL Inspection in Search Console and check the crawled HTML. If the answer text is missing, change the component so every answer is in the initial HTML and the accordion only shows or hides it. A native details and summary element does this without extra scripts. Retest after the change is live.

The Rich Results Test shows no FAQ result

Cause: this is expected. Google stopped showing FAQ rich results from May 7, 2026, so the test won't report an FAQ rich result, even for valid markup. Old tutorials and plugins may still describe FAQ markup as a way to win extra space in search results.

Fix: don't try to fix it. Decide whether to keep the markup at all. If you keep it, use the Schema Markup Validator to check the syntax and confirm it matches the visible FAQ word for word. Judge your FAQ by whether it answers real questions, not by a search feature. Then remove any plugin settings that add FAQ markup to pages with no visible FAQ.

Two pages answer the same question differently

Cause: FAQs are often copied between pages and then edited separately. Over time, a price, timeline or policy changes on one page but not the other. AI tools may then quote either version, and readers lose trust when they spot the conflict.

Fix: list every FAQ question across the site in one spreadsheet, with the page it appears on. Where a question repeats, pick one page to hold the full answer. Update that answer, then replace the copies with a short line and a link to it. Add a review step for FAQ content to your process for price or policy changes, so it can't drift again.