Social & Community Schema

TL;DR — “Social & Community schema” is my shorthand for six schema.org types that mark up content people create, interact with, or follow instructions from — forum posts, Q&A threads, FAQs, how-tos, events, and software/app pages. Add the right one and a page becomes eligible for a specialized search treatment. The twist: two of the six (FAQPage and HowTo) had their rich results removed by Google and now do nothing visible in search, while the other four (DiscussionForumPosting, QAPage, Event, SoftwareApplication) are still fully active. Knowing which half you’re dealing with changes whether the markup is worth your time.

What “Social & Community” schema means

A forum thread, a support Q&A, a list of FAQs, a recipe’s steps, a concert listing, and an app’s download page don’t look alike — but they share a job for search engines: each is a distinct unit of content that a person interacts with, not just reads. Structured data (usually JSON-LD) is code you add that spells out what that unit is — “this is a question with three community answers,” “this event happens at this address on this date” — using the shared vocabulary at schema.org.

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

• DiscussionForumPosting — a forum thread or community post.
• QAPage — a single question with community-submitted answers (Stack Overflow, a forum’s “solved” thread).
• FAQPage — a site-owner’s list of frequently asked questions and answers.
• HowTo — step-by-step instructions for completing a task.
• Event — an event’s date, location, and details.
• SoftwareApplication — an app or software product’s name, category, price, and rating.

One routing note before the type list: a page whose primary focus is identifying a person or organization — an author bio, a contributor page — is Google’s separate ProfilePage structured data, not one of these six. It isn’t covered in this hub; see Google’s own ProfilePage guide if that’s the page you’re marking up.

The single most important thing to know: half of these are dead rich results

This is the one fact that separates a useful article from a stale one. As of 2026:

• Still fully alive, documented, no deprecation notice: DiscussionForumPosting, QAPage, Event, SoftwareApplication.
• Rich result removed — type still technically valid, but invisible in search for almost everyone: FAQPage (restricted 2023, fully removed May 7, 2026) and HowTo (removed in two stages, fully gone by September 2023).

Don’t take a five-year-old blog post’s word for which is which — the landscape shifted under FAQPage and HowTo specifically, and a lot of still-circulating advice hasn’t caught up.

Why you’d bother: rich results (when they still exist)

The payoff, where it still applies, is a specialized listing in search:

• 💬 a forum thread surfaced in Google’s Discussions and forums feature
• ❓ a Q&A thread shown with its accepted answer
• 📅 an event card with date, location, and ticketing
• 📱 an app snippet with its star rating, price, and OS

Add the matching schema with its required properties, and the page becomes eligible. Eligible, never guaranteed — Google’s systems still separately decide whether to actually show it.

The thing most people get wrong

None of these six types are a ranking factor. Google has said this plainly and repeatedly across structured data generally. What schema does is make a page eligible for a richer listing (which can lift clicks) and help Google understand the page. That’s different from ranking better.

The second trap is more specific to this group: using FAQPage or HowTo markup expecting a rich result that no longer exists. The type is still valid markup, and I haven’t found published Google guidance saying you must remove it — but it won’t produce the expandable snippet it used to, so don’t count on it doing anything visible. Spend new effort where the rich result is still live.

Want the full breakdown — where each type sits in the schema.org hierarchy, the required properties, the exact removal dates, and which article to read next? Switch to the Advanced tab.

TL;DR — “Social & Community schema” is my practitioner grouping, not a Google or schema.org category, for six types built around user-generated, interactive, or instructional content: DiscussionForumPosting, QAPage, FAQPage, HowTo, Event, and SoftwareApplication. Google documents them across three separate families and schema.org doesn’t unify them taxonomically either. The fact that actually matters: DiscussionForumPosting, QAPage, Event, and SoftwareApplication remain live, documented rich results; FAQPage (restricted Aug 2023, fully removed May 7, 2026) and HowTo (removed in two stages, fully gone by Sept 13, 2023) are dead rich results — the schema.org types stay valid, but they no longer produce anything in the SERP for almost any site. None of the six affect rankings; every one only buys eligibility.

First, an honest framing: this is my grouping, not Google’s

Most content that talks about “community” or “engagement” schema quietly implies these six types are an official family. They aren’t.

