"FAQPage" schema

FAQPage schema marks up a page containing a list of frequently asked questions, each paired with a single, definitive answer. It's used to identify Q&A content for search engines.

Notes regarding Google

In August 2023, Google significantly limited FAQ rich results. They now only display in Google for "well-known authoritative government and health websites". For websites outside these niches, FAQ markup is still valid and machine-readable, but it will not produce the expandable Q&A rich result in Google Search anymore.

This doesn't make FAQ schema useless, however — it still helps with semantic understanding, as well as AI citations and mentions — but it should no longer be implemented with Google rich results as the goal.

When to use FAQPage schema

The page must contain a genuine list of questions and answers authored by the site itself. Don't use FAQPage for:

• Forum or community pages where users submit answers (that's QAPage)
• Pages with only one question
• Promotional content disguised as questions (this violates Google's content policy)

Key properties

• mainEntity – an array of Question items
• Each Question needs:
  • name – the question text
  • acceptedAnswer – an Answer object with text (the answer body, can include HTML)

Example (JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer service in regional Victoria?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we service all regional Victorian postcodes with a 1–2 day lead time."
      }
    },
    {
      "@type": "Question",
      "name": "What payment methods do you accept?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We accept all major credit cards, bank transfer, and PayPal."
      }
    }
  ]
}

Where to focus

While both the Question and Answer are important, the Answer is the most valuable piece of the puzzle.

The question's job is mostly framing. It needs to be a genuine question and match what's visible on the page, but it should be short and structural; don't stuff keywords into questions in the hope of increasing organic rankings.

The answer is where the substance has to be. Google's guidelines require the full answer text in the markup, and the answer must completely resolve the question — thin, partial, or promotional answers are what trigger problems.

SEO/GEO value

• Helps LLMs and AI search surfaces extract clean Q&A pairs
• Reinforces topical relevance and entity coverage
• Still a valid signal for Bing and other search engines
• Eligible for FAQ rich results only on qualifying gov/health domains

Schema

Disclaimer: All information contained herein is for informational purposes only. It is not advice or instructional.