Service Schema Markup
Service describes a non-tangible offering from a business. While Google doesn't have a dedicated Service rich result, proper Service markup improves how Google understands and presents your service pages.
Google Search Features
No Google rich result uses Service markup directly. It's still valid schema.org, and it helps search engines understand the page.
When to Use Service
Properties
| Property | Type | Status | Description |
|---|---|---|---|
| name | Text | required | Service name. |
| description | Text | recommended | What the service includes. |
| provider | Organization or Person | recommended | Who provides the service. |
| areaServed | Text or GeoShape | optional | Service area. |
| serviceType | Text | optional | Category of service. |
| offers | Offer | optional | Pricing. |
| url | URL | optional | Service page URL. |
JSON-LD Examples
Consulting Service
A professional consulting service.
{
"@context": "https://schema.org",
"@type": "Service",
"name": "SEO Consulting",
"description": "Comprehensive SEO audits and strategy consulting for businesses.",
"provider": {
"@type": "Organization",
"name": "Digital Growth Agency"
},
"areaServed": "United States",
"serviceType": "Digital Marketing",
"offers": {
"@type": "Offer",
"price": "2500",
"priceCurrency": "USD"
}
}Common Mistakes
Using Product for services — Service is the correct type for non-tangible offerings.
Complete Guide to Service Schema Markup
Service describes something a business does rather than a thing it sells: consulting, cleaning, repairs, legal advice, hosting. Google doesn't document a rich result for Service markup, and review snippets don't list it among the types they support, so the markup describes the offering without changing how the page looks in search.
The useful properties connect the service to who offers it and where. provider names the Organization or Person that performs it, ideally by the same @id as the business's Organization or LocalBusiness markup. serviceType names the kind of service in plain words, areaServed says where it's available, and offers carries the price when the page states one, as an Offer with price and priceCurrency, or with a priceSpecification for a rate such as an hourly one.
A business with several services can describe each as its own Service on its own page, or list them together with hasOfferCatalog, an OfferCatalog whose items are Offers for each Service. The first suits a site with a page per service; the second suits a single services page.
The common mistake is using Product for a service in the hope of product rich results. Product is schema.org's type for goods, and a service described as one misstates what the page offers. The reverse happens too: a business selling something physical, such as a boxed software licence, is describing a Product.
schema.org has more specific types for some services: FinancialProduct for accounts, loans and cards, GovernmentService for services run by a public body, TaxiService, FoodService, and a few others. When one fits, use it; the Service properties described here still apply.
Related Types
Check Your Service Markup
The generator doesn't have a Service form yet. Paste your markup into the validator to check its types, properties and values, and what Google needs from it.
Open Validator