暫定日本語訳：Social & Community Schema

暫定日本語案: TL;DR — “Social & Community schema” is my shorthと 向け six schema.org types 暫定日本語案: that mark up コンテンツ people create, interact とともに, or follow instructions from — 暫定日本語案: 向けum posts, Q&A threads, FAQs, how-tos, events, と software/app ページ. Add その 暫定日本語案: right one と a ページ becomes eligible 向け a specialized search treatment. The 暫定日本語案: twist: two of その six (FAQページ と HowTo) had そのir rich results removed by 暫定日本語案: Google と now do nothing visible in search, while その oそのr four 暫定日本語案: (DiscussionForumPosting, QAページ, Event, SoftwareApplication) are 暫定日本語案: still fully active. Knowing which half you’re dealing とともに changes wheそのr その 暫定日本語案: markup is worth your time. 暫定日本語案: Evidence for this claim Google documents DiscussionForumPosting for genuine user-generated forum discussions and distinguishes Q&A-pattern pages. Scope: Current Google discussion-forum structured-data guidance; eligibility does not guarantee visibility. Confidence: high · Verified: 2026-07-14 Google Search Central: Discussion forum structured data Evidence for this claim Google feature support is defined by the current structured-data Search Gallery, not by a practitioner grouping or Schema.org validity alone. Scope: Current Google supported structured-data features; display remains discretionary. Confidence: high · Verified: 2026-07-14 Google Search Central: Structured data feature gallery

暫定日本語案: What “Social & Community” schema means

暫定日本語案: A 向けum thread, a support Q&A, a list of FAQs, a recipe’s steps, a concert listing, 暫定日本語案: と an app’s download ページ don’t look alike — but そのy share a job 向け search 暫定日本語案: engines: each is a distinct unit of コンテンツ that a person interacts とともに, not just 暫定日本語案: reads. 構造化データ (usually JSON-LD) is code you add that spells out what 暫定日本語案: that unit is — “this is a question とともに three community answers,” “this event 暫定日本語案: happens at this address on this date” — using その shared vocabulary at 暫定日本語案: schema.org.

暫定日本語案: “Social & Community schema” isn’t an official Google or schema.org grouping. It’s my 暫定日本語案: umbrella 向け six types that cover this territory:

• 暫定日本語案: DiscussionForumPosting — a 向けum thread or community post.
• 暫定日本語案: QAページ — a single question とともに community-submitted answers (Stack Overflow, 暫定日本語案: a 向けum’s “solved” thread).
• 暫定日本語案: FAQページ — a site-owner’s list of frequently asked questions と answers.
• 暫定日本語案: HowTo — step-by-step instructions 向け completing a task.
• 暫定日本語案: Event — an event’s date, location, と details.
• 暫定日本語案: SoftwareApplication — an app or software 商品’s name, category, price, と 暫定日本語案: rating.

暫定日本語案: One routing note be向けe その type list: a ページ whose primary focus is identifying a 暫定日本語案: person or organization — an author bio, a contributor ページ — is Google’s separate 暫定日本語案: Profileページ 構造化データ, not one of そのse six. It isn’t covered in this hub; 暫定日本語案: see Google’s own Profileページ guide if that’s その ページ you’re marking up.

暫定日本語案: The single most important thing to know: half of そのse are dead rich results

暫定日本語案: This is その one fact that separates a useful article from a stale one. As of 2026:

• 暫定日本語案: Still fully alive, documented, no deprecation notice: DiscussionForumPosting, 暫定日本語案: QAページ, Event, SoftwareApplication.
• 暫定日本語案: Rich result removed — type still technically valid, but invisible in search 向け 暫定日本語案: almost everyone: FAQページ (restricted 2023, fully removed May 7, 2026) と 暫定日本語案: HowTo (removed in two stages, fully gone by September 2023).

暫定日本語案: Don’t take a five-year-old blog post’s word 向け which is which — その lとscape 暫定日本語案: shifted under FAQページ と HowTo specifically, と a lot of still-circulating advice 暫定日本語案: hasn’t caught up.

暫定日本語案: Why you’d boそのr: rich results (when そのy still exist)

暫定日本語案: The payoff, where it still applies, is a specialized listing in search:

• 暫定日本語案: 💬 a 向けum thread surfaced in Google’s Discussions と 向けums feature
• 暫定日本語案: ❓ a Q&A thread shown とともに its accepted answer
• 暫定日本語案: 📅 an event card とともに date, location, と ticketing
• 暫定日本語案: 📱 an app snippet とともに its star rating, price, と OS

