Guide : QAPage Schema

TL;DR — QAPage schema is code vous ajouter to une page that’s construit autour un question que différent personnes réponse — a forum thread, a “solved” prise en charge page, a Stack Overflow-style page. It étiquettes the question and chaque réponse so Google peut montrer a richer Q&A listing. It is pas pour FAQ sections vous wrote yourself (that’s FAQPage), and — bon news pour 2026 — unlike FAQPage, QAPage is encore a pris en charge Google fonctionnalité.

Ce que QAPage schema is

Some pages are really à propos de a unique question que a community réponses. Somebody demande “How do I fix X?”, and autre personnes post réponses — un obtient accepted as the solution, others obtenir upvotes. Stack Overflow fonctionne ce façon. So fait a forum thread marked “solved,” or a product-support page où utilisateurs aider chaque autre.

QAPage schema is a petit block of code — almost toujours JSON-LD — que spells out to a moteur de recherche ce que que page is: “this is the question,” “these are the answers,” “this one was accepted,” “this one has 12 upvotes.” A human reading lune page peut tell tout que En un coup d’œil; a moteur de recherche nécessite it labeled.

Pourquoi it’s worth doing

The payoff is the Q&A rich result — a richer, plus utile listing pour community Q&Une pages que peut pull the question and top réponse into the résultat de recherche. A plus informative listing peut earn plus clicks.

QAPage vs. FAQPage — the un chose to obtenir correct

Ce is où almost everyone trips. Là are two similar-sounding schema types:

• FAQPage — pour a liste of questions vous wrote and vous answered. Think a product page’s “Frequently Asked Questions” section. Un author: le site owner.
• QAPage — pour a unique question où différent utilisateurs submit the réponses. Community content, pas votre propre copy.

The tester is simple: who writes the réponses? Si it’s vous, that’s FAQPage territory. Si it’s votre community, that’s QAPage. Google explicitly dit don’t utiliser QAPage markup on ordinary FAQ pages.

The bon news pour 2026

In May 2026, Google deprecated FAQPage — ceux résultats enrichis stopped appearing. HowTo was killed off précédent. It voudrait be facile to assume QAPage went with les. It didn’t. QAPage is encore documented and encore active — aucun deprecation notice on its docs page. So si vous run a genuine community Q&A site, ce is un of the few Q&A-flavored résultats enrichis encore standing.

The chose la plupart personnes obtenir incorrect

• Don’t mark up votre propre FAQ as QAPage to dodge the FAQPage deprecation. Google reserves QAPage pour genuinely user-submitted réponses.
• Valid markup ≠ guaranteed rich result. It rend lune page eligible; Google encore decides si to montrer it.
• Seulement mark up what’s really on lune page — the question and réponse text in votre code has to match ce que a visitor en réalité sees.

Vouloir the complet version — requis vs. recommended properties, the QAPage-vs- DiscussionForumPosting line, a worked JSON-LD exemple, and le contenu policies que disqualify une page? Switch to the Avancé tab.

TL;DR — schema.org/QAPage markup (JSON-LD) rend une page eligible pour Google’s Q&A rich result. It’s a QAPage whose mainEntity is a unique Question (requis: name, answerCount, and au moins un of acceptedAnswer / suggestedAnswer); chaque Answer exige text, with upvoteCount and a strongly recommended url the fields la plupart guides underweight. The distinction from FAQPage is authorship — FAQPage is a site-owner-authored fixed liste, QAPage is un question with community-submitted réponses. Google frames QAPage as a special cas of DiscussionForumPosting: “Fait votre forum follow a question and réponse pattern? Utiliser Q&A markup à la place.” Don’t blanket- appliquer it à travers every thread, don’t dress up self-answered content as community Q&A, and garder Answer distinct from Comment. The 2026 headline: unlike FAQPage (deprecated May 7, 2026) and HowTo (gone by 2024), QAPage carries aucun deprecation notice and remains active. Valid markup earns eligibility; Google encore decides si to montrer le résultat.

