Service
Your business does things for people. Service schema names each of those things, says who provides it, where, and (if you publish it) what it costs.
First, an honest expectation
Google has no rich result for Service. Adding it won't put stars, prices, or anything else next to your listing. So why bother?
Because a service page is often the most important page a small business has, and it's usually written in marketing language: "We bring your story to life on paper." A person gets it. A machine has to guess. Service schema says it plainly: this page is about letterpress printing, Fern & Ink provides it, in Minneapolis, starting at $280.
That clarity helps search engines and AI tools connect the dots between your business and the work you do. It's not flashy. It's just good labeling.
When to use it
The rule is simple: one service page, one Service block. Fern & Ink offers three services, and each has its own page:
/services/brand-identity/gets a Service for brand identity design/services/letterpress-printing/gets a Service for letterpress printing/services/wedding-invitations/gets a Service for wedding invitations
If you only have a single "What we do" page that lists everything in a paragraph or two, you can skip Service for now. The LocalBusiness or Organization block from earlier lessons already says what kind of business you are. Service earns its keep when a service has real content behind it: a description, process, examples, maybe a price.
Selling a physical thing with a SKU, like a notebook? That's a Product, not a Service. We'll meet Product in the Reviews lesson.
The code
Here's the Service block for Fern & Ink's letterpress printing page. The page itself says "250 two-color business cards, $280," so the price goes in the markup too.
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://fernandink.example/services/letterpress-printing/#service",
"name": "Letterpress Printing",
"serviceType": "Letterpress printing",
"description": "Custom letterpress printing for business cards, stationery, and event invitations, printed by hand on cotton paper in our Minneapolis studio.",
"url": "https://fernandink.example/services/letterpress-printing/",
"provider": { "@id": "https://fernandink.example/#organization" },
"areaServed": [
{ "@type": "City", "name": "Minneapolis" },
{ "@type": "State", "name": "Minnesota" }
],
"offers": {
"@type": "Offer",
"name": "Letterpress business cards",
"description": "250 two-color business cards on 100% cotton stock.",
"price": "280.00",
"priceCurrency": "USD",
"url": "https://fernandink.example/services/letterpress-printing/"
}
}
Line by line
Since Google doesn't have a Service rich result, there's no official required list. The tags below are our advice for a solid, useful block.
| Property | Our advice | What it does |
|---|---|---|
name | Recommended | The service's name as it appears on the page, usually the H1. |
serviceType | Recommended | The plain, generic category. "Letterpress printing," not "Heirloom Press Experience." Think of it as what someone would type into a search box. |
description | Recommended | One or two sentences that match the page's intro. Plain language beats slogans. |
provider | Recommended | Who does the work. Point it at your business's @id instead of retyping the whole business. |
areaServed | Recommended | Where you offer it. A City, State, Country, or a simple text value like "Twin Cities metro." |
url | Recommended | The service page's own address. |
offers | Optional | An Offer with a price. Only add it if the price is visible on the page. |
@id | Optional | A name tag for this service, so other blocks (or other pages) can refer to it. |
The provider line is the important one
Remember the @id for Fern & Ink, https://fernandink.example/#organization? You defined the full business once (name, address, phone, logo) back in the Organization and LocalBusiness lessons. Here, you just point at it.
That one line tells machines "this is the same Fern & Ink, not a different one." Do it on all three service pages and you've built a small, tidy graph: one business, three services, all connected.
Prices: only if they're on the page
An Offer with price and priceCurrency is the simplest way to say what something costs. Write the price as a number with no currency symbol ("280.00", not "$280"), and put the currency in priceCurrency as a three-letter code like USD.
Lots of service businesses publish a "starting at" price instead of a fixed one. For that, use a priceSpecification with minPrice:
{
"offers": {
"@type": "Offer",
"priceSpecification": {
"@type": "PriceSpecification",
"minPrice": "1200.00",
"priceCurrency": "USD"
}
}
}
That snippet would sit inside the Service block for brand identity design, where the page says "Projects start at $1,200."
And if your pricing is "contact us for a quote"? Leave offers out entirely. The rest of the block is still useful on its own.
Common mistakes
- Inventing a price. If the page doesn't show it, the markup shouldn't say it. A made-up price that doesn't match what clients are quoted is worse than no price.
- One page, every service. Putting all three services in the markup of the homepage, when the homepage only mentions them in passing. Mark up each service on its own page.
- Retyping the business. Pasting a full
LocalBusinessinside everyprovider. It works, but one typo creates a "different" business. Point at the@idinstead. - Keyword-stuffed
serviceType. "Best Minneapolis letterpress printing wedding invitations cards" isn't a category. Keep it short.
Where does this go?
In the <head> of the service page, like every other block in this course. If your site already outputs a @graph with WebPage and BreadcrumbList, the Service can join that graph as one more item. Drop the @context line from the Service when you do, since the graph already has one.
If you use a CMS, a service page template is a great place to automate this. Give editors fields for service type, starting price, and area served, then output the block from those fields. Leave the price field empty and the template should skip offers.
Try it
Write the Service block for Fern & Ink's wedding invitations page. The page says: "Custom letterpress wedding invitation suites, designed and printed in Minneapolis. We ship anywhere in the US." It doesn't list a price.
Hints: what should areaServed be now that they ship nationwide? (A Country named "United States" works.) And should there be an offers property? (No, there's no price on the page.)
Check yourself
- I know Service has no Google rich result, and that its value is clarity.
- I give each real service page its own Service block.
- My
providerpoints at my business's@id. - I use a plain, generic
serviceType. - I only add
offerswhen the price is visible on the page.
How Service fits with LocalBusiness and Article for local search: Schema Markup Explained, Part 2: LocalBusiness, Service, Article, and Local Search.