暫定日本語案: Add その matching schema とともに its required properties, と その ページ becomes 暫定日本語案: eligible. Eligible, never guaranteed — Google’s systems still separately decide 暫定日本語案: wheそのr to actually show it.

暫定日本語案: The thing most people get wrong

暫定日本語案: None of そのse six types are a ranking factor. Google has said this plainly と 暫定日本語案: repeatedly across 構造化データ generally. What schema does is make a ページ 暫定日本語案: eligible 向け a richer listing (which can lift clicks) と help Google understと 暫定日本語案: その ページ. That’s different from ranking better.

暫定日本語案: The second trap is more specific to this group: using FAQページ or HowTo markup 暫定日本語案: expecting a rich result that no longer exists. The type is still valid markup, と 暫定日本語案: I haven’t found published Google guidance saying you must remove it — but it won’t 暫定日本語案: produce その expとable snippet it used to, so don’t count on it doing anything 暫定日本語案: visible. Spend new ef向けt where その rich result is still live.

暫定日本語案: Want その full breakdown — where each type sits in その schema.org hierarchy, その 暫定日本語案: required properties, その exact removal dates, と which article to read next? Switch 暫定日本語案: to その Advanced tab.

暫定日本語案: TL;DR — “Social & Community schema” is my practitioner grouping, not a Google 暫定日本語案: or schema.org category, 向け six types built around user-generated, interactive, or 暫定日本語案: instructional コンテンツ: DiscussionForumPosting, QAページ, FAQページ, 暫定日本語案: HowTo, Event, と SoftwareApplication. Google documents そのm across 暫定日本語案: three separate families と schema.org doesn’t unify そのm taxonomically eiそのr. The 暫定日本語案: fact that actually matters: DiscussionForumPosting, QAページ, Event, と 暫定日本語案: SoftwareApplication remain live, documented rich results; FAQページ (restricted 暫定日本語案: Aug 2023, fully removed May 7, 2026) と HowTo (removed in two stages, fully 暫定日本語案: gone by Sept 13, 2023) are dead rich results — その schema.org types stay valid, 暫定日本語案: but そのy no longer produce anything in その SERP 向け almost any site. None of その six 暫定日本語案: affect rankings; every one only buys eligibility. 暫定日本語案: Evidence for this claim Google documents DiscussionForumPosting for genuine user-generated forum discussions and distinguishes Q&A-pattern pages. Scope: Current Google discussion-forum structured-data guidance; eligibility does not guarantee visibility. Confidence: high · Verified: 2026-07-14 Google Search Central: Discussion forum structured data Evidence for this claim Google feature support is defined by the current structured-data Search Gallery, not by a practitioner grouping or Schema.org validity alone. Scope: Current Google supported structured-data features; display remains discretionary. Confidence: high · Verified: 2026-07-14 Google Search Central: Structured data feature gallery

暫定日本語案: First, an honest framing: this is my grouping, not Google’s

暫定日本語案: Most コンテンツ that talks about “community” or “engagement” schema quietly implies 暫定日本語案: そのse six types are an official family. They aren’t.

• 暫定日本語案: Google splits そのm across documentation families. DiscussionForumPosting と 暫定日本語案: QAページ sit under general Feature guides; FAQページ と HowTo have (or had) そのir 暫定日本語案: own dedicated guides; Event has its own guide; SoftwareApplication sits under 暫定日本語案: Feature guides too, alongside completely unrelated types.
• 暫定日本語案: schema.org doesn’t unify そのm eiそのr. They span different branches of その 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” コンテンツ.

暫定日本語案: I put そのm in one hub because そのy share a practical SEO problem — user-facing, 暫定日本語案: interactive or instructional コンテンツ that a reader does something とともに — not because 暫定日本語案: Google or schema.org files そのm togeそのr. I’d raそのr say that plainly than imply a 暫定日本語案: taxonomy that doesn’t exist.

暫定日本語案: The six types at a glance

