Service schema markup: what it describes and what Google uses
What Service schema markup describes, which properties are worth using, why Google shows no rich result for it, and how it fits with LocalBusiness and Organization.
By Crawlito · 8 min read
In short
- schema.org defines Service as a service provided by an organization, with properties such as serviceType, provider, areaServed, offers and hasOfferCatalog.
- Service is not in Google's search gallery at the time of writing, so Service markup on its own does not make a page eligible for any Google rich result.
- Service is also not a valid itemReviewed type for Google review snippets, so ratings attached to a Service do not produce star results.
- The useful pattern is a Service whose provider points by @id to the Organization or LocalBusiness defined once elsewhere on the site.
- Use the Schema Markup Validator to check Service markup, because the Rich Results Test only reports the features Google supports.
On this page
- What the schema.org Service type describes
- Does Google use Service markup?
- A Service markup example that links to your business
- How Service relates to LocalBusiness and Organization
- Why not just mark services up as Product?
- How to validate Service markup
- Frequently asked questions
- Check what crawlers receive from your service pages
Service schema markup is JSON-LD that describes a service a business provides: what it is, who provides it, where it is available and what it costs. schema.org defines the type and its properties, but Google does not list Service in its search gallery, so the markup does not make a page eligible for any rich result. It is still a clean way to state the facts of a service page in a form machines read without guessing, as long as it matches the visible page and links to your business entity rather than repeating it.
This post covers the Service type itself. If you need the business details (address, hours, locations), read the LocalBusiness schema guide first; for what a service page should say in its text, see local service pages for AI search.
What the schema.org Service type describes
schema.org/Service sits under Thing > Intangible > Service and is described as "a service provided by an organization", with delivery and print services as examples. It is not a subtype of LocalBusiness or Organization: a Service is the thing offered, and an Organization or Person is the one offering it.
Most of the properties defined on Service are optional and rarely needed. These are the ones that carry real information on a typical service page:
| Property | Expected type (schema.org) | What to put in it |
|---|---|---|
name | Text | The service as the page names it, such as "Boiler repair" |
serviceType | Text or GovernmentBenefitsType | The general kind of service, useful when name is a brand or package name |
provider | Organization or Person | The business that performs the service, ideally by @id reference |
areaServed | AdministrativeArea, GeoShape, Place or Text | Where the service is available; it replaced the older serviceArea |
offers | Offer or Demand | Price and terms, when the page states them |
hasOfferCatalog | OfferCatalog | A list of related offers, such as service tiers or sub-services |
availableChannel | ServiceChannel | How the service is delivered or booked, such as a phone line or URL |
providerMobility | Text | Whether the provider travels; schema.org gives static and dynamic as examples |
termsOfService | Text or URL | A link to the terms that apply |
audience | Audience | Who the service is for, when it is restricted |
schema.org also lists a handful of more specific subtypes: BroadcastService, CableOrSatelliteService, FinancialProduct, FoodService, GovernmentService, TaxiService and WebAPI. Most agencies, consultants and trades will use plain Service.
Does Google use Service markup?
Not for any feature it documents. Google's search gallery lists the structured data features it supports, from Article and Breadcrumb to Local business, Organization, Product and Software app. Service is not on the list at the time of writing. That means:
- No Service rich result exists, so there is nothing to win in the search results by adding it.
- The Rich Results Test does not list Service among the rich result types it supports, so it will not report a Service item as an eligible feature.
Google's review snippet documentation closes another door. Its list of valid itemReviewed types includes LocalBusiness, Organization, Product and Course, among others, but not Service. A rating nested inside a Service object is not a route to star results.
None of this makes the markup wrong. Google's introduction to structured data says it "uses structured data that it finds on the web to understand the content of the page", but Google does not document that it reads Service specifically, so do not assume it does. Treat Service markup as an accurate description for any system that parses schema.org, not as a ranking or visibility tactic. Our overview of structured data for AI search covers what is and is not documented about how AI systems use markup.
A Service markup example that links to your business
A common mistake is to paste a full business description inside every Service: name, address, phone, hours, repeated on twenty service pages and slowly drifting apart. Define the business once, usually on the homepage or contact page, give it an @id, and point to it.
On a service page, the markup can look like this:
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/services/boiler-repair/#service",
"name": "Boiler repair",
"serviceType": "Gas boiler repair",
"url": "https://www.example.com/services/boiler-repair/",
"description": "Diagnosis and repair of domestic gas boilers, including parts we stock on the van.",
"provider": { "@id": "https://www.example.com/#organization" },
"providerMobility": "dynamic",
"areaServed": [
{ "@type": "City", "name": "Leeds" },
{ "@type": "City", "name": "Bradford" }
],
"offers": {
"@type": "Offer",
"price": "95.00",
"priceCurrency": "GBP",
"description": "Call-out and first hour of labour. Parts are quoted separately."
}
}The provider value is only a reference. The full business entity, a LocalBusiness subtype such as Plumber or an Organization, lives once on the page where it belongs and carries the same @id. How @id references work across a site, and why they should resolve to real URLs, is covered in connecting entities with @id.
A few details in that example are deliberate:
areaServeduses named places, not a paragraph of 40 towns.Cityis a subtype of AdministrativeArea, whichareaServedaccepts. If coverage is really defined by postcode or radius, say that in the page text, and keep the markup to what you can state cleanly.- The price matches the page. If the page says "from £95" or "quote on request", the markup should not invent a fixed price. Leave
offersout when the page has no price. descriptionrestates the visible scope. It should not add claims the page does not make.
How Service relates to LocalBusiness and Organization
Think of three layers, each stated once:
| Layer | Type | Where it goes | What it says |
|---|---|---|---|
| The business | Organization, or a LocalBusiness subtype for a physical business | Homepage or about page, with an @id | Name, logo, contact details, address if it has one |
| What it offers overall | hasOfferCatalog or makesOffer on that business | Same place, or a services index page | The list of services |
| Each service | Service | Each service page | That service's scope, area and price |
schema.org lets you attach services to the business from either direction. provider on the Service points to the business. From the business side, hasOfferCatalog (available on Organization, Person and Service) points to an OfferCatalog, which is an ItemList of related offers; makesOffer (on Organization and Person) points to Offer objects, and each Offer names what it offers through itemOffered, which accepts a Service. A services index page might carry a catalog like this:
{
"@context": "https://schema.org",
"@type": "Plumber",
"@id": "https://www.example.com/#organization",
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Heating services",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": { "@id": "https://www.example.com/services/boiler-repair/#service" }
},
{
"@type": "Offer",
"itemOffered": { "@id": "https://www.example.com/services/boiler-servicing/#service" }
}
]
}
}Use the same @type and @id as the full business entity, so the two describe one node rather than two businesses. You do not need both directions. One consistent link from each Service to its provider is enough for a parser to connect them. Pick one pattern and use it everywhere, so a theme, a plugin and a hand-written block do not each describe the same business differently. The business entity itself is covered in the Organization schema guide.
For a business with no public premises, areaServed on the Service is the honest way to describe coverage. It does not require an address, unlike Google's LocalBusiness markup, which requires one.
Why not just mark services up as Product?
People try this because Product has rich results and Service does not. Two facts matter.
First, schema.org itself is broad here: it describes Product as "any offered product or service" and gives a haircut as an example. So a Product describing a packaged, fixed-price service is not invalid schema.org.
Second, Google's rules decide what happens in its results, and they are narrower. Its product snippet documentation says product rich results "only support pages that focus on a single product", and its merchant listings cover pages where shoppers can buy products. Its general structured data policies require that markup be "a true representation of the page content", that you use the most specific applicable type, and that you do not use markup to mislead. Relabelling a consulting engagement or a repair call-out as a Product to get a price or star snippet does not fit those rules, and a policy problem can cost you rich results the page would otherwise be eligible for.
Google's self-serving review rule also matters here. Its review snippet guidelines say that when the entity being reviewed controls the reviews about itself, its pages that use LocalBusiness or any other type of Organization structured data are ineligible for the star review feature. A service page usually describes and links to exactly that business, so testimonials about your own service belong in the page text, not in aggregateRating. Our guide to review and aggregate rating schema has the detail.
How to validate Service markup
Because Service is not a Google feature, the usual tool gives a misleading answer. Use them in this order:
- Schema Markup Validator. Google's structured data documentation points to the Schema Markup Validator to test all types of schema.org markup without Google-specific validation. Paste the URL and confirm a
Serviceitem appears with the properties you expect and no unknown property names. - Rich Results Test. Use it for the types on the same page that Google does support, such as Organization, LocalBusiness or Breadcrumb. Do not read "no Service result" as an error.
- Raw HTML. Confirm the JSON-LD is in the server response, so crawlers that do not run JavaScript receive it:
curl -s https://www.example.com/services/boiler-repair/ | grep -o '"@type": *"Service"'- Resolve the references. Open the URL in the
provider@idand check that the business entity with that exact@idis in its HTML. - Compare with the page. Name, price, area and scope in the markup should all appear in the visible text. Google's policies say not to mark up content readers cannot see.
If the validator reports syntax problems, fix those first: a single stray comma can stop a parser reading the whole block.
Frequently asked questions
Does Service schema markup produce a rich result in Google?
No. Service is not in Google's search gallery at the time of writing, so it does not make a page eligible for any rich result.
Should I use Service or LocalBusiness on a service page?
Use Service to describe the service and point its provider to the LocalBusiness or Organization defined once elsewhere on the site. LocalBusiness describes the business, not each thing it sells.
Can I add star ratings to Service markup?
You can write them, but Service is not a valid itemReviewed type for Google review snippets. Google also does not show stars for reviews a business controls about itself on pages that use LocalBusiness or Organization markup.
Is serviceArea still valid?
schema.org lists areaServed as superseding serviceArea. Use areaServed in new markup.
Will Service markup help AI assistants recommend my business?
Nothing documents that. It states your service facts in a machine-readable form, but whether an assistant uses or cites a page depends on many factors outside the markup.
Check what crawlers receive from your service pages
Service markup only describes a page accurately if it reaches crawlers in the HTML and agrees with the text. Run the free check on one of your service pages to see the markup and content a crawler actually gets.
Filed under Structure and schema. Topics: structured-data, json-ld, local-seo, google