FAQPage schema is one of the easiest rich results to implement and one of the highest-impact — it adds expandable question-and-answer dropdowns directly below your search result, doubling your SERP real estate without needing a higher rank. A 20–30% CTR improvement is common on pages where FAQ rich results appear.

+20–30%

Average CTR lift with FAQ rich results

2 max

FAQ dropdowns Google shows per result

~10 min

Time to implement on any page

1. Complete FAQPage Schema Template

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer a 30-day hassle-free return on all orders.
          Items must be unused and in original packaging.
          <a href='https://example.com/returns'>
          View our full return policy.</a>"
      }
    },
    {
      "@type": "Question",
      "name": "How long does shipping take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard shipping takes 3–5 business days within
          the US. Express shipping (1–2 days) is available
          at checkout for an additional fee."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer international shipping?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We ship to over 50 countries.
          International orders typically arrive in 7–14 business
          days depending on the destination."
      }
    }
  ]
}

💡 HTML is allowed in Answer text

The text field of acceptedAnswer accepts a limited set of HTML tags: <a>, <br>, <ul>, <li>, <b>, <strong>. This lets you add clickable links into answers displayed in the rich result.

2. Eligibility Requirements

✅ Eligible pages

• Pages with a real Q&A / FAQ section visible to users
• The questions and answers in schema must match what's on the page
• Product pages with a questions section
• Service pages with FAQ sections
• Support / help documentation pages
• Blog posts with a FAQ section at bottom

❌ Not eligible

• FAQ schema on pages where the Q&A isn't actually visible
• Promotional or advertising content
• Government, health, or legal pages (limited by Google)
• Forum-style pages where user answers change (use QAPage instead)
• Pages with only 1 question (technically valid but rarely shown)

3. FAQPage vs QAPage — Which to Use

Type	Use when	Answer source
FAQPage	Your site publishes authoritative answers	One accepted answer per question — written by you
QAPage	Community Q&A (like Stack Overflow or Reddit)	Multiple community answers; one may be marked accepted

4. Next.js Implementation

// components/FaqSchema.tsx
const faqs = [
  {
    question: "What is your return policy?",
    answer: "30-day returns on all orders. Items must be unused."
  },
  // add more...
];

export default function FaqSchema() {
  const schema = {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": faqs.map(({ question, answer }) => ({
      "@type": "Question",
      "name": question,
      "acceptedAnswer": { "@type": "Answer", "text": answer }
    }))
  };

  return (
    <script
      type="application/ld+json"
      dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
    />
  );
}

5. WordPress: Adding FAQ Schema

🔧 Yoast SEO Premium

Add FAQ Block in the Gutenberg editor. Yoast automatically generates FAQPage schema from the block content — no manual JSON-LD needed.

🔧 RankMath

Use the FAQ block, which auto-generates schema. Or use RankMath's Schema Generator for custom FAQ schema.

🔧 Manual via functions.php

Use wp_head() to inject a <script type="application/ld+json"> block with your FAQ schema, dynamically generated from ACF custom fields.

6. Why Your FAQ Rich Results Might Not Appear

🚩 FAQs not visible on the page

✅ Google requires the Q&A to be visible in the page content, not only in schema. Use an accordion that is open by default or shows content without JS.

🚩 Schema questions don't match page content

✅ The "name" in your Question must match the actual question text on the page. Any divergence may cause Google to ignore the schema.

🚩 Too many questions (100+)

✅ Google typically displays only 2 FAQ dropdowns per result. Having too many questions doesn't help — focus on the 3–5 most valuable questions.

🚩 Used on promotional content

✅ Google restricts FAQ rich results from pages that are primarily advertisements or lead generation. The content must be genuinely informational.

Frequently Asked Questions

How many FAQ questions should I add to get the rich result?▼

Google shows a maximum of 2 expandable FAQ dropdowns per search result, regardless of how many questions you mark up. Include 3–6 well-chosen questions. More than 10 rarely helps and can signal that you are trying to game the feature rather than genuinely help users.

Can I reuse the same FAQ schema on multiple pages?▼

No. FAQ schema must match the Q&A content of the specific page it is on. Copying identical FAQ schema across multiple pages violates Google’s structured data guidelines (duplicate content in schema). Each page needs its own unique questions relevant to that page’s topic.

Does FAQ schema still work in 2026 after Google’s changes?▼

Google restricted FAQPage rich results in 2023, limiting them primarily to authoritative government and health sites for competitive queries. However, for informational blog posts, product pages, and non-health content, FAQPage rich results still appear regularly in 2026. The key is that the page must be genuinely informational, not promotional.

Can I use FAQ schema on a product page?▼

Yes, if the product page has a real FAQ section visible to users. E-commerce product pages with a Q&A section (return policy, compatibility questions, sizing) are eligible. The schema questions must match the on-page content exactly.

Is there a character limit for FAQ answers?▼

Google does not publish a hard character limit, but answers displayed in FAQPage rich results are truncated in the UI after approximately 300–400 characters. Long answers are still valuable for content quality, but front-load the most important information in the first sentence so it appears in the collapsed preview.

My FAQ schema validates but the rich result doesn’t show. What’s wrong?▼

Validation passing means the schema is syntactically correct — but Google may still withhold the rich result. Common reasons: (1) the page is classified as promotional or commercial; (2) the Q&A is not visibly on the page (hidden behind JavaScript tabs or accordions that block indexing); (3) the site does not have sufficient authority for that query type; (4) Google is actively testing/suppressing FAQ rich results for that query category.

Can I use HTML in FAQ answers?▼

Yes — the acceptedAnswer text field allows a limited HTML subset: <a>, <br>, <ul>, <ol>, <li>, <b>, <strong>, <i>, <em>. This lets you include clickable links in the answer. Avoid using <div>, <p>, or <script> tags; they are stripped or cause validation warnings.

Should FAQ schema go in the <head> or <body>?▼

Either works. In Next.js App Router, placing the script tag in the page.tsx Server Component outputs it in the document body before the main content, which is fine. Google parses application/ld+json regardless of position. Many developers prefer the <head> for organisation, but practically it makes no difference to Google’s parser.

Validate Your FAQPage Schema

Check your FAQPage JSON-LD for eligibility errors before deploying.

Validate FAQ Schema →

FAQ Schema Markup: How to Get Expandable Questions in Google Search