What FAQ Schema Does for Your Search Presence
FAQ schema (FAQPage structured data) tells Google that a page contains a list of questions and answers. When rendered as a rich result, FAQ markup expands your search listing with collapsible question-and-answer pairs directly in the SERP. This can increase your listing height by 2-3x compared to a standard snippet, dramatically improving click-through rates.
Google's guidelines restrict FAQ schema to pages where the questions and answers are visible on the page itself. You cannot use FAQ markup for pages where users submit questions (use QAPage instead), for a single question-and-answer pair (use the Q&A type), or for content not actually visible on the page.
Correct JSON-LD Implementation
Place this in a <script type="application/ld+json"> tag in the page's <head> or <body>:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the return policy for online orders?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Online orders can be returned within 30 days of delivery for a full refund. Items must be unworn and in original packaging. Initiate returns through your account dashboard or contact support at 1-800-555-0100."
}
},
{
"@type": "Question",
"name": "How long does standard shipping take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Standard shipping takes 5-7 business days within the continental US. Express shipping (2-3 business days) and overnight options are available at checkout for an additional fee."
}
}
]
}
Key requirements: the @type must be FAQPage at the top level. Each question uses the Question type with name (the question text) and acceptedAnswer containing an Answer type with text. The text field supports limited HTML: <a>, <b>, <br>, <ol>, <ul>, <li>, <p>, <h2>-<h6>.
Common Validation Errors
Missing Required Fields
The most frequent error is omitting acceptedAnswer or using suggestedAnswer instead. Google only renders rich results from acceptedAnswer.
Content Mismatch
If your FAQ schema contains questions or answers not visible on the page, Google will flag it as a structured data spam issue in the Manual Actions report. Ensure a 1:1 match between your markup and on-page content.
Nested or Duplicate Schemas
Do not nest FAQPage inside other schema types or include multiple FAQPage schemas on the same page. One FAQPage per page, at the top level.
Using FAQ Schema on Every Page
Google has been reducing FAQ rich result eligibility. As of late 2023, FAQ rich results only appear for well-known, authoritative government and health websites for many query types. For commercial sites, FAQ schema may still improve Google's understanding of your content even without a visible rich result.
Validation Process
- Test before deploying: Paste your markup into Google's Rich Results Test tool
- Check for warnings: Warnings do not block rich results but should be addressed
- Monitor in GSC: After deployment, check Search Console > Enhancements > FAQ to see impression and error counts
- Validate page rendering: Ensure Google can see the FAQ content by using URL Inspection > View Tested Page
Performance Tracking
In Google Search Console, filter the Performance report by Search Appearance > "FAQ rich results" to isolate the impact. Compare CTR for pages with FAQ rich results against those without. A well-implemented FAQ schema typically lifts CTR by 15-30% when the rich result renders.
Track the FAQ enhancement report in GSC weekly. If valid items drop suddenly, a template change likely broke the markup. Act within 24 hours because Google deactivates rich results for pages with schema errors almost immediately.