• 暫定日本語案: DiscussionForumPosting (schema.org/DiscussionForumPosting) — a 向けum thread 暫定日本語案: or user-generated community post. Launched November 27, 2023 alongside 暫定日本語案: ProfilePage, tied to Google’s Discussions と 向けums と Perspectives features. 暫定日本語案: Requires author, author.name, datePublished, と at least one of 暫定日本語案: text/image/video on その post と every nested Comment. The real outlier: 暫定日本語案: Google recommends Microdata or RDFa over JSON-LD 向け this specific type, to 暫定日本語案: avoid duplicating large text blocks — その opposite of its usual JSON-LD preference. 暫定日本語案: Strictly 向け genuinely user-generated コンテンツ, never site-authored articles.
• 暫定日本語案: QAページ (schema.org/QAPage) — a ページ built around a single question とともに 暫定日本語案: community-submitted answers (a solved 向けum thread, a Stack Overflow ページ). 暫定日本語案: Requires a mainEntity Question とともに name, answerCount, と at least one of 暫定日本語案: acceptedAnswer/suggestedAnswer. As of this writing it carries no 暫定日本語案: deprecation notice — その freshest contrast in this whole hub, since its two 暫定日本語案: closest siblings (FAQページ, HowTo) both lost そのir rich results. Google’s own 暫定日本語案: dividing line against DiscussionForumPosting: “is your 向けum primarily Q&A?”
• 暫定日本語案: FAQページ (schema.org/FAQPage) — a site owner’s fixed list of questions と 暫定日本語案: answers (mainEntity array of Question items, each とともに a name と an 暫定日本語案: acceptedAnswer). The rich result was restricted to government と health sites 暫定日本語案: on August 8, 2023, そのn fully removed 向け everyone — including those 暫定日本語案: remaining sites — on May 7, 2026. The type itself isn’t deprecated as vocabulary, 暫定日本語案: と Google’s general structured-data guidance frames markup as helping ページ 暫定日本語案: understとing independent of rich-result eligibility — but その dedicated FAQページ 暫定日本語案: 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 とともに FAQページ” claim past その 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 — と Google’s own changelog describes その removal as covering “both desktop 暫定日本語案: と mobile devices.” A full, global removal, not a desktop-only one. Don’t confuse 暫定日本語案: it とともに Recipe schema, a separate type that still earns real rich results.
• 暫定日本語案: Event (schema.org/Event) — an event’s name, date, と location. Requires 暫定日本語案: name, startDate, と location. The load-bearing 2026 correction: Google’s 暫定日本語案: current docs state virtual-only events aren’t eligible 向け その 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 暫定日本語案: pとemic-era advice treats eventAttendanceMode alone as sufficient; it isn’t 向け 暫定日本語案: その rich result.
• 暫定日本語案: SoftwareApplication (schema.org/SoftwareApplication) — an app or software 暫定日本語案: 商品’s name, category, OS, price, と rating, feeding Google’s Software App 暫定日本語案: rich result (star rating, price, OS in その snippet). Requires name, offers 暫定日本語案: (とともに a price — 0 向け free apps), と at least one of aggregateRating or 暫定日本語案: review. applicationCategory と operatingSystem are recommended. Distinct 暫定日本語案: from 商品 schema — a paid SaaS or web app should generally use 暫定日本語案: SoftwareApplication (or its WebApplication/MobileApplication subtypes), not 暫定日本語案: 商品.

暫定日本語案: One adjacent routing case worth flagging: a ページ whose primary focus is identifying a 暫定日本語案: person or organization affiliated とともに その site — an author bio, a contributor ページ — 暫定日本語案: belongs to Google’s separate Profileページ 構造化データ 暫定日本語案: (schema.org/ProfilePage), not to any of そのse six. Google’s Profileページ guide 暫定日本語案: documents its own mainEntity と author-relationship properties; linking an author 暫定日本語案: to a profile establishes identity, it does not guarantee display, identity 暫定日本語案: consolidation, or ranking. Profileページ isn’t part of this hub’s six types, but if 暫定日本語案: you’re weighing a DiscussionForumPosting author ページ against a Profileページ, that’s 暫定日本語案: その deciding question. 暫定日本語案: Evidence for this claim ProfilePage is for a page primarily about one person or organization affiliated with the site, often an author or contributor profile; linking authors to profiles does not guarantee display, identity consolidation or ranking. Scope: public web and Google Search where documented Confidence: high · Verified: 2026-07-17 Profile page structured data

暫定日本語案: I keep this hub deliberately shallow on each type’s full property tables — その deep 暫定日本語案: dives live in その six child articles linked at その end.

暫定日本語案: The status split, restated plainly

暫定日本語案: This is worth a table of its own because it’s その one thing every reader of this hub 暫定日本語案: actually needs to walk away とともに:

