FAQ Rich Results Schema: Complete Guide
FAQ rich results let Google display your questions and answers directly in the search results page as an expandable accordion beneath your blue link. When implemented correctly, they can significantly expand your SERP real estate and improve click-through rates by up to 20–30%. This guide covers everything you need to know to implement, test, and troubleshoot FAQ schema markup.
What Are FAQ Rich Results?
FAQ rich results are a search feature that shows a list of questions and their answers beneath a page's standard search snippet. Each question is clickable and expands to reveal the answer inline. Google introduced this feature to help users find quick answers without clicking through, while giving sites more prominent SERP placement. They appear on both desktop and mobile and are triggered by valid FAQPage schema markup on the page. Only pages where the content is genuinely presented as a FAQ — with both questions and answers visible to users — are eligible.
Required Schema Markup (JSON-LD)
Implement FAQPage schema using JSON-LD in the <head> or <body> of your page. Each question maps to a Question type with a nested acceptedAnswer of type Answer. Here is a minimal valid example:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is an XML sitemap?",
"acceptedAnswer": {
"@type": "Answer",
"text": "An XML sitemap is a file that lists the URLs on your site, helping search engines discover and index your content more efficiently."
}
},
{
"@type": "Question",
"name": "How do I submit a sitemap to Google?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Submit your sitemap through Google Search Console under the Sitemaps report. Enter the sitemap URL and click Submit."
}
}
]
}Required vs Recommended Properties
The required properties are @type: FAQPage, mainEntity (array of Question), each Question with a name (the question text), and an acceptedAnswer with a text property. The recommended additions include wrapping the JSON-LD in a proper script tag, ensuring the answer text can contain limited HTML (anchor, bold, italic, lists, breaks), and keeping answers concise — Google truncates long answers in the SERP. You should also make sure every Q&A pair visible in the schema also appears visually on the page.
Eligibility Requirements
Not every page with FAQ schema will receive the rich result treatment. Google requires that the FAQ content is genuinely authored by the site (not user-generated) and that each question and answer is directly visible on the page — the schema must reflect the actual page content, not hidden content. Pages that use FAQs primarily for advertising purposes or that show the same FAQ across every page of a site may be demoted. Additionally, the page must be indexed, must not have a noindex tag, and must pass Google's quality thresholds for the domain.
How to Test FAQ Rich Results
Use Google's Rich Results Test (search.google.com/test/rich-results) and paste your page URL or code snippet. It will show whether FAQ rich results are detected and flag any errors. You can also use Schema Markup Validator (validator.schema.org) for spec compliance. In Google Search Console, navigate to the "Enhancements" section — once Google processes your page, a FAQs report will appear showing valid items, warnings, and errors. Always test in both tools since the Rich Results Test checks Google's interpretation while the validator checks spec conformance.
Common Mistakes to Avoid
The most common FAQ schema mistakes include: using FAQ schema on pages where the questions are not actually on the page (schema mismatch); marking up user-generated Q&A content that belongs under QAPage instead; adding FAQ schema to every page of a site with identical Q&A (Google may ignore repetitive markup); placing the JSON-LD inside a dynamically rendered section that Googlebot can't crawl; nesting special characters improperly (break & as & in HTML text nodes); and exceeding Google's recommended limit of around ten questions per page.
FAQ Rich Results Not Showing? How to Fix
If your FAQ schema is valid but rich results are not appearing in search, the most likely causes are: the page was recently published and Google has not re-crawled it yet (wait 2–4 weeks); the page does not meet Google's quality bar; the questions in the schema do not match what is visible on the page; or the site has a manual action. Check Search Console for any manual actions, ensure the page is indexed (use the URL Inspection tool), confirm the schema validates in the Rich Results Test, and verify the Q&A content is rendered in HTML rather than JavaScript that Googlebot cannot execute.
FAQPage vs QAPage Schema
FAQPage and QAPage are often confused. Use FAQPage when the site itself authors both the questions and the definitive answers — typical product FAQ sections, help center pages, or editorial FAQ content. Use QAPage when the content is user-generated, such as a community forum or Q&A platform where users ask questions and multiple people post answers. Google treats these differently: FAQPage generates the accordion-style rich result, while QAPage generates a different format showing the top voted or accepted answer. Mismatching the type to the content will result in the rich result being withheld.
Best Practices for FAQ Content
Write questions the way real users phrase them — use keyword research to identify actual search queries, then structure your FAQ around those phrases. Keep answers between 50–300 words: short enough to be scannable in a SERP accordion, but substantive enough to be useful. Avoid promotional language in answers; Google has been known to suppress rich results from pages where FAQ answers read like ads. Update your FAQ markup whenever the page content changes, and use SitemapFixer to audit your schema after each deployment to catch regressions before Google re-crawls the page.
Impact on CTR and Rankings
FAQ rich results visually expand your search listing, sometimes doubling or tripling the vertical space your result occupies on a SERP. Studies by SEO practitioners consistently show CTR improvements of 15–30% for pages that earn FAQ rich results, particularly on informational queries where the expanded snippet answers the searcher's micro-question and entices a click for the full answer. While schema markup is not a direct ranking factor, the resulting CTR improvements send behavioral signals that can indirectly support higher rankings over time. Test systematically by enabling FAQ schema on a subset of similar pages and measuring CTR changes in Search Console.