FAQPage Schema

Google’s documentation now states FAQ rich results are no longer appearing in Google Search as of May 7, 2026, with FAQ support leaving the Rich Results Test in June 2026 and the Search Console API in August 2026. Do not add FAQPage expecting a rich-result gain — add it only for standards-based structured data on the page itself. Every question and answer in the structured data must appear visibly on the page; hidden content fails validation regardless of engine.

Baseline

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "COMMON — question text matching the visible heading",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "COMMON — answer text; must be visible on the page. HTML allowed."
      }
    },
    {
      "@type": "Question",
      "name": "COMMON — second question; repeat this block for each Q&A pair",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "COMMON — second answer"
      }
    }
  ]
}

Field notes

• Treat existing FAQPage blocks the way you’d treat other retired Google-specific structured-data bets: valid markup can remain, but remove the rich-result expectation from audits, roadmaps, and reporting.
• Use QAPage only when the page centers on a single question with user-submitted alternative answers; a single publisher-authored Q&A stays FAQPage.
• If the same FAQ repeats across many pages, mark up one canonical instance rather than duplicating markup site-wide.
• text in acceptedAnswer can contain basic HTML; keep it close to the visible text to avoid a mismatch flag.
• Google’s AI optimization guide is explicit: there is no special schema required for generative AI search — a weak, inaccessible, or commodity page is not rescued by adding FAQPage.