What you need to know
Put serviceType on a Service entity when a concise category helps explain what the service is. Use a natural phrase such as “Technical SEO audit” or “Audiovisual system integration”. Keep Service.name as the actual service name.
serviceType is a Text property of Service that describes the category or type of service. It complements Service.name and description. Good values are concise, factual and supported by visible page content.
Key properties
The table below summarizes the fields that most often determine whether the entity is clear and internally consistent. Only provide values supported by the page.
| Property | Importance | How to use it |
|---|---|---|
serviceType | Main property | Concise human-readable service category. |
Service.name | Related | Actual name of the offered service. |
description | Related | Longer explanation of scope and deliverables. |
provider | Related | Organization or Person delivering the service. |
areaServed | Related | Real geographic coverage. |
What serviceType does
serviceType adds a short category label to Service and is especially useful when Service.name is branded or very specific.
Write for meaning
Use natural wording that a customer or machine can understand. Avoid long marketing phrases and location stuffing.
serviceType versus name
name identifies the offered service; serviceType classifies it; description carries richer scope and deliverables.
Consistency
The category should be obvious from H1, copy and navigation. Structured data should not introduce a service the page does not offer.
Multiple service types
If a page genuinely covers several services, model several Service entities or a broader service instead of a long comma-separated keyword list.
Relationships
serviceType is more useful with provider, url, @id and areaServed because together they identify what the service is, who provides it and where.
Validation
Read serviceType out of context. If it sounds like a clear category rather than an ad headline, it is probably usable.
JSON-LD examples
Service with a clear serviceType
serviceType classifies the service while name and description provide context.
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://example.com/services/seo-audit/#service",
"name": "Enterprise Technical SEO Audit",
"serviceType": "Technical SEO audit",
"description": "Crawl analysis, indexing diagnostics and structured data review.",
"provider": {
"@type": "Organization",
"name": "Example SEO"
},
"areaServed": {
"@type": "Country",
"name": "United States"
},
"url": "https://example.com/services/seo-audit/"
}Google, Bing and Yandex
serviceType is valid Schema.org semantic data but not a standalone rich-result feature.
Bing supports Schema.org JSON-LD and can use entity properties such as serviceType to classify content.
Yandex supports Schema.org selectively; accurate Service properties still improve semantic clarity.
Important: valid structured data does not guarantee a rich result. Each search engine decides whether to use the data and how to present it.
Common mistakes
- warningStuffing locations and marketing adjectives into serviceType.
- warningUsing serviceType as a paragraph.
- warningRepeating description verbatim.
- warningAdding a service not offered on the page.
- warningCombining many unrelated services in one value.
Frequently asked questions
Is serviceType required?
Not universally, but it is useful when it clarifies the Service category.
Can serviceType contain several words?
Yes. It is Text, so a natural phrase is appropriate.
Should serviceType include a city?
Usually no. Use areaServed for geography.