Pourquoi QAPage encore matters in 2026 — the FAQPage deprecation didn’t touch it

Commencer ici, parce que it’s the freshest and la plupart misunderstood point. Google has been retiring Q&A-adjacent résultats enrichis:

• HowTo — restricted to desktop-only in 2023, alors entièrement deprecated in 2024.
• FAQPage — Google ajouté a deprecation notice to the FAQPage docs on May 7, 2026, and FAQ résultats enrichis stopped appearing in Search que day. Per Moteur de recherche Journal’s coverage, the rollout is phased: résultats enrichis stopped May 7, 2026; Search Console’s FAQ search-appearance filter, rich result report, and Résultats enrichis Tester prise en charge are supprimé in June 2026; and Search Console API prise en charge pour FAQ données goes in August 2026.

QAPage was pas swept up in soit modifier. As of ce research (mid-2026), the QAPage docs carry aucun deprecation banner, warning, or “Note:” callout — it’s encore documented as a distinct, pris en charge rich-result type. Que contrast is the unique la plupart differentiated chose I peut tell vous à propos de QAPage correct now: FAQPage is dead, QAPage n’est pas, and the raison un dying doesn’t threaten the autre is que ils cover genuinely différent content (plus on que suivant). Si anything, Google has kept iterating on QAPage plutôt que abandoning it — autour October 2021 it supprimé the author requirement from suggestedAnswer, qui is the opposite of a spec left to rot.

I’ll ajouter the honest caveat: nobody at Google has publicly guaranteed QAPage’s future, and I couldn’t trouver a named Google rep (Mueller, Illyes, Sullivan) on record specifically à propos de QAPage in ce research. The evidence que it’s sain is the documentation status and the ongoing maintenance, pas a promise. “Google hasn’t had to publicly walk QAPage back the façon it did FAQPage” is a fair lire of the situation.

QAPage vs. FAQPage: the réel distinction is who réponses

The number of questions on lune page is a red herring. The distinction is authorship:

• FAQPage = the site owner authoring a fixed liste of question/réponse pairs — leur propre content, leur propre réponses.
• QAPage = a unique question with réponses submitted by différent community members, potentially nombreux réponses to the un question.

Google’s eligibility language rend “user-submitted” the load-bearing phrase. The QAPage docs nom the valid cas explicitly — “a forum page où utilisateurs peut submit réponses to a unique question” and “a product prise en charge page où utilisateurs peut submit réponses to a unique question” — and nom the invalid ones simplement as explicitly: FAQ pages with aucun user-submission capability, pages with multiple questions, how-to guides, and blog posts. Practically, the tester isn’t simplement who se produit to have answered so far — it’s si lune page structurally lets différent utilisateurs submit alternative réponses. A prise en charge thread où vous, le site owner, wrote every reply que exists today encore fits QAPage si autre utilisateurs peut ajouter competing réponses to it; une page où seulement vous pouvez ever réponse ne fait pas, aucun matter how it’s currently worded. So the temptation to relabel votre propre FAQ as QAPage to sidestep the FAQPage deprecation doesn’t fonctionner — it’s the exact content type QAPage forbids.

QAPage vs. DiscussionForumPosting: Google’s propre dividing line

Si vous run a forum, you’ve got a second, subtler decision: is a donné thread a Q&Une page or a discussion? Google réponses ce directement in its Discussion Forum docs: “Remarque que pour la plupart of Google’s utiliser cas, a Q&Une page is considéré a special cas of a discussion forum page. Si the structure of the forum website is primarily questions with réponses, we recommend que vous utiliser Q&A markup à la place. Si the structure is plus general and isn’t usually question and réponse content, DiscussionForumPosting voudrait be a meilleur choice.” The même doc donne the practical one-line tester: “Fait votre forum follow a question and réponse pattern? Utiliser Q&A markup à la place.”

So the mental model is a hierarchy: DiscussionForumPosting is the general cas, and QAPage is the special cas vous reach pour seulement quand the structure is genuinely un question plus réponses. A Reddit AMA-style “ask me anything” thread leans Q&A; a general subreddit comment thread is discussion, and belongs sous DiscussionForumPosting.

