FAQPage schema markup

Does Google still show a rich result for this?

Retired. Google restricted the FAQ rich result to well-known government and health sites in September 2023, then withdrew it altogether — it stopped appearing in Google Search on 7 May 2026, and the documentation was removed in June 2026. Nobody qualifies now, including the sites that kept it during the restriction. Advice describing FAQ markup as merely "limited" is itself out of date.

When to use it

Still worth adding where you have genuine question-and-answer content, but for machine-readability rather than for a search feature. It states unambiguously which text is the question and which is the answer, which is what anything parsing the page needs.

Recommended properties

• mainEntity
• mainEntity.name
• mainEntity.acceptedAnswer.text

Example

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does SEO take to work?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Longer than most people expect, and the honest answer depends on your starting point."
    }
  }]
}

Common mistakes

• Adding it expecting the expandable dropdown. That result no longer exists for anyone.
• Marking up questions that are not visible on the page. Google requires markup to match visible content, and it remains the rule regardless of the rich result.
• Using it for a support forum where users post answers. That is a different type.
• Keeping guidance that says it is restricted to government and health sites. That was the position between September 2023 and May 2026.

Verified against Google’s structured data documentation and its changelog on 28/07/2026. Google changes what it supports without much notice — if you are reading this long afterwards, check the current documentation before acting on it. Background on why this markup matters beyond rich results is in the answer engine optimisation guide.