How to Write an FAQ That AI Cites and Google Understands

An FAQ that AI cites answers real customer questions one at a time, with a direct answer of 40 to 80 words, in text that is visible on the page and free of advertising. FAQPage schema is no longer needed for Google: the FAQ rich result stopped appearing on May 7, 2026. What still counts is the content, and it serves people as well as AI search.

Quick summary

• Write the question the way the customer says it and answer in the first sentence, in 40 to 80 words.
• Take questions from real sources: Search Console, support, sales and comments, not from your imagination.
• Google ended the FAQ rich result on May 7, 2026. FAQPage schema still exists in schema.org, but it is no longer a goal.
• For Google, there is no special markup for appearing in AI answers. Clear, accessible content is what counts.
• The more specific the answer (price, deadline, condition, exception), the more likely it is to be useful and citable.
• An AI citation is never guaranteed. Measure with periodic tests.

How to read this: if you are just starting, read "What is a citable FAQ?", the step-by-step list and the example. If you already work in SEO, go to the schema section, the data on questions and AI Overviews and the query filter in Search Console.

What is an FAQ that AI can cite?

It is a block of questions and answers in which each answer stands on its own: whoever reads just that passage understands what was asked, gets the information and knows when it applies. This holds for a person in a hurry and for a system that extracts passages to build an answer, as we explain in LLM-citable content structure.

In plain English: think of a counter clerk. When someone asks "do you pick up dogs from home?", a good clerk says "yes, within 3 miles, for $12." They don't say "we have the best service in town." AI looks for the first kind of answer, because it is the one it can pass along without making anything up.

Four traits define a citable FAQ:

• A real question, in the customer's vocabulary ("how much does it cost," "how long does it take," "can I cancel").
• The answer in the first sentence, followed by the detail and the exception.
• Specific information: a number, a deadline, a condition, a review date.
• Visible text, written in HTML on the page, not only in an image or inside an app that needs a click to load.

Is FAQPage schema still worth it?

For Google, it is no longer a goal. The history is short. In September 2023, Google updated its documentation to say the feature only appeared for well-known government and health sites. On May 8, 2026, it added a deprecation notice saying the feature would stop appearing in Search from May 7, 2026. On June 15, 2026, it removed the documentation, since the feature is no longer displayed. All of this is in the Google Search documentation update history.

That does not mean the markup is "dead." Schema.org still defines the FAQPage type as a page that presents one or more frequently asked questions. What changed was the visual benefit on Google. And on AI, Google's guide for generative features is clear: structured data is not required for generative AI search and there is no special schema to add.

In plain English: schema is a label stuck on a shelf to help a system read what is on it. Google stopped using that FAQ label to dress up search results. The shelf, meaning the questions and answers written on the page, is still what people read and what AI makes use of.

So what is the practical decision?

• If you already have FAQPage on your site: you don't need to remove it just for this. But confirm that it reflects exactly the visible questions and answers.
• If you are creating one now: prioritize the visible text. Schema is optional and should not be the reason the FAQ exists.
• If a plugin generates FAQs in bulk: be suspicious. Generic questions on every page make the content repetitive.

For SEO professionals: update reports and targets that depended on the FAQ rich result. On pages that showed the dropdown, CTR may have shifted from May 7, 2026; compare by period and by query before attributing everything to AI. For the overall picture of markup, see schema markup for AI Search.

Why does an FAQ matter in AI answers?

Because queries phrased as questions are exactly the ones where AI appears most. According to the Seer Interactive study from April 2026, which tracked 53 brands and 5.47 million queries between January 2025 and February 2026, informational queries in question format showed an AI Overview 85.9% of the time (1,214 of 1,413 queries). For comparison queries, the rate was 95.4%.

The same study carries a limit: on informational queries, brands cited in the AI Overview received about 120% more organic clicks per impression than those not cited, but still came in about 38% below queries with no AI Overview. It is an agency study of 53 brands, and should be read as a direction, not as a rule for the whole market. The practical side: if your content answers questions, it competes exactly where AI answers. The best FAQ is one that carries information only your company has, such as a real deadline, a policy, a price, a step in how to use something. That is the "non-commodity" content Google itself asks for in its guide.

See also how this contest changes strategy in Google AI Overviews and in AEO: answer engine optimization.

How do you find the right questions?

Look where customers already ask, in order of quality: support, sales, Search Console and, last, tools and guesses. Real questions prevent the generic FAQ.

Source	What to extract	Caution
Support (chat, email, messaging apps)	Recurring doubts, in the customer's words	Anonymize personal data
Sales team	Objections before purchase: price, deadline, guarantee	Answer without pressuring the purchase
Search Console	Question-style queries that already generate impressions	New sites may have few impressions
Google's "People also ask"	Variations of the topic	Google chooses what to display; you cannot request it
Comments, reviews, social media	Spontaneous language and doubts	Use as a clue, not as fact
Testing in AI assistants	Sub-questions the AI generates (fan-out)	Use to complete, not to copy

The "People also ask" feature is described in Google's featured snippets documentation as a group of related questions. The same page explains that there is no way to mark a page to be a featured snippet: Google's systems decide whether it is a good fit.