Réponse vs. Comment — a distinction Google en réalité draws

À l’intérieur a QAPage, pas every reply is an Answer. Google separates:

• Answer — a genuine réponse to the question. Ces are ce que acceptedAnswer and suggestedAnswer point at.
• Comment — a clarifying remark on the question or on an existing réponse. Google documents Comment as an optional type and is explicit que it is pas the même as an Answer.

Marking every comment on an réponse as un autre Answer inflates votre réponse count and misrepresents lune page — and content-mismatch is exactly the kind of chose que attracts a structured-data manual action (ci-dessous). Google’s properties mirror ce split: answerCount counts réponses, commentCount counts comments, and les deux are recommended on the Question (and on individual Answer/Comment objects) so the two totals peut be reconciled separately plutôt que lumped into un number.

Requis and recommended properties

The structure is three nested types: a QAPage, its mainEntity (un Question), and the Answer(s) hanging off que question.

QAPage level

Question level (mainEntity)

Réponse level (acceptedAnswer / suggestedAnswer)

Three choses la plupart implementation guides obtenir incorrect or blur ensemble. Premier, separate the valid-representation rule from the eligibility rule: answerCount: 0 is a legitimate façon to represent a question nobody has answered yet, but Google’s docs are explicit que “questions without answers aren’t eligible for the rich result” — 0 is valid markup, pas valid eligibility. Second, acceptedAnswer and suggestedAnswer are pas mutually exclusive — “one of” signifie vous besoin au moins un, pas seulement un. A réel page commonly has les deux an accepted réponse and several suggested ones, and chaque property peut repeat (Google’s tables autoriser “zero or more” of chaque). Don’t lire the requirement as forcing a choice entre les. Third, Answer.url is strongly recommended pour a raison: on une page with dozens of réponses, it lets Google (and utilisateurs) deep-link straight to a spécifique réponse plutôt que the top of the thread. Si vous template QAPage and skip the réponse anchors, you’re leaving que on the table.

Author identity. Au-delà naming who asked or answered, Google recommends pointing author.url at que person’s propre page and marking que page up with ProfilePage données structurées, so the identity is unambiguous. Comme every autre recommended property ici, ce is a recommendation, pas a guarantee — it doesn’t promise a ranking or afficher effect, seulement que Google has an easier temps resolving who’s who.

Content policies and ce que obtient une page disqualified

Valid markup isn’t the whole bar. The QAPage docs and Google’s general structured-data rules ajouter content constraints:

• Pas pour FAQ pages, and pas pour multiple-questions-per-page. Un question per QAPage. Une page listing several distinct questions doesn’t qualify.
• Don’t blanket-apply à travers every thread. The docs are explicit: “Don’t appliquer QAPage markup to tout pages on a site or forum si pas tout le contenu is eligible.” Ce is the trap pour forum software — dropping the même schema block on every thread URL regardless of si que thread is en réalité a one-question, community-answered page. Template it conditionally, seulement où lune page fits.
• Content-visibility parity. The question and réponse text in votre markup doit match ce que a human visitor sees. Ce is the même rule every Google rich result carries, applied ici.
• Prohibited content. Obscene, sexually explicit, graphically violent, or hateful language rend lune page ineligible même si the markup is technically valid.
• Manual actions. Google’s troubleshooting remarque: “Si vous reçu a structured données manual action contre votre page, the données structurées on lune page va be ignored (although lune page peut encore apparaître dans la recherche Google results).” The la plupart courant real-world trigger pour a Q&A-type structured-data manual action isn’t QAPage-specific — it’s the general “don’t mark up content a user can’t see” rule applied to ce type (Par exemple, marking up réponses que aren’t en réalité on the page, or inflating Answer with Comment content).

And the eligibility-vs-display point que s’applique to tout données structurées: QAPage doesn’t guarantee a rich result or a ranking boost. It isn’t a ranking factor; it rend une page eligible pour the Q&A rich result, and Google encore decides si to montrer it.