• Google splits them across documentation families. DiscussionForumPosting and QAPage sit under general Feature guides; FAQPage and HowTo have (or had) their own dedicated guides; Event has its own guide; SoftwareApplication sits under Feature guides too, alongside completely unrelated types.
• schema.org doesn’t unify them either. They span different branches of the type hierarchy — some under CreativeWork-adjacent trees, Event as its own top-level type. There’s no schema.org grouping that bundles “social” or “community” content.

I put them in one hub because they share a practical SEO problem — user-facing, interactive or instructional content that a reader does something with — not because Google or schema.org files them together. I’d rather say that plainly than imply a taxonomy that doesn’t exist.

The six types at a glance

• 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 features. Requires author, author.name, datePublished, and at least one of text/image/video on the post and every nested Comment. The real outlier: Google recommends Microdata or RDFa over JSON-LD for this specific type, to avoid duplicating large text blocks — the opposite of its usual JSON-LD preference. Strictly for genuinely user-generated content, never site-authored articles.
• QAPage (schema.org/QAPage) — a page built around a single question with community-submitted answers (a solved forum thread, a Stack Overflow page). Requires a mainEntity Question with name, answerCount, and at least one of acceptedAnswer/suggestedAnswer. As of this writing it carries no deprecation notice — the freshest contrast in this whole hub, since its two closest siblings (FAQPage, HowTo) both lost their rich results. Google’s own dividing line against DiscussionForumPosting: “is your forum primarily Q&A?”
• FAQPage (schema.org/FAQPage) — a site owner’s fixed list of questions and answers (mainEntity array of Question items, each with a name and an acceptedAnswer). The rich result was restricted to government and health sites on August 8, 2023, then fully removed for everyone — including those 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 that used to cover this type in detail has itself been retired (as of this writing it 301-redirects to Google’s removal changelog entry; see Official Docs), so treat any specific “Google still does X with FAQPage” claim past the removal date as unverified unless you can point to current primary evidence.
• HowTo (schema.org/HowTo) — step-by-step instructions (step, HowToStep, HowToSection, plus tool, supply, totalTime). The rich result was removed in two stages — mobile first on August 8, 2023, desktop too by September 13, 2023 — and Google’s own changelog describes the removal as covering “both desktop and mobile devices.” A full, global removal, not a desktop-only one. Don’t confuse it with Recipe schema, a separate type that still earns real rich results.
• Event (schema.org/Event) — an event’s name, date, and location. Requires name, startDate, and location. The load-bearing 2026 correction: Google’s current docs state virtual-only events aren’t eligible for the rich result — “Virtual experiences that have no real-world component aren’t supported. Events must take place in a physical location.” A lot of still-circulating 2020 pandemic-era advice treats eventAttendanceMode alone as sufficient; it isn’t for the rich result.
• SoftwareApplication (schema.org/SoftwareApplication) — an app or software product’s name, category, OS, price, and rating, feeding Google’s Software App rich result (star rating, price, OS in the snippet). Requires name, offers (with a price — 0 for free apps), and at least one of aggregateRating or review. applicationCategory and operatingSystem are recommended. Distinct from Product schema — a paid SaaS or web app should generally use SoftwareApplication (or its WebApplication/MobileApplication subtypes), not Product.

One adjacent routing case worth flagging: a page whose primary focus is identifying a person or organization affiliated with the site — an author bio, a contributor page — belongs to Google’s separate ProfilePage structured data (schema.org/ProfilePage), not to any of these six. Google’s ProfilePage guide documents its own mainEntity and author-relationship properties; linking an author to a profile establishes identity, it does not guarantee display, identity consolidation, or ranking. ProfilePage isn’t part of this hub’s six types, but if you’re weighing a DiscussionForumPosting author page against a ProfilePage, that’s the deciding question.

I keep this hub deliberately shallow on each type’s full property tables — the deep dives live in the six child articles linked at the end.

The status split, restated plainly

This is worth a table of its own because it’s the one thing every reader of this hub actually needs to walk away with:

For the two dead ones, the schema.org type remains valid vocabulary. I haven’t found current Google guidance either mandating removal or explicitly calling it harmless to keep — the one fact you can rely on is that it no longer produces a visible search enhancement for almost anyone.

Shared ground rules across all six

Even though the types don’t share a taxonomy, they share Google’s general structured-data guidelines:

• Required properties are the eligibility gate. Miss one and the page isn’t eligible for that rich result, live or dead.
• Eligibility ≠ guaranteed display. Valid markup gets a page into the pool; Google’s systems still separately decide whether to show the enhancement.
• Only mark up visible, accurate, genuinely-sourced content. No fake reviews on a SoftwareApplication page, no self-answered “community” Q&A, no fabricated events. Google’s spam and content-quality policies apply across all six, and several carry their own feature-specific content policy on top.
• JSON-LD is Google’s general recommendation — with the explicit DiscussionForumPosting exception noted above.

Does Social & Community schema help SEO?

No, not rankings. The same “structured data won’t make your site rank better” position Google has repeated across every schema type applies here without exception. What these six types do — where their rich result still exists — is earn eligibility for a specialized listing and help Google understand the page. For FAQPage and HowTo specifically, that eligibility no longer produces a visible SERP change for most sites; the on-page and understanding value is what’s left.

Where to go next

This hub is the map; each of these is its own deep dive nested under it:

• DiscussionForumPosting schema — required 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 why it’s still fully supported.
• FAQPage schema — the exact restriction-to-removal timeline, what’s still valid vs. gone, and whether it’s still worth implementing.
• HowTo schema — the two-stage removal, the desktop-only misconception corrected, and how it differs from Recipe schema.
• Event schema — required properties, the virtual-only-events myth-bust, and eventStatus handling.
• SoftwareApplication schema — required properties, the applicationCategory enum, and when to use it instead of Product schema.

For the wider picture, this hub nests under the broader structured data subcluster — see also the sibling Commerce schema hub there for the transactional-listing types (Product, ProductGroup, JobPosting), and the schema markup article for the vocabulary, formats, and deprecation cycle generally. It all lives in the on-page cluster.

AI summary

A condensed take on the Advanced version:

• What it is: “Social & Community schema” is Patrick’s practitioner grouping — not a Google or schema.org category — for six types covering user-generated, interactive, or instructional content: DiscussionForumPosting, QAPage, FAQPage, HowTo, Event, SoftwareApplication.
• Not an official family: Google documents them across separate Feature-guide entries; schema.org doesn’t group them either.
• Adjacent, not included: author/org identity pages route to Google’s separate ProfilePage type, not to any of these six.
• The critical status split:
  • Live rich results, no deprecation: DiscussionForumPosting (launched Nov 27, 2023), QAPage, Event (virtual-only events NOT eligible), SoftwareApplication.
  • Dead rich results, type still valid: FAQPage (restricted Aug 2023 → fully removed May 7, 2026) and HowTo (removed in two stages, fully gone by Sept 13, 2023 — both desktop and mobile, not desktop-only).
• Required properties (minimum):
  • DiscussionForumPosting: author, author.name, datePublished, one of text/image/video.
  • QAPage: mainEntity Question with name, answerCount, one of acceptedAnswer/suggestedAnswer.
  • FAQPage: mainEntity array of Question items with name + acceptedAnswer.
  • HowTo: step (HowToStep/HowToSection).
  • Event: name, startDate, location.
  • SoftwareApplication: name, offers (with price), one of aggregateRating/review.
• Format note: JSON-LD is Google’s general recommendation, except DiscussionForumPosting, where Google recommends Microdata/RDFa instead.
• QAPage vs. FAQPage: authorship is the dividing line — FAQPage is site-owner-authored; QAPage is community-submitted, potentially multiple answers.
• QAPage vs. DiscussionForumPosting: “is your forum primarily Q&A?” is Google’s own framing for which type to use.
• SoftwareApplication vs. Product: a paid SaaS/web app should generally use SoftwareApplication (or WebApplication/MobileApplication), not Product.
• SEO impact: not a ranking factor for any of the six — eligibility and understanding only, never rank.

Official documentation

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

Google — shared rules

• General structured data guidelines — the eligibility principle and content-quality/spam policies that apply across all six types.
• Structured data search gallery — the current source of truth for what still produces a rich result.

Google — each type

