FAQPage Schema
Definition
FAQPage schema is markup that structures Q&A content to increase AI citation potential.
Summary
FAQPage JSON-LD defines page Q&A pairs in a machine-readable format. Since August 2023, Google Search Rich Results have been limited to government and medical sites, but AI Overviews and voice search still prioritize FAQPage structure. A minimum of 2 Q&A pairs is required.
Problems This Guide Solves
"My FAQ section exists but isn't cited by AI."
Even with Q&A on the page, if machines cannot tell which text is the question and which is the answer, the content cannot be used as structured data. FAQPage schema creates that connection.
Prerequisites
- The page contains at least 2 actual Q&A-format content items
- You have permission to insert JSON-LD on the site (direct HTML editing or CMS plugin)
- Each answer is written in complete sentences
Basic FAQPage Schema Structure
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is AEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "AEO (Answer Engine Optimization) is the practice of optimizing content so AI answer engines such as ChatGPT, Perplexity, and Google AI Overviews cite it."
}
},
{
"@type": "Question",
"name": "What is the BLUF writing method?",
"acceptedAnswer": {
"@type": "Answer",
"text": "BLUF (Bottom Line Up Front) is a content writing pattern that places the core conclusion in the first sentence. AI answer engines prioritize text at the top of the page, so the first paragraph written in BLUF style is more likely to be cited."
}
}
]
}
</script>
Required Fields
| Field | Type | Description |
|---|---|---|
| @context | string | Fixed as "https://schema.org" |
| @type | string | Fixed as "FAQPage" |
| mainEntity | array | Array of Question objects |
| name | string | Question text |
| acceptedAnswer.text | string | Answer text |
Step-by-Step Implementation Guide
Step 1: Write FAQ Content on the Page
Do not write JSON-LD first—the page body must contain actual Q&A text. Google's structured data policy prohibits defining content in JSON-LD only when it is not displayed on the page. name and text in JSON-LD must match visible text.
Step 2: Write Questions in Natural Language
Write the name field in the form of questions users actually search. Use complete sentences, not keyword lists.
- Good example: "How are AEO and SEO different?"
- Bad example: "AEO SEO difference comparison"
Step 3: Apply BLUF to Answers
Put the core of the answer in the first sentence of the text field. AI Overviews often cite answer text verbatim, so sentences should be self-contained and definitive.
"text": "AEO is the practice of optimizing content so AI answer engines cite it. While SEO targets search rankings, AEO targets inclusion in AI answers themselves."
Step 4: Insert JSON-LD in <head>
Wrap in a <script type="application/ld+json"> tag and insert in <head> or <body>. In Next.js, add it from the page component as follows.
export default function Page() {
const faqSchema = {
'@context': 'https://schema.org',
'@type': 'FAQPage',
mainEntity: [
{
'@type': 'Question',
name: 'What is AEO?',
acceptedAnswer: {
'@type': 'Answer',
text: 'AEO is the practice of optimizing content so AI answer engines cite it.',
},
},
],
}
return (
<>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(faqSchema) }}
/>
{/* Page content */}
</>
)
}
Step 5: Validate with Google Rich Results Test
At https://search.google.com/test/rich-results, enter the URL or code to confirm FAQPage schema parses correctly. If "FAQPage" is detected without errors, it is valid.
Changes Since August 2023
In August 2023, Google limited FAQ Rich Results (FAQ accordion in search results) to government and official medical sites only. General websites no longer show FAQ accordions in search results.
However, the AEO value of FAQPage schema has not changed. There are two reasons.
AI Overviews: Google AI Overviews tend to treat Q&A with clear FAQPage structure as citation candidates because machines can clearly know "this text is the question and this text is the answer." Data confirms pages with FAQPage markup are 3.2 times more likely to appear in Google AI Overviews.
Voice search: Voice search systems such as Google Assistant extract answers directly from FAQPage schema and read them aloud.
Connection with AEO
FAQPage schema is most effective when combined with answer block structure. Write the page body's Q&A section as answer blocks (BLUF + self-contained paragraphs) and define the same Q&A in FAQPage JSON-LD to create a double signal.
- Body text → processed as question-answer units during RAG chunk extraction
- FAQPage JSON-LD → Google explicitly recognizes Q&A structure
Aggarwal et al. (2024) KDD research experimentally confirmed that structured content optimization can increase AI citation potential by up to 40%.
Validation Methods
- Google Rich Results Test: Check JSON-LD parsing errors
- Google Search Console: Check FAQPage errors in the "Rich results" report
- AI test: Enter FAQ questions in ChatGPT and provide the page URL as context to verify accurate answer extraction
Frequently Asked Questions
Q. Is there a limit on the number of FAQ questions?
A. Google Rich Results guidelines allow up to 10 Q&A items in Rich Results. There is no limit on Q&A count in JSON-LD itself, so you can define more. From an AI Overviews citation perspective, more Q&A increases citation opportunities.
Q. Can I use HTML tags in answer text?
A. Google allows limited HTML in the text field (<br>, <ul>, <li>, etc.). However, plain text is safer. AI systems often strip HTML tags and process text only.
Q. Must I add FAQPage schema to every page?
A. Apply only to pages with actual Q&A-format content. Adding FAQPage schema to pages without FAQ content violates Google policy.
Q. How can I easily add FAQPage schema in WordPress?
A. Yoast SEO Premium or RankMath Pro FAQ blocks automatically generate FAQPage JSON-LD. In free versions, add code directly using <head> insertion features.
Q. Should I remove FAQPage schema after August 2023?
A. Removal is not recommended. Search result Rich Results disappeared for general sites, but AI Overviews, voice search, Bing Copilot, and other channels still prioritize FAQPage structure. Maintenance cost is low with potential benefits.
Related Sources
- Google Search Central. FAQ (FAQPage) structured data. https://developers.google.com/search/docs/appearance/structured-data/faqpage
- Google Search Central (2023). Changes to FAQ and How-to rich results. https://developers.google.com/search/blog/2023/08/howto-faq-changes
- Aggarwal, S., et al. (2024). GEO: Generative Engine Optimization. KDD 2024. https://arxiv.org/abs/2311.09735
이 페이지를 참조하는 항목
- 📘ConceptClick-Through Rate (CTR)
- 📘ConceptPAA (People Also Ask)
- 📘ConceptQuery Fan-Out
- 📘ConceptGEO Master Guide: 5-Area Checklist
- 📘ConceptHow RAG Works
- 📘ConceptWhat Is AEO?
- 📘ConceptWhat Is GEO?
- 📘ConceptWhat Is SEO?
- 📘Concept50-Word Rule
- 📙How-toHow to Build Answer Blocks
- 📘ConceptContent Freshness
- 📙How-toHow to Write BLUF
- 📘ConceptYMYL (Your Money Your Life)
- 📙How-toGoogle Business Profile
- 📘ConceptBreadcrumb
- 📙How-toH Tag Hierarchy Design
- 📘ConceptGoogle AI Overviews
- 📘ConceptComplete Guide to Article · NewsArticle · BlogPosting Schema
- 📘ConceptJSON-LD Basics
- 📘ConceptRich Snippet
- 📒ToolALLEO