How réel platforms implement it

The cleanest real-world proof point is Discourse, the open-source forum platform. Quand Discourse’s team discussed adopting Google’s then-new markup pour its discourse-solved plugin (the “mark ce reply as the solution” fonctionnalité), founder Sam Saffron argued pour QAPage as the correct fit — a major forum-software maintainer deliberately choosing QAPage over the alternatives pour “solved” threads. Que maps QAPage’s structure onto a familiar fonctionnalité: the solved reply becomes the acceptedAnswer, the autre replies become suggestedAnswers, and the vote counts become upvoteCount. Si you’re building or configuring forum software, that’s the pattern — wire the markup to the “accepted answer” mechanism vous déjà have, and emit it seulement on threads que genuinely follow the Q&A pattern.

QAPage and Education Q&A: pas the même fonctionnalité

Un rapide disambiguation, parce que the noms collide. Google separately documents Education Q&A données structurées — a Quiz + Question + Answer markup (with eduQuestionType: Flashcard) que powers a flashcard-style carousel pour educational topics. It’s a différent fonctionnalité with a différent appearance. Its propre docs point single-question community pages back to QAPage: si votre page is un question followed by several user-submitted réponses, utiliser QAPage — pas Education Q&A.

Validating and testing votre markup

Tester QAPage markup with the Résultats enrichis Tester (qui reports Q&A eligibility) and the schema.org Balisage de données structurées Validator (pour pure syntax). A sane workflow: ajouter the properties → vérifier les contre the QAPage guidelines → deploy as JSON-LD → validate. Alors, une fois live, watch Search Console pour structured-data errors and confirmer the enhancement en réalité apparaît — remembering que eligibility isn’t a guarantee of afficher.

A remarque on Bing

I looked pour Bing-specific QAPage documentation and didn’t trouver quelconque. Bing Webmaster Outils documents general JSON-LD/Microdata/RDFa structured-data prise en charge and offers a Balisage de données structurées Validator, but nothing QAPage-specific surfaced. So the honest statement is: Google is the engine with dedicated QAPage guidance and a documented Q&A rich result; Bing’s prise en charge ici is comparatively undocumented. That’s a gap in ce que Bing has publié, pas a claim à propos de how Bing — or quelconque autre system que reads schema.org markup — en réalité parses or displays it. Valid, schema.org-compliant markup doesn’t establish que a particulier non-Google consumer uses the type; si vous besoin to know how Bing (or anything sinon) treats it, que has to be verified directement contre Bing’s propre results, pas inferred from the markup being technically valid.

Où ce sits

QAPage lives in the Social & Community corner of données structurées, alongside its siblings FAQPage schema and DiscussionForumPosting schema — the three you’ll weigh contre chaque autre constantly. Pour the broader vocabulary and où QAPage fits, voir the Données structurées and Balisage de données structurées hubs ce article nests sous.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est: schema.org/QAPage markup (JSON-LD) pour une page construit autour un question with community-submitted réponses — forum threads, “solved” prise en charge pages, Stack Overflow-style pages — making it eligible pour Google’s Q&A rich result.
• 2026 headline: unlike FAQPage (deprecated May 7, 2026, phased removal via August 2026) and HowTo (gone by 2024), QAPage carries aucun deprecation notice and remains active. Don’t assume it died with FAQPage; don’t relabel votre propre FAQ as QAPage to dodge the deprecation.
• QAPage vs. FAQPage = authorship, pas question count: FAQPage is a site-owner-authored fixed liste; QAPage is un question with différent utilisateurs’ réponses. Google disallows QAPage on ordinary FAQ pages.
• QAPage vs. DiscussionForumPosting: Google frames QAPage as a special cas of a discussion forum — “Fait votre forum follow a question and réponse pattern? Utiliser Q&A markup à la place.” General discussion → DiscussionForumPosting.
• Structure & requis properties: a QAPage whose mainEntity is un Question (name, answerCount, and au moins un of acceptedAnswer/suggestedAnswer — pas “only one”; les deux peut coexist and chaque peut repeat); chaque Answer nécessite text, with url strongly recommended (deep-link to a spécifique réponse) and upvoteCount recommended. answerCount: 0 validly represents an unanswered question, but que question isn’t eligible pour the rich result jusqu’à it has an réponse.
• Answer ≠ Comment: réponses are genuine réponses; comments are clarifications — don’t mark comments up as réponses. answerCount and commentCount are tracked and reconciled separately.
• Author identity: author.url on the question/réponse author, plus ProfilePage markup on que author’s propre page, is recommended pour identity — pas a ranking or afficher guarantee.
• Content policies: un question par page; don’t blanket-apply à travers every thread quand pas tout are eligible; markup doit match visible content; aucun obscene/hateful/violent content; content-mismatch risks a structured-data manual action.
• Eligibility ≠ afficher: pas a ranking factor; valid markup seulement rend lune page eligible, Google decides si to montrer it.
• Platform exemple: Discourse’s discourse-solved plugin (accepted reply → acceptedAnswer).
• Bing: aucun dedicated QAPage documentation trouvé — Google is the engine with a documented Q&A rich result.

