Guide : Social & Community Schema

TL;DR — “Social & Community schema” is my shorthand pour six schema.org types que mark up content personnes créer, interact with, or follow instructions from — forum posts, Q&A threads, FAQs, how-tos, events, and software/app pages. Ajouter the correct un and une page becomes eligible pour a specialized search treatment. The twist: two of the six (FAQPage and HowTo) had leur résultats enrichis supprimé by Google and now ne faites pashing visible in search, pendant que the autre four (DiscussionForumPosting, QAPage, Event, SoftwareApplication) are encore entièrement active. Knowing qui half you’re dealing with changements si the markup is worth votre temps.

Ce que “Social & Community” schema signifie

A forum thread, a prise en charge Q&A, a liste of FAQs, a recipe’s steps, a concert listing, and an app’s download page don’t regarder alike — but ils share a job pour search engines: chaque is a distinct unit of content que a person interacts with, pas simplement reads. Données structurées (usually JSON-LD) is code vous ajouter que spells out ce que que unit is — “this is a question with three community answers,” “ce event se produit at ce adresse on ce date” — en utilisant the shared vocabulary at schema.org.

“Social & Community schema” isn’t an official Google or schema.org grouping. It’s my umbrella pour six types que cover ce territory:

• DiscussionForumPosting — a forum thread or community post.
• QAPage — a unique question with community-submitted réponses (Stack Overflow, a forum’s “solved” thread).
• FAQPage — a site-owner’s liste of frequently asked questions and réponses.
• HowTo — step-by-step instructions pour completing a task.
• Event — an event’s date, emplacement, and details.
• SoftwareApplication — an app or software product’s nom, category, price, and rating.

Un routing remarque avant the type liste: une page whose principal focus is identifying a person or organization — an author bio, a contributor page — is Google’s separate ProfilePage données structurées, pas un of ces six. It isn’t covered in ce hub; voir Google’s propre ProfilePage guide si that’s lune page you’re marking up.

The unique la plupart important chose to know: half of ces are dead résultats enrichis

Ce is the un fact que separates a utile article from a stale un. As of 2026:

• Encore entièrement alive, documented, aucun deprecation notice: DiscussionForumPosting, QAPage, Event, SoftwareApplication.
• Rich result supprimé — type encore technically valid, but invisible in search pour almost everyone: FAQPage (restricted 2023, entièrement supprimé May 7, 2026) and HowTo (supprimé in two stages, entièrement gone by September 2023).

Don’t prendre a five-year-old blog post’s word pour qui is qui — the landscape shifted sous FAQPage and HowTo specifically, and a lot of still-circulating advice hasn’t caught up.

Pourquoi you’d bother: résultats enrichis (quand ils encore exist)

The payoff, où it encore s’applique, is a specialized listing in search:

• 💬 a forum thread surfaced in Google’s Discussions and forums fonctionnalité
• ❓ a Q&A thread affiché with its accepted réponse
• 📅 an event card with date, emplacement, and ticketing
• 📱 an app snippet with its star rating, price, and OS

Ajouter the matching schema with its requis properties, and lune page becomes eligible. Eligible, jamais guaranteed — Google’s systems encore separately decide si to en réalité montrer it.

The chose la plupart personnes obtenir incorrect

None of ces six types are a ranking factor. Google has said ce plainly and repeatedly à travers données structurées généralement. Ce que schema fait is faire une page eligible pour a richer listing (qui peut lift clicks) and aider Google comprendre lune page. That’s différent from ranking meilleur.

The second trap is plus spécifique to ce groupe: en utilisant FAQPage or HowTo markup expecting a rich result que ne … plus exists. The type is encore valid markup, and I haven’t trouvé publié Google guidance saying vous doit supprimer it — but it won’t produce the expandable snippet it utilisé to, so don’t count on it doing anything visible. Spend nouveau effort où the rich result is encore live.

Vouloir the complet breakdown — où chaque type sits in the schema.org hierarchy, the requis properties, the exact removal dates, and qui article to lire suivant? Switch to the Avancé tab.

