FAQPage schema

What it does for AI citation

It is the closest thing to handing an assistant a pre-formatted answer. A question-and-answer pair is exactly the shape a model wants to quote, which makes this the highest-leverage type per hour of work for AI citation specifically.

A working example

Paste this into a <script type="application/ld+json"> tag in your page head and replace the values. It is valid as written.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does setup take?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "About ten minutes. You add your domain, confirm the questions we suggest, and the first check runs immediately."
    }
  }]
}

What actually goes wrong

These are the errors that show up repeatedly on real sites, in rough order of how often we see them.

• Marking up questions that do not appear visibly on the page. That is a guidelines violation, not a shortcut.
• One-line answers. An answer too thin to stand alone is too thin to be quoted, which defeats the point.
• Putting FAQPage on a page that is not an FAQ, in the hope of rich results.
• HTML left unescaped inside the answer text, which breaks the JSON and silently kills the whole block.

Markup is necessary, not sufficient

Valid FAQPage does not buy you a citation. It makes your page legible, which is the precondition. Whether an assistant names you when a buyer asks also turns on your content, how current the page is, and who else on the web corroborates you. Any tool that tells you markup alone will get you cited is overselling.

Other types