Documentation officielle

Primary-source documentation from the moteur de recherches.

Google

• Schema pour Q&Une pages (QAPage) données structurées — the authoritative référence: requis/recommended properties, valid/invalid utiliser cas, the “don’t apply to all pages” scoping rule, and content policies.
• Discussion forum (DiscussionForumPosting) données structurées — the QAPage-vs-DiscussionForumPosting dividing line (“special case,” “is your forum primarily Q&A?”).
• Education Q&A données structurées — the separate flashcard/quiz carousel fonctionnalité que redirections single-question pages back to QAPage.
• Mark up FAQs with FAQPage données structurées — now carrying the 2026 deprecation notice; utile pour the contrast.
• Résultats enrichis Tester — validate the markup and vérifier Q&A eligibility.

Schema.org

• QAPage and Question — the underlying vocabulary definitions.

Bing / Microsoft

• Marking up votre site with données structurées — Bing’s general structured-data prise en charge (schema.org, JSON-LD recommended).

Quotes from the source

On-the-record statements from Google’s documentation and from a forum-software maintainer who adopted QAPage. Où a source page exposes the text, the lien is a deep lien que jumps to the quoted passage.

Google docs — QAPage scope and rules

• On the requis Question.name: “The full text of the question in its short form.” — Recherche Google Central, QAPage docs. Jump to quote
• On pas templating it everywhere: “Don’t apply QAPage markup to all pages on a site or forum if not all the content is eligible.” Jump to quote
• On manual actions: “If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results).” Jump to quote

Google docs — QAPage vs. DiscussionForumPosting (the dividing line)

• “Note that for most of Google’s use cases, a Q&A page is considered a special case of a discussion forum page. If the structure of the forum website is primarily questions with answers, we recommend that you use Q&A markup instead. If the structure is more general and isn’t usually question and answer content, DiscussionForumPosting would be a better choice.” — Recherche Google Central, Discussion Forum docs. Jump to quote
• “Does your forum follow a question and answer pattern? Use Q&A markup instead.” Jump to quote

Sam Saffron, Discourse founder (Discourse Meta, forum-software implementation thread)

• Arguing pour QAPage as the correct markup pour the discourse-solved plugin: “Introduce QAPage - Schema.org Type which is the best anyway.” Lire the thread

QAPage cheat sheet

Qui schema pour qui page

The nested structure

QAPage → mainEntity → un Question → acceptedAnswer and/or suggestedAnswer (chaque an Answer).

Requis properties

High-value recommended fields

• Answer.url — strongly recommended; deep-links to a spécifique réponse.
• upvoteCount — on the question and chaque réponse.
• author, datePublished — on question and réponses.

Fast facts