• Discussion forum structured data — required/recommended properties, the Microdata/RDFa recommendation.
• Q&A page structured data — QAPage’s Question/Answer structure and eligibility rules.
• FAQ structured data — as of this writing (checked 2026-07-18) this URL 301-redirects to Google’s changelog entry on removing the FAQ rich result. Google appears to have retired the dedicated FAQPage doc itself, not just added a deprecation notice to it — link kept here as the historical location, but the changelog is the current source.
• Event structured data — required/recommended properties and the eventStatus values.
• Software App structured data — required/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 Tools — Marking up your site with structured data — generic schema.org support only; this page doesn’t name FAQPage or any of the other five types specifically, and Bing has published no type-specific rich-result eligibility spec for any of them. Checked 2026-07-18: treat “Bing still supports FAQPage” as an unverified claim beyond generic structured-data parsing — I found no current primary Bing source confirming a FAQ-specific rich result.

Quotes from the source

On-the-record statements. Where a page exposes the text, the link is a deep link that 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 (applies to all 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 is not a ranking factor

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

Social & Community schema at a glance

The six types compared

Fast facts

• “Social & Community schema” is a practitioner grouping, not a Google or schema.org category.
• Status matters more than taxonomy here: four types are live, two are dead rich results with valid-but-inert markup.
• Eligibility ≠ display — valid markup gets a page in the pool; Google still decides whether to show the enhancement, for every live type.
• Not a ranking factor for any of the six.
• DiscussionForumPosting is the one JSON-LD exception across this site’s entire structured-data coverage — Google recommends Microdata/RDFa for it specifically.
• No published removal mandate. I haven’t found Google guidance saying leftover FAQPage/HowTo markup causes a penalty, but I also haven’t found guidance calling it risk-free — the one confirmed fact is that it stops producing a visible result.

Which Social & Community schema type do I need?

Answer for the page you’re marking up, and you’ll land on the right type (and the right deep dive to read next).

Test yourself: Social & Community Schema

Five quick questions on the six schema types, their status, and how they relate. Pick an answer for each, then check.

Resources worth your time

My structured data writing

• Schema Markup — my broader take on the vocabulary, the formats, entity understanding, and the deprecation cycle. This hub’s six types are a slice of that bigger picture.
• Commerce Schema — the sibling hub for the transactional-listing types (Product, ProductGroup, JobPosting), if you’re marking up something for sale instead.
• The Beginner’s Guide to Technical SEO — where I frame schema as code that helps engines understand content and powers the features that make a listing stand out.

From around the industry

• Google Again Says Structured Data Does Not Make Your Site Rank Better (Search Engine Roundtable) — Mueller’s April 2025 statement, the myth-bust that applies across all six types here.
• Google Drops FAQ Rich Results From Search (Search Engine Journal) — coverage of the FAQPage removal and what stays valid.
• Discussion and profile markup launch post (Google Search Central) — the original DiscussionForumPosting announcement.
• schema.org — the vocabulary itself, straight from the source.

Social & Community Schema

"Social & Community schema" is a practitioner label — not an official Google or schema.org category — for six schema.org types built around user-generated, interactive, or instructional content: DiscussionForumPosting, QAPage, FAQPage, HowTo, Event, and SoftwareApplication.

Related: Schema Markup, DiscussionForumPosting Schema, QAPage Schema, FAQPage Schema, HowTo Schema, Event Schema, SoftwareApplication Schema

Social & Community Schema

Social & Community schema isn’t a term Google or schema.org uses themselves — it’s shorthand for six schema.org types that share a job: marking up content a reader interacts with rather than just reads. The six are DiscussionForumPosting (a forum thread or post), QAPage (a single question with community-submitted answers), FAQPage (a site owner’s fixed FAQ list), HowTo (step-by-step instructions), Event (an event’s date and location), and SoftwareApplication (an app or software product’s name, category, price, and rating).

Google documents these across separate feature guides rather than one family, and schema.org doesn’t unify them either. What actually matters for practitioners is status, not taxonomy: DiscussionForumPosting, QAPage, Event, and SoftwareApplication remain live, documented rich results with no deprecation notice, while FAQPage (restricted 2023, fully removed May 7, 2026) and HowTo (removed in two stages, fully gone by September 13, 2023) are dead rich results — the schema.org types stay technically valid, but they no longer produce a visible search enhancement for almost any site.

None of the six types are a ranking factor. Each only buys eligibility for a specialized listing where its rich result still exists, and Google’s systems separately decide whether to actually show it.

Related: Schema Markup, DiscussionForumPosting Schema, QAPage Schema, FAQPage Schema, HowTo Schema, Event Schema, SoftwareApplication Schema

Changelog