FAQPage schema is a block of JSON-LD that mirrors a question and answer section that is already visible on your page. The way to implement it correctly is to write the visible questions first, then generate the markup from the same text. The bottom line: Google no longer shows FAQ rich results, so the markup is no longer a traffic lever in Google, but it remains valid schema.org vocabulary, and the visible question and answer section does most of the work for AI systems that read your page.

What changed, and when

DateWhat happened
2019Google introduced FAQ rich results, expandable question and answer panels under a search listing.
August 2023Google restricted FAQ rich results to well known government and health sites. For most sites the dropdowns disappeared.
May 7, 2026Google stopped showing FAQ rich results in Search entirely.
June and August 2026The Search Console FAQ report was retired, and API support for it was removed.

Google has said you do not need to remove existing FAQPage markup, and the FAQPage vocabulary on schema.org remains valid. What is gone is the display feature.

Should you still implement it

Yes, with realistic expectations. Microsoft's Fabrice Canel said in March 2025 that schema markup helps Microsoft's language models understand content for Copilot. A December 2024 Search/Atlas study found no correlation between schema coverage and citation rates, and there is no published controlled study showing FAQPage markup increases citations in ChatGPT, Perplexity, or Gemini. The defensible position is that the markup is cheap and harmless when accurate, and the visible question and answer formatting does the load bearing work.

Steps

  1. Choose real questions. Use questions customers actually ask, from sales calls, support email, and your own monitoring of AI answers.
  2. Write each answer in full on the page. Two to four sentences that stand alone, so a system can lift one answer out without the rest of the page.
  3. Put each question in a heading. An H2 or H3 for each question makes the structure visible to machines and readers.
  4. Generate the JSON-LD from the same text. The markup must match the visible words. Do not add questions to the markup that the page does not show.
  5. Use FAQPage only for questions you answer yourself. Pages where visitors submit answers use QAPage instead.
  6. Validate it. Test at validator.schema.org and confirm the block appears in the raw HTML.
  7. Maintain it. When an answer changes on the page, change it in the markup in the same edit.
<div class="faq">
  <h3>How long does an emergency plumbing visit take?</h3>
  <p>Most emergency visits take 60 to 90 minutes once a technician arrives.</p>
  <h3>Do you charge extra for weekend calls?</h3>
  <p>Weekend calls carry a flat after hours fee, listed on our pricing page.</p>
</div>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question",
      "name": "How long does an emergency plumbing visit take?",
      "acceptedAnswer": { "@type": "Answer",
        "text": "Most emergency visits take 60 to 90 minutes once a technician arrives." } },
    { "@type": "Question",
      "name": "Do you charge extra for weekend calls?",
      "acceptedAnswer": { "@type": "Answer",
        "text": "Weekend calls carry a flat after hours fee, listed on our pricing page." } }
  ]
}
</script>

Common mistakes

Our scan credits question and answer content in two ways: FAQPage or Question schema, or three or more question style headings, so a page with visible question headings passes even without the markup.

Questions people ask

Does FAQPage schema still work?

Google stopped showing FAQ rich results on May 7, 2026, so it no longer creates dropdowns in Google. The markup remains valid schema.org vocabulary and Google says you do not need to remove it.

Should I remove my FAQ schema?

Not unless it is hidden or stale. Keep accurate markup, and keep the visible question and answer content either way.

Does FAQPage schema help AI citations?

Evidence is mixed. Microsoft says schema helps Copilot understand content, but a Search/Atlas study found no correlation with citation rates and no controlled study shows a lift in ChatGPT, Perplexity, or Gemini.

What is the difference between FAQPage and QAPage?

FAQPage is for questions the site owner answers. QAPage is for pages where users submit answers, such as a forum thread.

Sources