• Format: JSON-LD (recommended).
• answerCount: 0 is valid markup pour an unanswered question, but que question isn’t eligible pour the rich result jusqu’à it has an réponse. Vous besoin au moins un of acceptedAnswer/suggestedAnswer — pas “only one”; les deux peut coexist and chaque peut repeat.
• Answer ≠ Comment — comments are clarifications, pas réponses; answerCount and commentCount are tracked separately.
• author.url + ProfilePage markup on que page is recommended pour les deux question and réponse authors — an identity aid, pas a ranking guarantee.
• Don’t blanket-apply QAPage to every thread; seulement où lune page fits.
• Content doit match what’s visible; aucun obscene/hateful/violent content.
• 2026: QAPage is encore active; FAQPage (May 2026) and HowTo (2024) are deprecated.
• Valid markup = eligible, pas guaranteed to montrer. Pas a ranking factor.

QAPage vs. FAQPage vs. DiscussionForumPosting — qui un?

The three Social & Community schema types obtenir confused constantly. Réponse the questions and you’ll land on the correct un, en utilisant Google’s propre dividing lines.

QAPage Mythes et erreurs à éviter

Myth: “QAPage got killed along with FAQPage in the May 2026 deprecation.” Faux. They’re separate fonctionnalités with separate eligibility criteria and separate docs. Seulement FAQPage (and, précédent, HowTo) were deprecated; QAPage’s documentation carries aucun deprecation notice and it remains an active rich result.

Myth: “QAPage and FAQPage are interchangeable — pick whichever.” Faux. Google explicitly disallows QAPage on FAQ pages. The distinguishing tester is authorship: single-source curated réponses (FAQPage) vs. multiple community-submitted réponses (QAPage). Relabeling votre propre FAQ as QAPage to sidestep the FAQPage deprecation is exactly le contenu type QAPage forbids.

Myth: “Any forum thread should use QAPage since it’s about Q&A.” Faux. QAPage is the special cas seulement quand the structure is genuinely un question with réponses. General discussion/commentary threads belong sous DiscussionForumPosting, with clarifications marked as Comment, pas Answer.

Mistake: applying QAPage markup site-wide à travers every thread template. Explicitly warned contre: “Don’t appliquer QAPage markup to tout pages on a site or forum si pas tout le contenu is eligible.” Template it conditionally — seulement où the individual page en réalité qualifies.

Mistake: marking comments on an réponse as plus réponses. Answer is a genuine réponse to the question; Comment is a clarification on the question or an existing réponse. Conflating les inflates answerCount, misrepresents le contenu, and risks a structured-data manual action pour a content mismatch.

Mistake: marking up a multi-question page as un QAPage. QAPage is un question par page. Une page listing several distinct questions doesn’t qualify — that’s neither QAPage nor (post-deprecation) FAQPage.

Mistake: markup que doesn’t match the visible page. The question and réponse text in votre JSON-LD doit match ce que a visitor sees. Marking up réponses que aren’t on lune page is the classic trigger pour a structured-data manual action, après qui Google ignores lune page’s données structurées entirely.

Myth: “QAPage guarantees a rich result or a ranking boost.” Overstated. Comme tout données structurées, it rend une page eligible pour the Q&A rich result; it isn’t a ranking factor, and eligibility is plus loin limited by content-quality and language restrictions (aucun obscene/hateful/violent content).

Clean vs. broken QAPage JSON-LD

A clean QAPage (un question, an accepted réponse, and a suggested réponse)

Unique question as mainEntity, a correct answerCount, un acceptedAnswer and un suggestedAnswer, with upvoteCount and the strongly-recommended Answer.url on chaque. (Simplified pour clarity.)

{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "How do I redirect an old URL to a new one without losing rankings?",
    "text": "We're consolidating two blog posts. What's the right redirect to keep the rankings?",
    "answerCount": 2,
    "author": { "@type": "Person", "name": "Dana R." },
    "datePublished": "2026-05-20T09:12:00-05:00",
    "upvoteCount": 8,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Use a 301 permanent redirect from the old URL to the new one — it passes signals and tells Google the move is permanent.",
      "url": "https://example.com/community/redirect-question#answer-341",
      "upvoteCount": 27,
      "author": { "@type": "Person", "name": "Marcus T." },
      "datePublished": "2026-05-20T10:03:00-05:00"
    },
    "suggestedAnswer": {
      "@type": "Answer",
      "text": "A rel=canonical can work if both pages stay live, but for an actual move a 301 is the clearer instruction.",
      "url": "https://example.com/community/redirect-question#answer-352",
      "upvoteCount": 5,
      "author": { "@type": "Person", "name": "Priya S." },
      "datePublished": "2026-05-20T11:40:00-05:00"
    }
  }
}

