Quick answer
FAQ sections still help when they answer real buyer questions concisely on relevant pages. Since August 2023, Google shows FAQ rich results mainly for well-known government and health websites, so most businesses should not expect expandable FAQ snippets. However, FAQ content can address objections, capture question-style searches, support featured snippets and give AI systems clear question-answer pairs. FAQPage markup remains valid when it matches visible content.
Key takeaways
- Write FAQs from real customer questions, not keyword lists.
- Most business sites will not get FAQ rich results in Google.
- Concise Q&A pairs remain useful for readers and answer engines.
- Keep FAQs on relevant pages, avoid duplicating them site-wide.
Who this guide is for
Content and SEO teams deciding whether FAQ sections and FAQPage markup are still worth the effort.
Understand the change
Until 2023, many sites added FAQPage markup to gain expandable questions under their search result. Google then limited FAQ rich results to well-known, authoritative government and health websites, citing a desire for a cleaner results page. For other sites, the markup is still valid and may be read by search engines, but the visual enhancement in Google results generally no longer appears. Other search engines and tools may treat FAQ markup differently.
Decide why you want FAQs
The strongest reasons now are user-focused: answering objections before people contact you, clarifying pricing, process and eligibility, reducing repetitive support questions and helping readers who scan rather than read. FAQs also give answer engines and AI assistants compact question-answer pairs that are easy to understand and quote. If an FAQ section exists only for a rich result, it is probably not worth adding.
Source questions from real conversations
Use sales call notes, enquiry forms, support tickets, chat transcripts, reviews and “People also ask” results. Choose questions that matter to decisions: how long it takes, what it costs, what the customer needs to provide, what is included and what happens after purchase. Phrase questions the way customers ask them. Avoid filler questions that exist only to repeat keywords.
Write answers that stand alone
Begin each answer with a direct response, then add a sentence or two of context or conditions. Keep answers short enough to scan, typically one to three sentences, and link to fuller explanations where needed. Be accurate and specific; vague answers like “it depends, contact us” frustrate readers. If the honest answer depends on factors, list the main factors.
Place FAQs on the right pages
Put FAQs on the pages where the questions arise: service pages, pricing pages, product pages and detailed guides. Avoid copying the same FAQ block across many pages, which creates duplicate content and dilutes relevance. A central help or FAQ page can collect general questions, but page-specific questions belong in context.
Mark up honestly
If you use FAQPage markup, include only questions and answers that are visible on the page, written by you rather than user-submitted (which belongs in QAPage), and without promotional content in answers. Generate the markup from the same data as the visible FAQ to keep them in sync. Do not expect it to produce a rich result, and validate it to avoid errors.
Measure usefulness
Track whether visitors interact with FAQ sections, whether question-style queries bring impressions to those pages, and whether support teams receive fewer repeated questions. Update answers when policies, prices or processes change. Remove questions nobody asks. FAQ content that stays accurate and useful contributes to trust, which is the underlying goal of SEO, AEO and GEO efforts.
Scope checklist
- Which real customer questions does each page need to answer?
- Do answers start with a direct response?
- Are FAQs specific to the page rather than duplicated?
- Does any FAQPage markup match visible content exactly?
- Who keeps answers current?
Frequently asked questions
Is FAQ schema still worth adding?
It is valid and harmless when accurate, and may help machines understand Q&A content, but most sites will not receive FAQ rich results in Google. Prioritize useful visible FAQ content.
How many FAQs should a page have?
As many as address real, relevant questions for that page, often between three and eight. Quality and relevance matter more than quantity.
Can AI assistants use FAQ content?
AI systems that retrieve web pages can use clear question-and-answer content, as with any well-structured text. There is no guarantee of citation.
Sources and implementation references
- Google Search Central blog: changes to HowTo and FAQ rich results
Announcement limiting FAQ rich results to authoritative government and health sites.
- Google Search Central: FAQPage structured data
Current requirements and eligibility for FAQ markup.
Prepared with AI assistance as an engineering decision guide. Examples are illustrative unless explicitly labelled as an internal implementation. No independent expert review or customer outcome is claimed.
Want more qualified enquiries from search and AI answers?
Share your website, main services and target markets. We review technical, content and conversion gaps before proposing scope. Scope, access, dependencies and commercial terms are agreed before delivery. Do not submit passwords, API keys or confidential records.