Skip to content

Should You Add Service Schema Markup to Your Service Pages?

Service structured data is code that describes one of your services: its name, what it is, which business provides it, and the area it covers. It’s an optional extra. Google doesn’t list Service as a markup type that creates a special search result, so add it only after your local business markup is right, and only for services you really offer, with details that match the page.

Schema.org, the shared vocabulary used for structured data, has a type called Service. Its main fields are:

  • name: the service name, like “Water Heater Installation”
  • description: a short plain description
  • provider: your business, usually linked to your local business markup
  • areaServed: the places you offer it
  • serviceType: the kind of service
  • offers: pricing details, if you show prices on the page

Google keeps a list of the structured data types that can create special search features. As of October 16, 2026, Service is not on it. So this markup won’t create a special look in Google results. Its value is in describing your services clearly in a standard format that any search engine or tool can read.

Say Greenline Lawn Care has a page for “Aeration and Overseeding.” Its developer adds Service markup with that name, a one-sentence description, Greenline as the provider, and the three cities listed on the page as areaServed. Every fact matches what visitors see.

  • It labels what you sell. Clear labels can help search engines and artificial intelligence (AI) tools connect your services to your business.
  • It must match reality. Google’s general rules say markup must describe content visitors can see and must not be misleading. Markup for services you don’t offer, or areas you don’t serve, breaks those rules.
  • It’s easy to overdo. Some plugins add service markup for every keyword. That’s clutter, not help.
  • It’s lower priority. If your local business markup, titles, and service pages aren’t solid, fix those first.

Service businesses with separate pages for each main service. Skip it if you have a one-page site, or if your website builder doesn’t let you control the markup cleanly. Product sellers should look at 19.6.3 Product Structured Data instead.

  1. Finish your local business markup first (see 19.6.1 Local Business Structured Data).
  2. List your real services from your Master Business Record and your Google Business Profile (GBP) services list (see 14.1.7 Services). Use the same names.
  3. Add Service markup only to the page for that service. One main service per page.
  4. Fill in name, description, and provider. Link the provider to your business markup so they’re clearly connected. Your developer may do this with an “@id” reference.
  5. Add areaServed with only the places listed on that page and in your service area (see 14.1.3 Service Area).
  6. Only add prices in “offers” if the same prices show on the page. Keep them current (see 11.3.2 Pricing Disclosures).
  7. Test the page. Google’s Rich Results Test only checks types that create Google features, so it may not report on Service markup. Use the Schema Markup Validator at validator.schema.org to check the code (see 19.6.6 Testing Structured Data).
  8. Review the markup any time you change a service, its name, or your service area.
  • A list of service pages with markup and the date added or changed
  • Schema Markup Validator results for each page
  • A note showing the service names match your GBP services list

Keep these in your website records folder.

  • Expecting a rich result. Google doesn’t list Service as a supported feature, so nothing new will show in results.
  • Listing services you don’t offer. It’s misleading and goes against Google’s structured data rules.
  • Listing every town in the state as areaServed. Use only places you really serve and show on the page.
  • Old prices in the code. If you change prices on the page, change the markup too, or remove the price.
  • Two plugins adding service markup. You end up with duplicate or conflicting code. Use one source.
  • Skipping the basics. Service markup won’t help a thin service page. Write the page first (see 13.4.2 Service Pages).

Your web developer or a search engine optimization (SEO) specialist: if you have many services or locations, or your builder adds markup you can’t control. Questions to ask:

  • Is our service markup connected to our main business markup?
  • Do the names, areas, and prices in the code match the visible page?

[Bill: add a short story or lesson here. For example, whether you add Service markup on SiteSmarty client sites and why, or a plugin you’ve seen add junk service markup.]

If you’d rather have this done for you, SiteSmarty builds service pages with clean, accurate structured data.

  • [Date I did this:]
  • [What I actually did, step by step: whether I added Service markup to SiteSmarty’s service pages, which fields I used, and how I tested it]
  • [What it cost and how long it took:]
  • [What surprised me or what I’d do differently:]
  • [Screenshot or photo to add, with private info blurred: service markup on one SiteSmarty page and the validator result]
  • [Result so far:]

Does Google show rich results for Service schema? Google’s list of supported structured data features doesn’t include Service as of October 16, 2026.

What is areaServed? A Schema.org field for the places where the service is available, like cities or counties.

Should every service page have its own markup? If you add it, put one service’s markup on that service’s page, not all of them on one page.

Can I list prices? Only if the same prices show on the page and you keep them current.

Is service schema worth adding? It’s optional. Do it after your local business markup and service pages are solid.

  • Question: If service markup is used, does it describe only real services, real areas, and visible details on each service page?
  • Pass looks like: One Service block per service page, names matching the GBP services list, provider linked to the business markup, areaServed limited to real areas, prices only if shown, and a clean validator result.
  • Fail looks like: Services not offered, statewide area lists, old prices, duplicate plugin markup, or markup on thin pages.
  • Evidence to collect: The service markup list, validator results, and the GBP services comparison.

Where this fits

Do this first: 19.6.1 Local Business Structured Data, 13.4.2 Service Pages

Do this next: 19.6.3 Product Structured Data

Related pages: 7.7 Define the Service Area, 11.3.2 Pricing Disclosures, 14.1.3 Service Area, 14.1.7 Services, 19.6.6 Testing Structured Data, 19.7 Entity Consistency

Sources

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.

Get free updates

I'll send you a short email when new guide pages and videos go up.

No sales pitches. Unsubscribe any time.