| 暫定日本語案: Type | Rich result status | | 暫定日本語案: --- | --- | | 暫定日本語案: DiscussionForumPosting | Live — launched Nov 27, 2023, no deprecation | | 暫定日本語案: QAページ | Live — no deprecation notice as of this writing | | 暫定日本語案: Event | Live — but virtual-only events are NOT eligible | | 暫定日本語案: SoftwareApplication | Live — ratings must be genuine, not self-serving | | 暫定日本語案: FAQページ | Dead — restricted Aug 2023, fully removed May 7, 2026 | | 暫定日本語案: HowTo | Dead — removed in two stages, fully gone by Sept 13, 2023 |

暫定日本語案: For その two dead ones, その schema.org type remains valid vocabulary. I haven’t 暫定日本語案: found current Google guidance eiそのr mとating removal or explicitly calling it 暫定日本語案: harmless to keep — その one fact you can rely on is that it no longer produces a 暫定日本語案: visible search enhancement 向け almost anyone.

暫定日本語案: Shared ground rules across all six

暫定日本語案: Even though その types don’t share a taxonomy, そのy share Google’s general 暫定日本語案: structured-data guidelines:

• 暫定日本語案: Required properties are その eligibility gate. Miss one と その ページ isn’t 暫定日本語案: eligible 向け that rich result, live or dead.
• 暫定日本語案: Eligibility ≠ guaranteed display. Valid markup gets a ページ into その pool; 暫定日本語案: Google’s systems still separately decide wheそのr to show その enhancement.
• 暫定日本語案: Only mark up visible, accurate, genuinely-sourced コンテンツ. No fake reviews on 暫定日本語案: a SoftwareApplication ページ, no self-answered “community” Q&A, no fabricated 暫定日本語案: events. Google’s spam と コンテンツ-quality policies apply across all six, と 暫定日本語案: several carry そのir own feature-specific コンテンツ policy on top.
• 暫定日本語案: JSON-LD is Google’s general recommendation — とともに その explicit 暫定日本語案: DiscussionForumPosting exception noted above.

暫定日本語案: Does Social & Community schema help SEO?

暫定日本語案: No, not rankings. The same “構造化データ won’t make your site rank better” 暫定日本語案: position Google has repeated across every schema type applies here とともにout 暫定日本語案: exception. What そのse six types do — where そのir rich result still exists — is earn 暫定日本語案: eligibility 向け a specialized listing と help Google understと その ページ. For 暫定日本語案: FAQページ と HowTo specifically, that eligibility no longer produces a visible SERP 暫定日本語案: change 向け most sites; その on-ページ と understとing value is what’s left.

暫定日本語案: Where to go next

暫定日本語案: This hub is その map; each of そのse is its own deep dive nested under it:

• 暫定日本語案: DiscussionForumPosting schema — required properties, その Microdata/RDFa 暫定日本語案: outlier, その digitalSourceType AI-disclosure field, と その 2025–2026 UGC/向けum 暫定日本語案: visibility question.
• 暫定日本語案: QAページ schema — その QAページ-vs-FAQページ authorship distinction, その 暫定日本語案: QAページ-vs-DiscussionForumPosting dividing line, と why it’s still fully supported.
• 暫定日本語案: FAQページ schema — その exact restriction-to-removal timeline, what’s still valid 暫定日本語案: vs. gone, と wheそのr it’s still worth implementing.
• 暫定日本語案: HowTo schema — その two-stage removal, その desktop-only misconception corrected, 暫定日本語案: と how it differs from Recipe schema.
• 暫定日本語案: Event schema — required properties, その virtual-only-events myth-bust, と 暫定日本語案: eventStatus hとling.
• 暫定日本語案: SoftwareApplication schema — required properties, その applicationCategory 暫定日本語案: enum, と when to use it instead of 商品 schema.

暫定日本語案: For その wider picture, this hub nests under その broader 暫定日本語案: structured data subcluster — see also その 暫定日本語案: sibling Commerce schema hub そのre 向け その transactional-listing types (商品, 暫定日本語案: 商品Group, JobPosting), と その schema markup article 向け その vocabulary, 暫定日本語案: 向けmats, と deprecation cycle generally. It all lives in その 暫定日本語案: on-page cluster.

暫定日本語案: AI summary

暫定日本語案: A condensed take on その Advanced version:

• 暫定日本語案: What it is: “Social & Community schema” is Patrick’s practitioner grouping — 暫定日本語案: not a Google or schema.org category — 向け six types covering user-generated, 暫定日本語案: interactive, or instructional コンテンツ: DiscussionForumPosting, QAページ, 暫定日本語案: FAQページ, HowTo, Event, SoftwareApplication.
• 暫定日本語案: Not an official family: Google documents そのm across separate Feature-guide 暫定日本語案: entries; schema.org doesn’t group そのm eiそのr.
• 暫定日本語案: Adjacent, not included: author/org identity ページ route to Google’s separate 暫定日本語案: Profileページ type, not to any of そのse six.
• 暫定日本語案: The critical status split:
  • 暫定日本語案: Live rich results, no deprecation: DiscussionForumPosting (launched Nov 27, 暫定日本語案: 2023), QAページ, Event (virtual-only events NOT eligible), SoftwareApplication.
  • 暫定日本語案: Dead rich results, type still valid: FAQページ (restricted Aug 2023 → fully 暫定日本語案: removed May 7, 2026) と HowTo (removed in two stages, fully gone by Sept 13, 暫定日本語案: 2023 — both desktop と mobile, not desktop-only).
• 暫定日本語案: Required properties (minimum):
  • 暫定日本語案: DiscussionForumPosting: author, author.name, datePublished, one of 暫定日本語案: text/image/video.
  • 暫定日本語案: QAページ: mainEntity Question とともに name, answerCount, one of 暫定日本語案: acceptedAnswer/suggestedAnswer.
  • 暫定日本語案: FAQページ: mainEntity array of Question items とともに name + acceptedAnswer.
  • 暫定日本語案: HowTo: step (HowToStep/HowToSection).
  • 暫定日本語案: Event: name, startDate, location.
  • 暫定日本語案: SoftwareApplication: name, offers (とともに price), one of aggregateRating/review.
• 暫定日本語案: Format note: JSON-LD is Google’s general recommendation, except 暫定日本語案: DiscussionForumPosting, where Google recommends Microdata/RDFa instead.
• 暫定日本語案: QAページ vs. FAQページ: authorship is その dividing line — FAQページ is 暫定日本語案: site-owner-authored; QAページ is community-submitted, potentially multiple answers.
• 暫定日本語案: QAページ vs. DiscussionForumPosting: “is your 向けum primarily Q&A?” is Google’s 暫定日本語案: own framing 向け which type to use.
• 暫定日本語案: SoftwareApplication vs. 商品: a paid SaaS/web app should generally use 暫定日本語案: SoftwareApplication (or WebApplication/MobileApplication), not 商品.
• 暫定日本語案: SEO impact: not a ranking factor 向け any of その six — eligibility と 暫定日本語案: understとing only, never rank.

暫定日本語案: Official documentation

暫定日本語案: Primary-source documentation 向け その six Social & Community schema types.

暫定日本語案: Google — shared rules

• 暫定日本語案: General structured data guidelines — その eligibility principle と コンテンツ-quality/spam policies that apply across all six types.
• 暫定日本語案: Structured data search gallery — その current source of truth 向け what still produces a rich result.

暫定日本語案: Google — each type

• 暫定日本語案: Discussion forum structured data — required/recommended properties, その Microdata/RDFa recommendation.
• 暫定日本語案: Q&A page structured data — QAページ’s Question/Answer structure と 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 その dedicated FAQページ doc itself, not just added a deprecation notice to it — link kept here as その historical location, but その changelog is その current source.
• 暫定日本語案: Event structured data — required/recommended properties と その eventStatus values.
• 暫定日本語案: Software App structured data — required/recommended properties と 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 ページ doesn’t name FAQページ or any of その oそのr five types specifically, と Bing has published no type-specific rich-result eligibility spec 向け any of そのm. Checked 2026-07-18: treat “Bing still supports FAQページ” as an unverified claim beyond generic structured-data parsing — I found no current primary Bing source confirming a FAQ-specific rich result.

暫定日本語案: Note: each child article’s Official Docs tab has その fuller, per-type property 暫定日本語案: table と コンテンツ-policy links — this list is その map, not その full detail.

暫定日本語案: Quotes from その source

暫定日本語案: On-その-record statements. Where a ページ exposes その text, その link is a deep link that 暫定日本語案: jumps to その quoted passage.

暫定日本語案: Google — DiscussionForumPosting launch (Thomas Han, Nov 27, 2023)

• 暫定日本語案: “Forums とともに this markup are considered 向け having そのir コンテンツ appear in その Perspective と ‘Discussions と 向けums’ features. However, その use of その markup does not guarantee appearance.” 暫定日本語案: Jump to quote
• 暫定日本語案: “Unlike our general 構造化データ preference, we recommend providing その 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 その documentation 向け your specific rich result type. Items that are missing required properties are not eligible 向け rich results.” 暫定日本語案: Jump to quote

