schema.org/ServiceNo rich result
Service schema
A service being offered, as distinct from a product.
Where to use it
Consulting, audits, done-for-you offerings.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
service.json
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Acme Reference",
"description": "A one sentence description that restates its own subject.",
"provider": {
"@id": "https://www.seoforsolos.com/#organization"
},
"areaServed": "Worldwide",
"offers": {
"@type": "Offer",
"price": "249.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.seoforsolos.com/pricing"
},
"serviceType": "Technical audit"
}Properties
| Property | Status |
|---|---|
name | Required |
description | Recommended |
provider | Recommended |
areaServed | Recommended |
offers | Recommended |
serviceType | Recommended |
The three mistakes this type attracts
- 01Using Product for a service, which produces a shopping entity claim you cannot satisfy.
- 02Omitting provider, leaving the service unattached.
- 03areaServed omitted on a service that is geographically limited.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
Questions
What is the Service schema type for?
A service being offered, as distinct from a product. Use it on: consulting, audits, done-for-you offerings.
Which Service properties are required?
Service requires one property: name. It also recommends 5: description, provider, areaServed, offers, serviceType.
Does Service produce a rich result?
Service does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common Service mistake?
The most common Service mistake is: Using Product for a service, which produces a shopping entity claim you cannot satisfy.