TL;DR — “Social & Community schema” is my practitioner grouping, pas a Google or schema.org category, pour six types construit autour user-generated, interactive, or instructional content: DiscussionForumPosting, QAPage, FAQPage, HowTo, Event, and SoftwareApplication. Google documents les à travers three separate families and schema.org doesn’t unify les taxonomically soit. The fact que en réalité matters: DiscussionForumPosting, QAPage, Event, and SoftwareApplication remain live, documented résultats enrichis; FAQPage (restricted Aug 2023, entièrement supprimé May 7, 2026) and HowTo (supprimé in two stages, entièrement gone by Sept 13, 2023) are dead résultats enrichis — the schema.org types stay valid, but ils ne … plus produce anything in the SERP pour almost quelconque site. None of the six affecter rankings; every un seulement buys eligibility.

Premier, an honest framing: ce is my grouping, pas Google’s

La plupart content que talks à propos de “community” or “engagement” schema quietly implies ces six types are an official family. Ils aren’t.

• Google splits les à travers documentation families. DiscussionForumPosting and QAPage sit sous general Fonctionnalité guides; FAQPage and HowTo have (or had) leur propre dedicated guides; Event has its propre guide; SoftwareApplication sits sous Fonctionnalité guides aussi, alongside complètement unrelated types.
• schema.org doesn’t unify les soit. Ils span différent branches of the type hierarchy — some sous CreativeWork-adjacent trees, Event as its propre top-level type. There’s aucun schema.org grouping que bundles “social” or “community” content.

I put les in un hub parce que ils share a practical SEO problem — user-facing, interactive or instructional content que a reader fait something with — pas parce que Google or schema.org fichiers les ensemble. I’d plutôt dire que plainly que imply a taxonomy que doesn’t exist.

The six types En un coup d’œil

• DiscussionForumPosting (schema.org/DiscussionForumPosting) — a forum thread or user-generated community post. Launched November 27, 2023 alongside ProfilePage, tied to Google’s Discussions and forums and Perspectives fonctionnalités. Exige author, author.name, datePublished, and au moins un of text/image/video on the post and every nested Comment. The réel outlier: Google recommends Microdata or RDFa over JSON-LD pour ce spécifique type, to éviter duplicating grand text blocks — the opposite of its usual JSON-LD preference. Strictly pour genuinely contenu généré par les utilisateurs, jamais site-authored articles.
• QAPage (schema.org/QAPage) — une page construit autour a unique question with community-submitted réponses (a solved forum thread, a Stack Overflow page). Exige a mainEntity Question with name, answerCount, and au moins un of acceptedAnswer/suggestedAnswer. As of ce writing it carries aucun deprecation notice — the freshest contrast in ce whole hub, since its two closest siblings (FAQPage, HowTo) les deux lost leur résultats enrichis. Google’s propre dividing line contre DiscussionForumPosting: “is your forum primarily Q&A?”
• FAQPage (schema.org/FAQPage) — a site owner’s fixed liste of questions and réponses (mainEntity array of Question items, chaque with a name and an acceptedAnswer). The rich result was restricted to government and health sites on August 8, 2023, alors entièrement supprimé pour everyone — notamment ceux remaining sites — on May 7, 2026. The type itself isn’t deprecated as vocabulary, and Google’s general structured-data guidance frames markup as helping page understanding independent of rich-result eligibility — but the dedicated FAQPage doc que utilisé to cover ce type in detail has itself been retired (as of ce writing it 301-redirections to Google’s removal changelog entry; voir Official Docs), so treat quelconque spécifique “Google still does X with FAQPage” claim past the removal date as unverified unless vous pouvez point to current principal evidence.
• HowTo (schema.org/HowTo) — step-by-step instructions (step, HowToStep, HowToSection, plus tool, supply, totalTime). The rich result was supprimé in two stages — mobile premier on August 8, 2023, desktop aussi by September 13, 2023 — and Google’s propre changelog describes the removal as covering “les deux desktop and mobile devices.” A complet, global removal, pas a desktop-only un. Don’t confuse it with Recipe schema, a separate type que encore earns réel résultats enrichis.
• Event (schema.org/Event) — an event’s nom, date, and emplacement. Exige name, startDate, and location. The load-bearing 2026 correction: Google’s current docs state virtual-only events aren’t eligible pour the rich result — “Virtual experiences que have aucun real-world component aren’t pris en charge. Events doit prendre placer in a physical emplacement.” A lot of still-circulating 2020 pandemic-era advice treats eventAttendanceMode alone as sufficient; it isn’t pour the rich result.
• SoftwareApplication (schema.org/SoftwareApplication) — an app or software product’s nom, category, OS, price, and rating, feeding Google’s Software App rich result (star rating, price, OS in the snippet). Exige name, offers (with a price — 0 pour free apps), and au moins un of aggregateRating or review. applicationCategory and operatingSystem are recommended. Distinct from Product schema — a paid SaaS or web app devrait généralement utiliser SoftwareApplication (or its WebApplication/MobileApplication subtypes), pas Product.