暫定日本語案: John Mueller, Google — schema is not a ranking factor

• 暫定日本語案: “構造化データ won’t make your site rank better.” 暫定日本語案: Coverage 暫定日本語案: Relayed via Search Engine Roundtable’s coverage of Mueller’s April 2025 Bluesky posts; treat その phrasing as transcribed secondary reporting.

暫定日本語案: Each child article’s Quotes tab has その fuller, per-type set of verified 暫定日本語案: statements, including several items my research flagged as paraphrase-only because 暫定日本語案: その primary source レンダリングed via JavaScript or その coverage ページ returned a 403 — 暫定日本語案: those are marked inline in each article raそのr than presented here as verbatim.

暫定日本語案: Social & Community schema at a glance

暫定日本語案: The six types compared

| 暫定日本語案: | DiscussionForumPosting | QAページ | FAQページ | HowTo | Event | SoftwareApplication | | 暫定日本語案: --- | --- | --- | --- | --- | --- | --- | | 暫定日本語案: What it marks up | A 向けum thread/post | One question, community answers | Site-owner FAQ list | Step-by-step instructions | An event | An app/software 商品 | | 暫定日本語案: Rich result status | Live | Live | Dead (removed May 2026) | Dead (removed Sept 2023) | Live | Live | | 暫定日本語案: Minimum required | author, author.name, datePublished, one of text/image/video | mainEntity Question: name, answerCount, accepted/suggestedAnswer | mainEntity array of Question: name + acceptedAnswer | step (HowToStep/Section) | name, startDate, location | name, offers (price), one of aggregateRating/review | | 暫定日本語案: Recommended 向けmat | Microdata/RDFa (outlier) | JSON-LD | JSON-LD | JSON-LD | JSON-LD | JSON-LD | | 暫定日本語案: Bing support | None documented | None documented | None documented | None documented | None documented | None documented | | 暫定日本語案: Closest sibling confusion | vs. QAページ (is it primarily Q&A?) | vs. FAQページ (authorship) | vs. QAページ (authorship) | vs. Recipe (separate, still live) | — | vs. 商品 schema |

暫定日本語案: 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 とともに valid-but-inert markup.
• 暫定日本語案: Eligibility ≠ display — valid markup gets a ページ in その pool; Google still 暫定日本語案: decides wheそのr to show その enhancement, 向け every live type.
• 暫定日本語案: Not a ranking factor 向け any of その six.
• 暫定日本語案: DiscussionForumPosting is その one JSON-LD exception across this site’s entire 暫定日本語案: structured-data coverage — Google recommends Microdata/RDFa 向け it specifically.
• 暫定日本語案: No published removal mとate. I haven’t found Google guidance saying leftover 暫定日本語案: FAQページ/HowTo markup causes a penalty, but I also haven’t found guidance calling 暫定日本語案: it risk-free — その one confirmed fact is that it stops producing a visible result.

暫定日本語案: Which Social & Community schema type do I need?

暫定日本語案: Answer 向け その ページ you’re marking up, と you’ll lと on その right type (と その 暫定日本語案: right deep dive to read next).

暫定日本語案: Test yourself: Social & Community Schema

暫定日本語案: Five quick questions on その six schema types, そのir status, と how そのy relate. 暫定日本語案: Pick an answer 向け each, そのn check.

暫定日本語案: Resources worth your time

暫定日本語案: My 構造化データ writing

• 暫定日本語案: Schema Markup — my broader take on その vocabulary, その 向けmats, entity understとing, と その deprecation cycle. This hub’s six types are a slice of that bigger picture.
• 暫定日本語案: Commerce Schema — その sibling hub 向け その transactional-listing types (商品, 商品Group, JobPosting), if you’re marking up something 向け sale instead.
• 暫定日本語案: The Beginner’s Guide to Technical SEO — where I frame schema as code that helps engines understと コンテンツ と powers その features that make a listing stと out.

暫定日本語案: Full disclosure: I haven’t published a dedicated piece on any of そのse six 暫定日本語案: types specifically — this hub と its six child articles are original ground raそのr 暫定日本語案: than a rewrite of prior work. The writing above is my broader structured-data 暫定日本語案: material that this topic sits inside.

暫定日本語案: From around その industry

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

変更履歴