What Is FAQPage Schema?
FAQPage schema is structured data from schema.org that marks up a list of questions and their answers on a page so search engines can identify them as a frequently asked questions section. Delivered as JSON-LD, each entry pairs a Question with an accepted Answer. Search engines use it to understand Q&A content, and historically it could produce expandable FAQ rich results in Google, though eligibility has narrowed to certain authoritative sites since 2023.
- Vocabulary
- schema.org/FAQPage with Question and Answer entities (schema.org)
- Rich result status
- Limited to authoritative government and health sites since Aug 2023 (Google Search Central)
- Content rule
- Answers must be author-written, not user-submitted, and match the page (Google Search Central)
- Still useful for
- AI Overviews, voice answers, and content clarity (industry-typical)
What is FAQPage schema and what changed? #
FAQPage schema is the code that tells a search engine, this section is a set of questions and the answers to them. Each item is a Question object whose acceptedAnswer holds the response text. It is one of the most widely deployed schema types because almost every business has FAQs. For years, adding it could earn an eye-catching rich result: your listing expanded to show clickable questions right in the search results, taking up more space and pushing competitors down. In August 2023 Google narrowed that rich result to well-known, authoritative government and health websites, so most local businesses no longer see the expandable FAQ display. That change disappointed many, but the markup did not become useless. It still helps machines understand your content, and that understanding increasingly feeds AI Overviews and voice assistants, as covered in /wiki/what-are-ai-overviews and /wiki/ai-search-optimization. The rich result faded; the underlying value shifted.
Is FAQPage schema still worth adding in 2026? #
Yes, but for different reasons than in 2021. The classic rich result is largely gone for local businesses, so if your only goal was those expandable questions, temper expectations. What remains valuable is machine comprehension. AI Overviews and answer engines pull directly from clearly structured Q&A content, and schema makes your answers easier to extract and cite. Voice assistants favor concise, well-marked answers. Well-organized FAQ content also improves the user experience on the page itself, reducing support calls and pre-answering objections before a customer contacts you, which lifts conversions in ways our /services/conversion-optimization work measures. The schema is cheap to add and carries little downside when implemented honestly. The honest caveat matters: do not add FAQPage markup hoping to force a rich result Google no longer grants, and never mark up questions that are really promotional copy in disguise. Use it where you genuinely have questions and answers, generated cleanly through /tools/schema-generator.
How do you write FAQPage JSON-LD correctly? #
The structure is straightforward. The top-level object is FAQPage, and its mainEntity is an array of Question objects. Each Question has a name, which is the question text, and an acceptedAnswer, which is an Answer object with a text property holding the answer. The answer text may include basic HTML like links and lists. Every question you mark up must appear visibly on the page with the same answer; hidden or altered content violates Google's guidelines and can trigger a manual action. Do not use FAQPage for content where multiple users submit competing answers; that is QAPage, a different type. Keep answers genuinely helpful and self-contained. The example below shows two questions for a dentist. After deploying, validate with /tools/schema-validator and inspect the live page in Google Search Console. Because eligibility for rich results is limited, the main confirmation you seek is simply that the markup parses without errors and reflects the visible page.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do you accept dental insurance?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We accept most major PPO plans and file claims for you. Call our office to confirm your specific plan before your visit."
}
},
{
"@type": "Question",
"name": "How often should I get a cleaning?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most patients benefit from a professional cleaning every six months, though we may recommend more frequent visits based on your gum health."
}
}
]
}What are the content rules Google enforces? #
Google's guidelines for FAQPage are specific and worth respecting because violations risk manual penalties. First, the FAQ content must be written by the site owner, not submitted by users; user-generated Q&A belongs in QAPage. Second, the marked-up questions and answers must be visible on the page, exactly matching what the schema declares. Third, the content should not be primarily promotional or advertising; marking up 'Why is Rivertown Plumbing the best?' with a sales pitch invites trouble. Fourth, do not use FAQ markup to duplicate the same handful of questions across dozens of pages just to game the system. The safest approach is to write FAQs that genuinely help a reader decide or troubleshoot, then mark up exactly what appears. This aligns with how we build every /services/web-design project: the FAQ serves the customer first and the schema simply describes it. When content is honest and useful, the schema carries no risk and quietly helps machines and AI systems understand you.
How does FAQPage schema help with AI Overviews and voice? #
The center of gravity for FAQ content has moved from blue-link rich results to answer engines. AI Overviews, described in /wiki/what-are-ai-overviews, synthesize responses by pulling from clearly structured, authoritative content, and a well-marked FAQ is exactly the kind of clean question-answer pair these systems favor for extraction. Voice assistants, which read a single concise answer aloud, similarly reward tightly written responses. When a searcher asks 'does the plumber in Austin offer emergency service,' a page whose FAQ explicitly poses and answers that question is far easier for a machine to surface and cite than the same information buried in a paragraph. Our /wiki/ai-search-optimization entry covers this shift in detail. Practically, this means you should write FAQ answers as if a machine will read one of them aloud with no surrounding context: lead with the direct answer, keep it under about 50 words, and avoid pronouns that only make sense mid-conversation. The schema then labels these gems so systems find them.
Where should FAQs live on a local business site? #
FAQ content works best where it answers real hesitation at the moment of decision. On a service page, address the questions that stall a booking: pricing ranges, availability, warranty, licensing, what to expect. On a location or contact page, cover hours, parking, and service area. A dedicated FAQ page is fine for general questions but often converts less than FAQs embedded on the page where the doubt arises. For a law firm, questions about consultation cost and confidentiality belong on the practice-area page; for a gym, questions about contracts and trial passes belong on the membership page. This is a content-strategy decision as much as a technical one, and it is part of how we structure sites in /services/web-design and refine them through /services/conversion-optimization. Mark up whichever FAQs are genuinely present. Avoid the temptation to bolt a generic FAQ block onto every page purely for schema; relevance to the page's purpose is what makes both the content and the markup effective.
How do you implement and maintain FAQPage schema? #
On WordPress, many SEO and block plugins output FAQPage schema automatically when you use their FAQ block, and a developer can wire this up through /services/wordpress-development so editors just fill in questions. On a custom site, place the JSON-LD in the page template and populate it from the same source that renders the visible FAQ, guaranteeing they never drift apart. That single-source approach is the most important maintenance principle: if the visible answer and the schema answer come from one field, they cannot contradict. Generate the initial markup with /tools/schema-generator, validate with /tools/schema-validator, and confirm in Google Search Console that it parses. Revisit your FAQs periodically, because the questions customers ask change as your services, pricing, and policies evolve. Retire outdated answers rather than leaving stale ones marked up. Because FAQ maintenance is easy to forget once the page is live, we fold it into /services/care-plans so the answers stay current and accurate over the life of the site.
Common mistakes and how to avoid them #
The biggest mistake is expecting the old expandable rich result; for most local businesses it will not appear, so judge success by comprehension and AI visibility, not by a badge. The second is marking up content that is not visible on the page, which breaks Google's rules. The third is using FAQPage for user-submitted questions, which should be QAPage. The fourth is stuffing keyword-loaded pseudo-questions that no real person would ask, which reads as manipulation to both users and machines. The fifth is duplicating the same FAQ block across many unrelated pages. The sixth is letting answers go stale after a price or policy change. Avoid all of these by writing genuine, page-relevant questions, keeping schema tied to visible content through a single source, and validating every change. Done this way, FAQPage schema is a low-cost, low-risk addition that improves clarity for readers, helps AI systems answer questions about your business accurately, and supports the broader structured-data strategy in our /wiki/schema-markup-guide.
FAQ
Does FAQPage schema still show rich results in Google?
For most local businesses, no. Since August 2023 Google limits FAQ rich results to well-known, authoritative government and health websites. Ordinary business sites usually will not see the expandable questions in search results anymore. The markup remains useful for machine comprehension, AI Overviews, and voice answers, but expect no visual rich result from it.
Is it worth adding FAQPage schema if the rich result is gone?
Often yes. The schema helps AI Overviews and answer engines extract and cite your Q&A content, supports voice assistants, and improves clarity for readers. It is cheap to add and low-risk when implemented honestly. Just add it because it helps machines understand genuine FAQ content, not because you expect an expandable rich result.
What is the difference between FAQPage and QAPage schema?
FAQPage is for questions and answers written by the site owner, like a business FAQ. QAPage is for pages where users submit questions and other users provide competing answers, like a community forum thread. Using the wrong type violates Google's guidelines, so match the schema to who actually authors the answers.
Can I put the same FAQ schema on every page?
You should not. Google discourages duplicating identical FAQ blocks across many pages purely to add markup. Instead, place FAQs where they answer real questions relevant to that specific page, and mark up only the questions actually visible there. Relevance to the page's purpose makes both the content and schema effective.
How long should FAQ answers be?
Aim for concise, self-contained answers of roughly 40 to 60 words that lead with the direct response. This length reads well for humans, extracts cleanly for AI Overviews, and works if a voice assistant reads it aloud. Avoid pronouns that only make sense mid-conversation, since a machine may surface the answer with no surrounding context.
Will FAQ schema hurt my rankings if done wrong?
It can. Marking up content that is not visible, using promotional pseudo-questions, or applying FAQ markup to user-generated content violates Google's guidelines and risks a manual action. Implemented honestly, with visible content tied to the schema through a single source and validated before deployment, FAQPage schema carries little risk.
Was this helpful?