How many FAQ pairs should I include for the best chance of rich results?

Google does not publish an official limit, but 3–10 high-quality pairs is the recommended range. More than 10 often means some questions are lower-quality filler. Google selects which pairs to display from your markup, so quality matters more than quantity. Focus on questions that reflect real user searches — check your Search Console queries report and site search logs for genuine questions users ask.

Can I add FAQ schema to every page on my site?

You can add it to any page that has genuine FAQ content visible to users. However, Google has been known to reduce or eliminate FAQ rich results site-wide when it appears a site is using the markup purely for SERP space manipulation rather than to answer genuine user questions. Use FAQPage schema only on pages where FAQ content is a genuine, primary part of the page — not as a universal footer element on all pages.

My FAQ schema passes validation but I am not getting rich results. Why?

Several factors can prevent rich results despite valid markup: your site may not yet have enough authority for Google to trust its structured data; the FAQ content may be considered low quality or thin; Google may have determined the queries triggering your page are better served without rich results; or Google may be testing the feature's impact on user satisfaction. Check Google Search Console under Enhancements > FAQ to see if Google has detected your markup and any associated warnings.

How many FAQ pairs should I include for the best chance of rich results?

Google does not publish an official limit, but 3–10 high-quality pairs is the recommended range. More than 10 often means some questions are lower-quality filler. Google selects which pairs to display from your markup, so quality matters more than quantity. Focus on questions that reflect real user searches — check your Search Console queries report and site search logs for genuine questions users ask.

Can I add FAQ schema to every page on my site?

You can add it to any page that has genuine FAQ content visible to users. However, Google has been known to reduce or eliminate FAQ rich results site-wide when it appears a site is using the markup purely for SERP space manipulation rather than to answer genuine user questions. Use FAQPage schema only on pages where FAQ content is a genuine, primary part of the page — not as a universal footer element on all pages.

My FAQ schema passes validation but I am not getting rich results. Why?

Several factors can prevent rich results despite valid markup: your site may not yet have enough authority for Google to trust its structured data; the FAQ content may be considered low quality or thin; Google may have determined the queries triggering your page are better served without rich results; or Google may be testing the feature's impact on user satisfaction. Check Google Search Console under Enhancements > FAQ to see if Google has detected your markup and any associated warnings.

FAQ Page JSON-LD Schema Template

FAQ structured data is one of the highest-impact, lowest-effort schema implementations available. When validated correctly, Google displays your FAQ questions and answers directly in search results as expandable accordion items beneath your page listing. This effectively doubles or triples the vertical space your result occupies on the SERP, and expanded FAQ answers can dominate the screen on mobile devices — dramatically increasing click-through rates even for pages that are not ranking in the top three positions.

Google's FAQ rich results have specific eligibility requirements that differ from other schema types. The page must genuinely contain FAQ content — a list of questions with their corresponding answers. The content must be visible to users on the page, not just in the structured data. Google crawls and compares the schema markup to the visible content; if they do not match, the rich result will not be granted. The FAQPage type is designed for pages where the same organization both asks and answers the questions; community Q&A platforms should use QAPage instead.

Each Question in the FAQPage mainEntity array must have a name property (the question text) and an acceptedAnswer property containing an Answer object with a text property (the answer text). HTML is permitted in the text property of Answer — this is useful for including links to related content, bold text for emphasis, and basic formatting. However, keep answers substantive: thin one-sentence answers are less likely to be selected for display.

The number of FAQ pairs to include is a balance between completeness and schema file size. Google recommends including all FAQ items on the page in the structured data. A page with 3–10 well-crafted Q&A pairs is more likely to earn rich results than one with 20+ low-quality pairs. Google does not display all FAQ pairs from a page — it selects the subset it considers most relevant to the user's query.

Maintenance discipline matters. FAQ rich results are granted and revoked dynamically. If you update the visible FAQ content on your page without updating the schema, Google will detect the mismatch and may revoke the rich result eligibility. Always keep schema and visible content synchronized, especially after CMS content updates.

Template Preview

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your first frequently asked question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This is the detailed answer to the first question. Include enough information to be genuinely helpful — at least two or three sentences. You can include <a href='https://example.com'>links</a> in answers."
      }
    },
    {
      "@type": "Question",
      "name": "What is your second frequently asked question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This is the detailed answer to the second question. Be specific and actionable. Answers with concrete steps or data points are more likely to be selected for display."
      }
    },
    {
      "@type": "Question",
      "name": "What is your third frequently asked question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This is the detailed answer to the third question. Keep answers accurate and up to date — outdated information in FAQ answers can harm user trust and cause Google to revoke rich result eligibility."
      }
    }
  ]
}

Customize this template with your own details using the free generator:

▸Open in Generator

FAQ

How many FAQ pairs should I include for the best chance of rich results?: Google does not publish an official limit, but 3–10 high-quality pairs is the recommended range. More than 10 often means some questions are lower-quality filler. Google selects which pairs to display from your markup, so quality matters more than quantity. Focus on questions that reflect real user searches — check your Search Console queries report and site search logs for genuine questions users ask.
Can I add FAQ schema to every page on my site?: You can add it to any page that has genuine FAQ content visible to users. However, Google has been known to reduce or eliminate FAQ rich results site-wide when it appears a site is using the markup purely for SERP space manipulation rather than to answer genuine user questions. Use FAQPage schema only on pages where FAQ content is a genuine, primary part of the page — not as a universal footer element on all pages.
My FAQ schema passes validation but I am not getting rich results. Why?: Several factors can prevent rich results despite valid markup: your site may not yet have enough authority for Google to trust its structured data; the FAQ content may be considered low quality or thin; Google may have determined the queries triggering your page are better served without rich results; or Google may be testing the feature's impact on user satisfaction. Check Google Search Console under Enhancements > FAQ to see if Google has detected your markup and any associated warnings.

Related Templates

Article JSON-LD Schema Template Product JSON-LD Schema Template Blog Post Meta Tags Template