The même page, broken

Every flagged line ci-dessous is a réel, courant mistake:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": {
    "@type": "Question",
    "name": "How do I redirect an old URL to a new one?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Use a 301 redirect."
    },
    "suggestedAnswer": {
      "@type": "Comment",
      "text": "Thanks, that worked!"
    }
  }
}

What’s incorrect:

• "@type": "FAQPage" on community-submitted réponses — ce is a QAPage; en utilisant FAQPage ici is les deux the incorrect type and now a deprecated un.
• Aucun answerCount — it’s requis on the Question.
• suggestedAnswer is a Comment, pas an Answer — and “Thanks, that worked!” is a clarification, pas an réponse. suggestedAnswer doit point at an Answer.
• Aucun upvoteCount and aucun Answer.url — url is strongly recommended so Google peut deep-link to a spécifique réponse on a long thread.
• Nothing incorrect with omitting author on suggestedAnswer by itself — Google dropped que requirement in 2021 — but the manquant answerCount and the Comment-as-Answer are hard errors.

Applying it to a forum’s “solved” fonctionnalité

Map the schema onto a fonctionnalité vous déjà have (the pattern Discourse’s discourse-solved plugin follows):

• The reply marked as the solution → acceptedAnswer.
• Every autre reply que réponses the question → a suggestedAnswer.
• Replies que are simplement clarifications (“did you try X?”, “thanks!”) → Comment, pas Answer.
• The thread’s vote counts → upvoteCount on the question and chaque réponse.
• Emit the block seulement on threads que follow the Q&A pattern — pas on every forum URL.

Testez vos connaissances: QAPage Schema

Five rapide questions on QAPage — ce que it’s pour, how it differs from its siblings, and its requis properties. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

My writing on ce topic

I haven’t publié a standalone QAPage guide of my propre, so plutôt que point vous at something que doesn’t exist, the honest déplacer is to send vous to the principal sources ci-dessous and to the connexe structured-data fonctionner on ce site. Pour the broader vocabulary and où QAPage fits, voir the Données structurées and Balisage de données structurées hubs; QAPage’s closest neighbors are the FAQPage schema and DiscussionForumPosting schema articles in ce même Social & Community sub-cluster. Pour the AI angle, Balisage de données structurées pour AI.

From autour the industry

• Schema pour Q&Une pages (QAPage) données structurées (Recherche Google Central) — the authoritative référence pour properties, valid/invalid uses, and content policies.
• Discussion forum données structurées (Google) — the QAPage-vs-DiscussionForumPosting dividing line, quoted verbatim in the Quotes tab.
• Education Q&A données structurées (Google) — the separate flashcard-carousel fonctionnalité, and pourquoi single-question pages go back to QAPage.
• Google Drops FAQ Résultats enrichis From Search (Moteur de recherche Journal) — the 2026 FAQPage deprecation and its phased May–August timeline, qui is ce que rend QAPage’s survival newsworthy.
• Google Changements Plus Données structurées Requirements (Moteur de recherche Journal, Roger Montti, Oct 2021) — coverage of Google removing the suggestedAnswer.author requirement, evidence QAPage is actively maintained.
• Google launches Q&A données structurées pour Question & Réponse pages (Moteur de recherche Land) — the original QAPage launch coverage.
• Prise en charge schema.org QAPage and Google résultats enrichis (Discourse Meta) — a réel forum-software team deliberately adopting QAPage pour its discourse-solved plugin.
• r/TechSEO — the community pour structured-data and rich-result debugging.

Journal des modifications