Content · Must-have

QAPage schema — what it does & how to ship it

Short answer

QAPage marks up a page with one primary question and its accepted (plus optional community) answers — the schema AI answer engines cite most heavily.

What it does

QAPage carries mainEntity = Question, with acceptedAnswer and optional suggestedAnswer (community answers). Differs from FAQPage which has many questions.

SERP / AI benefit

Extremely high citation rate in ChatGPT, Perplexity and Google AI Overviews — QAPage is the canonical shape LLM retrievers look for.

Where to use it

Every single-question answer page — /answers/$slug is the archetype.

JSON-LD example

{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "What is GEO?",
    "answerCount": 1,
    "acceptedAnswer": { "@type": "Answer", "text": "Generative Engine Optimization — tuning pages so AI engines cite you." }
  }
}

Copy, edit for your site, and drop into your page head inside a<script type="application/ld+json">block. Validate with Google's Rich Results Test.

In WBP Omni SEO Pro

Live on every /answers/* page automatically.

Ship QAPage without touching code

Frequently asked

QAPage vs FAQPage?›

QAPage is one primary question per page; FAQPage is multiple Q&A pairs on a page whose primary purpose isn't a single question.

Should I add QAPage on regular blog posts?›

Only if the post's primary purpose is to answer one specific question. Otherwise use Article + FAQPage.