FAQ Schema for AEO: Feeding Answer Engines Quotable Q&A

FAQPage schema wraps your questions and answers in machine-readable JSON-LD — turning prose an AI engine has to interpret into facts it can quote with confidence. Google stopped showing FAQ rich results for most sites in 2023, and people wrongly concluded FAQ schema was dead. For answer engines, it’s the single most useful markup you can add.

Why answer engines love it

An AI engine assembling an answer needs to (a) find a passage that answers the question and (b) be confident it parsed the passage correctly. FAQPage markup removes the guesswork: here is the question, verbatim; here is the complete answer, verbatim. Pages with clean Q&A markup get quoted more and misquoted less.

The template

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does delivery take in the UK?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Standard UK delivery takes 2–3 working days and is free over £50. Next-day delivery is £6.95 if ordered before 2pm."
      }
    },
    {
      "@type": "Question",
      "name": "Do you ship internationally?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes — we ship to the EU, USA, Canada and Australia. International orders typically arrive within 5–10 working days."
      }
    }
  ]
}
</script>

Rules that decide whether it works

1. The Q&A must be visible on the page. Schema describing content that isn’t rendered is treated as spam by search engines and as untrustworthy by answer engines. Markup mirrors the page; it never substitutes for it.
2. Answers must be complete in themselves. “See our delivery page” is not an answer. 2–4 sentences with the concrete numbers is ideal — that’s the exact size of passage engines lift.
3. Real questions only. Mine them from support tickets, sales emails and the “People also ask” boxes in your niche. Keyword-stuffed pseudo-questions dilute the good ones.
4. One FAQPage block per page, and only on pages that genuinely are (or contain) an FAQ.
5. Match text exactly. If the visible answer says £6.95 and the schema says £5.95, both get discarded.

Where to deploy it first

• Delivery, returns and warranty pages — the questions buyers ask a chatbot before committing.
• Product and category pages — 3–5 real pre-purchase questions each (the Magento AEO checklist covers ecommerce specifics).
• Service pages — pricing, timelines, process.
• One pillar FAQ page for brand-level questions: who you are, where you ship, how support works.

Beyond FAQPage

The same principle extends to HowTo (step-by-step content) and QAPage (forum-style single questions). Start with FAQPage — it covers the most ground for the least work. Then verify the whole structured-data layer with the free AI visibility check, which tests for entity and FAQ/HowTo markup alongside crawler access.

Next: How to get cited by ChatGPT and Perplexity — where FAQ schema fits in the full citation playbook.