For SEO professionals: in the Search Console performance report, you can filter queries by regular expression with the "Custom (regex)" filter. To list question-style queries, try something like ^(how|what|which|who|when|where|why|can|should|is|does|do|are)\b in Queries and sort by impressions. Then cross-reference with the page receiving the impression and the average position. Details on reading the report are in Google Search Console for beginners.

How do you write a good FAQ answer?

Start with the answer, then add the condition and, if there is one, the exception. Keep it between 40 and 80 words, without repeating the question and without inviting the reader to "get in touch" instead of answering. The answer can include a link to go deeper.

Hypothetical example: the fictional pet shop "Happy Paws" gets the question "Do you pick up dogs from home?" Compare.

Weak answer	Strong answer
"Get in touch to learn more about our pickup and delivery service. We have the best conditions on the market and service designed for you and your pet."	"Yes. Happy Paws picks up and drops off your pet at home within 3 miles of the store, Monday through Saturday, for $12 each way. Beyond that radius, the fee is calculated per mile and quoted before you book. You need to book 24 hours ahead, by text message or on the website. Pets under veterinary treatment follow their own rules."

The strong answer is about 60 words, opens with "Yes," gives a number, a deadline, a channel and an exception, and does not depend on the page's context. The values above are made up for the example.

Rules that help in any industry:

• One question, one answer. Don't combine two doubts.
• No "as mentioned above." Each answer has to work in isolation.
• Terms defined within the answer itself. Whoever reads only that passage needs to understand it.
• A review date when the subject changes (prices, rules, deadlines).
• In health, finance and law, the answer must be reviewed by a qualified professional, with a source. Do not invent numbers.

Where and how do you publish the FAQ?

Publish questions on the page of the subject they belong to, with each question in a heading (H2 or H3) and the answer right below it, in open text. Avoid one giant page of "general questions" and avoid copying the same FAQ onto every page.

• 4 to 8 questions per page is usually enough. More than that is generally a sign that the content should become its own page.
• Different questions on different pages, according to the search intent of each one (types of intent).
• Text in the HTML, not only in an image, PDF or carousel.
• No page per question variation. Google's guide warns that creating separate content for every possible variation, especially to manipulate AI answers, violates the scaled content spam policy.

The same guide also says you don't need to rewrite your text "just for AI," nor break it into tiny blocks. Write for the reader and organize clearly.

Step by step to create your FAQ

Follow this sequence for the page of a service or product.

1. Gather 20 real questions from support, sales and Search Console.
2. Group by intent: price, deadline, use, comparison, problems, guarantee.
3. Choose 4 to 8 for the page, the ones that weigh most on the decision.
4. Write each answer with the conclusion in the first sentence, in 40 to 80 words.
5. Add the specific detail (number, deadline, condition) and the review date when needed.
6. Ask for a review from someone who knows the subject, especially on sensitive topics.
7. Publish as visible text, with each question as a heading. FAQPage schema is optional.
8. Test and revise every quarter: ask AI assistants, as in "prompts to test your brand," see whether your page appears and update what changed. Contentor's AI Visibility does this on the questions you choose, in ChatGPT only. Use the GEO, AEO and SEO checklist to check the rest of the page.

Frequently asked questions

Does Google still show FAQs in results?

No. Google said the FAQ rich result stopped appearing from May 7, 2026 and removed the documentation in June 2026. Before that, since 2023, it only appeared for well-known government and health sites. The FAQ itself is still useful as content for people and for systems that extract answers.

Do I need FAQPage schema for AI to cite me?

No. Google says there is no special schema and no structured data requirement for generative AI search. FAQPage remains valid in schema.org, but what makes an answer useful and citable is visible, specific, direct text. Use the schema only if you have your own reason, and make sure it mirrors the page's content.

What is the ideal answer length in an FAQ?

Between 40 and 80 words usually balances completeness and brevity: there is room to answer, give the condition and mention an exception. Very short answers leave doubts, and long ones hide the conclusion. This is not a Google rule, it is a practice. If the subject needs more, answer in brief and link to an article with the detail.

How many questions should I put in an FAQ?

4 to 8 per page is usually a good number, chosen from those that most influence the decision. Lists of 30 questions dilute the focus and turn into repetitive text. If a question calls for a long explanation, it deserves its own article, linked to the FAQ by an internal link.

Can I generate the FAQ with AI?

You can use AI to draft and to suggest questions, but the answers must come from real information about your company and go through human review. Generic answers generated in bulk are commodity content, which Google itself says is not what helps most. Check numbers, deadlines and policies before publishing.

Next step

Pick a page that already generates conversations, such as a main service, and write 4 to 8 questions on it with answers of 40 to 80 words. Then deepen the structure with LLM-citable content structure and, if your business serves a city, see GEO for local businesses. If you are short on time to produce the pages, generate articles with AI on Contentor with question-style headings and direct answers, and review before publishing.

Read also:

• Google AI Overviews: how to optimize to get cited
• AEO: answer engine optimization
• SEO, AEO and GEO glossary