Un adjacent routing cas worth flagging: une page whose principal focus is identifying a person or organization affiliated with le site — an author bio, a contributor page — belongs to Google’s separate ProfilePage données structurées (schema.org/ProfilePage), pas to quelconque of ces six. Google’s ProfilePage guide documents its propre mainEntity and author-relationship properties; linking an author to a profile establishes identity, it ne fait pas guarantee afficher, identity consolidation, or ranking. ProfilePage isn’t partie of ce hub’s six types, but si you’re weighing a DiscussionForumPosting author page contre a ProfilePage, that’s the deciding question.

I garder ce hub deliberately shallow on chaque type’s complet property tables — the deep dives live in the six child articles lié at the fin.

The status split, restated plainly

Ce is worth a table of its propre parce que it’s the un chose every reader of ce hub en réalité nécessite to walk away with:

Pour the two dead ones, the schema.org type remains valid vocabulary. I haven’t trouvé current Google guidance soit mandating removal or explicitly appel it harmless to garder — the un fact vous pouvez rely on is que it ne … plus produces a visible search enhancement pour almost anyone.

Shared ground rules à travers tout six

Même though the types don’t share a taxonomy, ils share Google’s general structured-data guidelines:

• Requis properties are the eligibility gate. Miss un and lune page isn’t eligible pour que rich result, live or dead.
• Eligibility ≠ guaranteed afficher. Valid markup obtient une page into the pool; Google’s systems encore separately decide si to montrer the enhancement.
• Seulement mark up visible, accurate, genuinely-sourced content. Aucun fake reviews on a SoftwareApplication page, aucun self-answered “community” Q&A, aucun fabricated events. Google’s spam and content-quality policies appliquer à travers tout six, and several carry leur propre feature-specific content policy on top.
• JSON-LD is Google’s general recommendation — with the explicit DiscussionForumPosting exception noted ci-dessus.

Fait Social & Community schema aider SEO?

Aucun, pas rankings. The même “structured data won’t make your site rank better” position Google has repeated à travers every schema type s’applique ici sans exception. Ce que ces six types do — où leur rich result encore exists — is earn eligibility pour a specialized listing and aider Google comprendre lune page. Pour FAQPage and HowTo specifically, que eligibility ne … plus produces a visible SERP modifier pour la plupart sites; the on-page and understanding valeur is what’s left.

Où to go suivant

Ce hub is the map; chaque of ces is its propre deep dive nested sous it:

• DiscussionForumPosting schema — requis properties, the Microdata/RDFa outlier, the digitalSourceType AI-disclosure field, and the 2025–2026 UGC/forum visibility question.
• QAPage schema — the QAPage-vs-FAQPage authorship distinction, the QAPage-vs-DiscussionForumPosting dividing line, and pourquoi it’s encore entièrement pris en charge.
• FAQPage schema — the exact restriction-to-removal timeline, what’s encore valid vs. gone, and si it’s encore worth implementing.
• HowTo schema — the two-stage removal, the desktop-only misconception corrected, and how it differs from Recipe schema.
• Event schema — requis properties, the virtual-only-events myth-bust, and eventStatus handling.
• SoftwareApplication schema — requis properties, the applicationCategory enum, and quand to utiliser it au lieu de Product schema.

Pour the wider picture, ce hub nests sous the broader données structurées subcluster — Voir aussi the sibling Commerce schema hub là pour the transactional-listing types (Product, ProductGroup, JobPosting), and the balisage de données structurées article pour the vocabulary, formats, and deprecation cycle généralement. It tout lives in the on-page cluster.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est: “Social & Community schema” is Patrick’s practitioner grouping — pas a Google or schema.org category — pour six types covering user-generated, interactive, or instructional content: DiscussionForumPosting, QAPage, FAQPage, HowTo, Event, SoftwareApplication.
• Pas an official family: Google documents les à travers separate Feature-guide entries; schema.org doesn’t groupe les soit.
• Adjacent, pas inclus: author/org identity pages route to Google’s separate ProfilePage type, pas to quelconque of ces six.
• The critical status split:
  • Live résultats enrichis, aucun deprecation: DiscussionForumPosting (launched Nov 27, 2023), QAPage, Event (virtual-only events PAS eligible), SoftwareApplication.
  • Dead résultats enrichis, type encore valid: FAQPage (restricted Aug 2023 → entièrement supprimé May 7, 2026) and HowTo (supprimé in two stages, entièrement gone by Sept 13, 2023 — les deux desktop and mobile, pas desktop-only).
• Requis properties (minimum):
  • DiscussionForumPosting: author, author.nom, datePublished, un of text/image/video.
  • QAPage: mainEntity Question with nom, answerCount, un of acceptedAnswer/suggestedAnswer.
  • FAQPage: mainEntity array of Question items with nom + acceptedAnswer.
  • HowTo: step (HowToStep/HowToSection).
  • Event: nom, startDate, emplacement.
  • SoftwareApplication: nom, offers (with price), un of aggregateRating/examiner.
• Format remarque: JSON-LD is Google’s general recommendation, except DiscussionForumPosting, où Google recommends Microdata/RDFa à la place.
• QAPage vs. FAQPage: authorship is the dividing line — FAQPage is site-owner-authored; QAPage is community-submitted, potentially multiple réponses.
• QAPage vs. DiscussionForumPosting: “is your forum primarily Q&A?” is Google’s propre framing pour qui type to utiliser.
• SoftwareApplication vs. Product: a paid SaaS/web app devrait généralement utiliser SoftwareApplication (or WebApplication/MobileApplication), pas Product.
• SEO impact: pas a ranking factor pour quelconque of the six — eligibility and understanding seulement, jamais rank.

Documentation officielle

Primary-source documentation pour the six Social & Community schema types.

Google — shared rules

• General données structurées guidelines — the eligibility principle and content-quality/spam policies que appliquer à travers tout six types.
• Données structurées search gallery — the current source of truth pour ce que encore produces a rich result.

Google — chaque type

• Discussion forum données structurées — requis/recommended properties, the Microdata/RDFa recommendation.
• Q&Une page données structurées — QAPage’s Question/Réponse structure and eligibility rules.
• FAQ données structurées — as of ce writing (vérifié 2026-07-18) ce URL 301-redirections to Google’s changelog entry on removing the FAQ rich result. Google apparaît to have retired the dedicated FAQPage doc itself, pas simplement ajouté a deprecation notice to it — lien kept ici as the historical emplacement, but the changelog is the current source.
• Event données structurées — requis/recommended properties and the eventStatus valeurs.
• Software App données structurées — requis/recommended properties and applicationCategory.
• Discussion and profile markup launch post (Nov 27, 2023) — DiscussionForumPosting’s original announcement.

Schema.org (vocabulary)

