FAQ content has FAQPage schema

The two biggest AI-answer vendors disagree about schema, and this check reflects both positions honestly. Microsoft's Bing guidance explicitly recommends JSON-LD schema for AI search answers — "Schema is a type of code that helps search engines and AI systems understand your content" — and Bing's index powers Microsoft Copilot and feeds ChatGPT search as a named third-party provider. Google says the opposite for its own AI features: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add," while still recommending it for rich-results eligibility. Net: FAQPage markup on existing FAQ content is a low-cost win on the Bing/Copilot side and harmless on the Google side. It is not a gate — well-written visible Q&A is extractable without it.

Add a FAQPage JSON-LD block to any page with FAQ content. Each visible question needs a corresponding Question entry — stale subsets (fewer than 80% of visible questions) fail the check.

// Inline in your FAQ page component
<script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify({
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": faqItems.map(item => ({
    "@type": "Question",
    "name": item.question,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": item.answer
    }
  }))
})}} />

Derive schema entries directly from the same data array that renders the visible FAQ, so the schema never gets out of sync. Avoid hardcoding a subset of questions.