Structured Data for AEO: FAQPage, QAPage and Speakable
What FAQPage, QAPage, HowTo and Speakable do, which one fits which page, and why you might still mark up questions when no rich result appears.
rabbitclip teamPublished: 6 min read
Short answer
Question-and-answer structured data is code that describes the questions and answers on a page in the schema.org vocabulary so that machines can read them; FAQPage, QAPage, HowTo and Speakable are the best-known types in this family. The code does not replace visible content, it labels it. According to Google's documentation, FAQ and HowTo rich results are no longer shown in search results, yet the markup can still be worth writing because it states plainly what a page covers, provided it matches the text on the screen exactly.
This article looks only at question-and-answer types, within the wider frame of answer engine optimisation (AEO). For the general logic of structured data, see our schema.org guide on this site, and for how to write the FAQ page itself, see our piece on FAQ pages and AI answers. We will not repeat either here.
One warning at the start: no markup guarantees that an answer engine will choose you as a source. Answer engines pick sources by their own criteria, and those criteria change over time. Markup is a small, cheap part of the job. The real work is the answer on the page.
Which types does question-and-answer structured data cover?
Four types come up most often. FAQPage is for questions and answers written by the site itself. QAPage is for pages built around one question that has several answers. HowTo describes a task done in steps. Speakable marks which parts of a page suit being read aloud by text-to-speech.
What the four have in common is that each labels a structure already present on the page. If the page has no questions and answers, the tag cannot create them. Markup only makes the machine's job easier; what persuades the reader is the answer itself.
Which type belongs on which page?
The rule is to look at what the page really is. The pairings below are enough for most business websites.
Google's QAPage documentation describes the type for pages focused on a single question where users can submit answers, and says not to use it for FAQ pages written by the site or for pages with several questions. So a five-question block under a service page is FAQPage, never QAPage.
- Several questions and answers written by the site: FAQPage.
- A forum or support page with one question and many user-submitted answers: QAPage.
- An operation explained in ordered steps: HowTo, though remember that Google no longer shows rich results for it.
- News-style pages with short passages suited to being read aloud: Speakable.
Why write it if no rich result appears?
In August 2023 Google announced that FAQ rich results would be limited to well-known government and health sites and that HowTo rich results would stop appearing. The change log in its documentation now states that the FAQ rich result is no longer shown in search results at all. So do not expect a visual box on the results page from this markup.
There are still sensible reasons to write it. Markup states plainly which question a page answers and with what answer. Search systems and AI products can read it, though from the outside we cannot know whether they use it. The honest frame is this: a harmless, low-cost layer that helps a page be understood when done correctly. It is not the main investment.
Rich result display varies by type and by site; check Google's documentation for the current position. A type that works today may be restricted tomorrow. That is why it is safer to base the decision on describing the page cleanly, not on a display feature.
How do you keep markup matched to visible content?
The golden rule: every question and answer in the markup must match the text the reader sees on the page. Adding a question the reader cannot see, or writing one answer in the code and another on screen, goes against Google's structured data guidelines and damages trust.
In practice the safest method is to generate the markup from the page text automatically. If you render the FAQ section from a data list, produce the code from the same list. Then one cannot be updated while the other is forgotten.
- Keep the question text identical to the page.
- Make the answer the full on-page answer, or a summary that clearly means the same.
- When you remove a question from the page, remove it from the code too.
- Do not mark up hidden text that the reader can never reach.
What mistakes are common in question-and-answer markup?
The most common mistake is putting QAPage on an FAQ page with a single author. By the documentation, that type is for pages where users can submit answers. The second is marking up questions written like advertising copy; a question the reader never really asks weakens both the page and the markup.
The third is pasting the same FAQ block on every page. If the same five questions repeat across forty pages, none of them serves the topic of that page. The fourth is skipping validation: broken JSON-LD fails silently and nobody notices.
- Using QAPage for a single-author FAQ.
- Adding to the code a question that is not on the page.
- Copying the same FAQ block to every page.
- Not checking with Search Console and validators after publishing.
When is question-and-answer markup unnecessary?
It is unnecessary if your page has no real question-and-answer section; do not invent questions for the sake of markup. On a small single-page business card site with no questions, the return on effort is low as well. Writing the answer itself, shaping headings as questions and making the first sentence a direct answer does more good.
When you build your markup, our schema generator can help, but do not publish its output without comparing it with the text on your page. If you want to choose together which pages are worth the effort, a discovery call with rabbitclip is a calm place to start.
Question-and-answer markup is a cheap, harmless layer that tells answer engines how a page is built; it promises no rich result and does not guarantee you will be chosen as a source. Pick the type according to the real structure of the page, keep it matched to the visible text, and put most of your effort into the quality of the answer. If you would like to judge together which of your pages deserve this markup, we are happy to arrange a calm discovery call with rabbitclip.
FAQ
Does FAQ schema still produce a rich result?
According to Google's documentation, the FAQ rich result is no longer shown in search results, and in August 2023 it had already been limited to well-known government and health sites. Check Google's documentation for the current position.
What is the difference between FAQPage and QAPage?
FAQPage is for several questions and answers written by the site itself. QAPage is for pages focused on a single question where users can submit answers; it is not used on FAQ pages.
Does every business need Speakable markup?
No. Google's documentation describes the feature as beta and focused on news content and read-aloud use. For most business websites it is not a priority.
Can I mark up a question that is not visible on the page?
No. The questions and answers in the markup must match the text the reader sees on the page. Adding content that is not shown goes against structured data guidelines and damages trust.
If I add markup, will I appear in answer engines?
There is no guarantee. Answer engines choose sources by their own criteria. Markup is a small layer that helps a page be understood; the quality of the answer on the page decides the outcome.
Sources
The specific facts in this article rest on these official pages; check them for the current position.