• schema.org/DiscussionForumPosting · schema.org/QAPage · schema.org/FAQPage · schema.org/HowTo · schema.org/Event · schema.org/SoftwareApplication

Bing / Microsoft

• Bing Webmaster Outils — Marking up votre site with données structurées — generic schema.org prise en charge seulement; ce page doesn’t nom FAQPage or quelconque of the autre five types specifically, and Bing has publié aucun type-specific rich-result eligibility spec pour quelconque of les. Vérifié 2026-07-18: treat “Bing still supports FAQPage” as an unverified claim au-delà generic structured-data parsing — I trouvé aucun current principal Bing source confirming a FAQ-specific rich result.

Quotes from the source

On-the-record statements. Où une page exposes the text, the lien is a deep lien que jumps to the quoted passage.

Google — DiscussionForumPosting launch (Thomas Han, Nov 27, 2023)

• “Forums with this markup are considered for having their content appear in the Perspective and ‘Discussions and forums’ features. However, the use of the markup does not guarantee appearance.” Jump to quote
• “Unlike our general structured data preference, we recommend providing the DiscussionForumPosting markup in Microdata (or RDFa) if possible.” Jump to quote

Google docs — Event’s virtual-only correction

• “Virtual experiences that have no real-world component aren’t supported. Events must take place in a physical location.” Jump to quote

Google docs — general eligibility principle (s’applique to tout six)

• “Specify all required properties listed in the documentation for your specific rich result type. Items that are missing required properties are not eligible for rich results.” Jump to quote

John Mueller, Google — schema n’est pas a ranking factor

• “Structured data won’t make your site rank better.” Coverage Relayed via Moteur de recherche Roundtable’s coverage of Mueller’s April 2025 Bluesky posts; treat the phrasing as transcribed secondary reporting.

Social & Community schema En un coup d’œil

The six types comparé

Fast facts

• “Social & Community schema” is a practitioner grouping, pas a Google or schema.org category.
• Status matters plus que taxonomy ici: four types are live, two are dead résultats enrichis with valid-but-inert markup.
• Eligibility ≠ afficher — valid markup obtient une page in the pool; Google encore decides si to montrer the enhancement, pour every live type.
• Pas a ranking factor pour quelconque of the six.
• DiscussionForumPosting is the un JSON-LD exception à travers ce site’s entier structured-data coverage — Google recommends Microdata/RDFa pour it specifically.
• Aucun publié removal mandate. I haven’t trouvé Google guidance saying leftover FAQPage/HowTo markup causes a penalty, but I aussi haven’t trouvé guidance appel it risk-free — the un confirmed fact is que it arrête producing a visible result.

Qui Social & Community schema type do I besoin?

Réponse pour lune page you’re marking up, and you’ll land on the correct type (and the correct deep dive to lire suivant).

Testez vos connaissances: Social & Community Schema

Five rapide questions on the six schema types, leur status, and how ils relate. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

My données structurées writing

• Balisage de données structurées — my broader prendre on the vocabulary, the formats, entity understanding, and the deprecation cycle. Ce hub’s six types are a slice of que bigger picture.
• Commerce Schema — the sibling hub pour the transactional-listing types (Product, ProductGroup, JobPosting), si you’re marking up something pour sale à la place.
• The Beginner’s Guide to SEO technique — où I frame schema as code que helps engines comprendre content and powers the fonctionnalités que faire a listing stand out.

From autour the industry

• Google À nouveau Dit Données structurées Ne fait pas Faire Votre site Rank Meilleur (Moteur de recherche Roundtable) — Mueller’s April 2025 statement, the myth-bust que s’applique à travers tout six types ici.
• Google Drops FAQ Résultats enrichis From Search (Moteur de recherche Journal) — coverage of the FAQPage removal and ce que stays valid.
• Discussion and profile markup launch post (Recherche Google Central) — the original DiscussionForumPosting announcement.
• schema.org — the vocabulary itself, straight from the source.

Journal des modifications