Schema.org canonical pattern: one Service entity with audience: { type: Audience, name: ... } + areaServed

Claim: Schema.org's GovernmentService example demonstrates the canonical pattern for audience-targeted services: one Service entity with audience: { "@type": "Audience", "name": "Veterans" } plus areaServed for geographic coverage.

Source: https://schema.org/GovernmentService

Confidence: Verified.

Why this matters for multi-vertical service businesses: The Schema.org-blessed pattern is one service entity per audience-targeted offering, with explicit audience and areaServed properties. Don't cram all audiences into a single Service via a comma-separated string in the description — that's invisible to consumers of the schema.

See RULE: One Service schema per vertical when offerings genuinely differ. Multi-audience Service when offering is identical. for the Candid prescription on when to use one-service-per-vertical vs one-service-with-multiple-audiences.