FAQ schema is one of the most impactful structured data types for service and informational pages because it can dramatically increase your SERP real estate — folding out two to four question-and-answer pairs directly beneath your listing. It also feeds Google AI Overviews, which makes it increasingly important for visibility in AI-generated answers. Here is how to implement it correctly and what gets people into trouble.

What FAQPage Schema Is

FAQPage is a schema.org type that marks up a page containing a list of frequently asked questions along with their answers. When Google validates it, your search result can expand to show individual Q&A pairs in the SERP without the user clicking through. That expansion can double or triple the vertical space your result occupies on a results page.

Beyond the traditional SERP result, FAQPage-marked content is among the most commonly extracted content for AI Overviews. If your answer is concise, accurate, and well-structured, it stands a real chance of being surfaced directly in AI-generated summaries. For topical authority, that visibility matters even when the click does not come.

FAQPage vs QAPage

These are easy to confuse. The rule is simple:

  • FAQPage: One authoritative answer per question, written by the site owner. The page is an FAQ section — you wrote the questions and the answers. This is appropriate for service pages, product pages, and dedicated FAQ pages.
  • QAPage: Multiple answers per question, contributed by different users. Think Stack Overflow, Quora, or a community forum where users vote on the best answer.

Most business sites should use FAQPage. QAPage is specifically for user-generated, community-answered content. Misusing QAPage on a standard FAQ section is a common error and can cause Google to ignore the markup.

Google Eligibility Rules

Google has published specific guidelines for FAQPage eligibility, and they matter. Violating them will prevent rich results from appearing, or worse, can result in a manual action if the pattern is seen as deceptive.

  • The content must be visible on the page. Every question and answer in your JSON-LD must be readable by a human visitor to that page. Hidden content, collapsed accordions that are not in the DOM, or content that only appears after a JavaScript interaction may not qualify.
  • Markup text must match visible text exactly. The text property in your schema must be word-for-word identical to what appears on the page. Paraphrasing or summarizing in the schema while showing a different version on the page is a violation.
  • Advertising content is not eligible. FAQ schema should not be used on pages that consist primarily of promotional or ad content. It is for genuinely informational Q&A.
  • No duplicate FAQs across pages. If you have the same FAQ block appearing on dozens of pages, Google may choose to show the rich result on only one of them or suppress it across all. Unique FAQs per page perform better.

How to Structure the JSON-LD

The basic structure for FAQPage schema:

<script type='application/ld+json'>
{
  '@context': 'https://schema.org',
  '@type': 'FAQPage',
  'mainEntity': [
    {
      '@type': 'Question',
      'name': 'What does a schema markup consultant do?',
      'acceptedAnswer': {
        '@type': 'Answer',
        'text': 'A schema markup consultant audits, plans, and implements structured data on your website to improve search engine understanding and enable rich results.'
      }
    },
    {
      '@type': 'Question',
      'name': 'How long does schema implementation take?',
      'acceptedAnswer': {
        '@type': 'Answer',
        'text': 'For most service sites, a complete schema implementation takes 3 to 5 business days depending on the number of page types and complexity of the entity graph.'
      }
    }
  ]
}
</script>

Each question is a Question type with a name (the question text) and an acceptedAnswer (an Answer type with a text property). The answers can include basic HTML for links and bold text, but keep them clean and readable.

Common Implementation Mistakes

Using FAQ Schema on Pages Without Visible Q&A

I see this frequently on service pages where someone wants the SERP expansion but has not actually written a visible FAQ section on the page. The schema is there; the content is not. Google will not show the rich result, and if the gap is large enough, the page may be flagged.

Accordion Visibility Issues

Many FAQ sections use accordion-style expand/collapse UI. This is fine for UX, but the question-and-answer text must be in the DOM (not loaded dynamically). If the answer text only appears after a JavaScript click event, Google may not reliably index it. Test your page with Google Search Console’s URL Inspection tool and check whether the rendered HTML includes the full text.

Answers That Are Too Short

Answers of one or two words do not perform well in either traditional rich results or AI Overview extraction. Answers should be 1–3 sentences that fully address the question. If your FAQ answers are placeholder-length, expand them before adding schema.

Copying FAQ Blocks Across Many Pages

Templated FAQ blocks that appear identically across 50 service location pages will underperform. At minimum, customize the questions and answers for each page context. The effort is worth it — unique, specific FAQs get rich result treatment far more consistently.

Not Validating After Publication

Always run the page through Google Rich Results Test after publishing. It will catch syntax errors, property mismatches, and eligibility warnings before they become silent failures in Search Console.

Where FAQ Schema Performs Best

In my experience, these page types see the strongest rich result appearance rate:

  • Service pages with specific questions about process, pricing, and timeline
  • Product pages with technical questions (compatibility, specs, warranty)
  • How-to and instructional content where common follow-up questions are addressed
  • Pillar pages covering broad topics where readers commonly want definitional answers

It is less effective on homepage FAQs (often suppressed in favor of inner pages) and on very short FAQ sections with fewer than three questions.

Combining FAQ Schema with Other Types

FAQPage schema can coexist on a page with other schema types. A service page might carry both FAQPage and Service schema. An article might carry both Article and FAQPage if there is a genuine FAQ section at the bottom. Just make sure each type is in its own <script> block or properly structured within a single block — do not nest incompatible types together.

If you want to understand all the schema types worth implementing, my post on types of schema markup gives a full breakdown. For the technical side of adding any schema type to your site, see how to add schema markup.

For clients working with me through Salterra, FAQ schema is a standard part of any page-level structured data implementation — along with validation, visible-content alignment, and Search Console monitoring. If your FAQ schema is not generating rich results, there is usually a fixable reason. My schema markup consultant page explains how I diagnose and resolve those issues.