QAPage Schema

What Is QAPage Schema?

QAPage is a Schema.org structured data type built for one specific job: marking up a page dedicated to answering a single question. It's easy to confuse with FAQPage schema, and the two do look similar in JSON-LD, but they're meant for different page shapes and search engines treat them differently.

FAQPage marks up a collection of question-answer pairs living on one page — a service page's FAQ section, or a dedicated FAQ hub with twenty questions stacked on top of each other. QAPage marks up a page that exists to answer exactly one question, the way a knowledge-base article or a glossary entry like this one does.

The markup itself

{
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "What is GBP AI optimization?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "GBP AI optimization is the practice of..."
    },
    "suggestedAnswer": [
      {"@type": "Answer", "text": "An alternative perspective..."}
    ]
  }
}

The structure mirrors a forum thread more than a document: one Question, one acceptedAnswer, and optionally one or more suggestedAnswer entries representing alternative or community-style answers. Most single-purpose glossary or knowledge-base pages only need the acceptedAnswer field — the suggestedAnswer array matters more for genuine Q&A forums like Stack Overflow or Quora, where multiple answers coexist.

Choosing QAPage over FAQPage

Use FAQPage when a page contains several distinct FAQ pairs — a service page's FAQ block, a product page's common-questions section, a standalone FAQ hub. Use QAPage when the entire page exists to answer one specific question and nothing else, the way a page titled "What Is Share of AI Voice?" does, or the way this page itself does.

Angryturtle's dedicated Q&A pages, the individual question-answer pages that make up its knowledge base, use QAPage rather than FAQPage for exactly this reason — each one is built around a single question, not a set of them. Getting this choice wrong doesn't break the page, but it does send a slightly muddled signal about the page's actual structure, and structured data that doesn't match the content it describes is the kind of thing that erodes trust with the systems reading it over time.

Why it matters for AEO

AI engines and AI Overviews are built to extract a clean, direct answer and attribute it to a source. QAPage schema hands them exactly that: one question, one clearly marked accepted answer, with no ambiguity about which text on the page is the actual answer versus supporting context. A page without any schema forces the AI system to infer the question-answer structure from the prose itself, which works, but less reliably than an explicit declaration does.

This is part of why single-question pages built for AEO purposes are usually worth marking up with QAPage even when the page also happens to rank fine in traditional search without it — the schema is aimed at a different reader, an AI system parsing structured data rather than a person scanning a rendered page.

A common implementation mistake

Some teams mark up every FAQ-style page with FAQPage by default, including pages that are really single-question pages wearing an FAQ template. The reverse mistake also happens — cramming several distinct questions into one QAPage's mainEntity, when Schema.org's QAPage type expects exactly one question per page. If a page genuinely covers three separate questions, it's an FAQPage candidate, not three QAPages stacked awkwardly into one.

India context

For Indian local businesses building out AEO content — individual pages answering things like "how much does teeth whitening cost in Mumbai" or "is same-day GBP verification possible in India" — QAPage schema is the correct default. These pages tend to be narrow by design, answering one query precisely rather than surveying a topic, which is exactly the shape QAPage was built for.

Related terms: FAQPage schema → · Structured data → · Answer capsule → · Schema.org → · JSON-LD → · Answer engine optimization →

AEO Services → | Structured Data & Schema → | Generative Engine Optimization →