Skip to main content

Service Schema Markup: How to Describe What You Offer and Verify It on the Page

admin9 min read
Illustration of service schema markup matching the visible service page

The phrase “service schema markup” can mean two different things. One is the structured data you add to your own page to describe a service you offer, such as plumbing, bookkeeping or web design. The other is a “schema markup service”, where you hire someone to write structured data for you. This article is about the first meaning. You will learn which fields describe a service, how to write them in JSON-LD, how to keep them consistent with what visitors read, and how to check the result on the live page. I will also be direct about the limits: markup helps search engines understand a page and does not guarantee any special display, ranking or traffic.

Service details being organized into structured data cards

What Service Schema Markup Describes

Schema.org defines Service as a service provided by an organization. In practice, you use it on a page that explains a piece of work you do for customers. JSON-LD (JavaScript Object Notation for Linked Data) is the format Google recommends for structured data, and it sits in a script block separate from your visible text.

Schema.org supports several properties on a Service. Five are enough for most small business pages:

  • name: the service as the page names it.
  • description: a short summary that agrees with the page copy.
  • serviceType: the kind of service, such as “gutter cleaning”.
  • provider: the person or organization that delivers it.
  • areaServed: the geographic area you genuinely cover.

Schema.org does not turn these five into a Google required-field checklist. They are a practical starting set, and you should add only what your page supports.

Three different items representing a service, a product and a local business location

Service Versus Product Versus LocalBusiness

These types answer different questions. Use Service for the work being offered. Use LocalBusiness to describe an applicable business or location, such as its address and opening hours. They can sit together on one page when both accurately describe it, for example a Service whose provider is a LocalBusiness. For location details, read the guide on how to describe a business location in JSON-LD.

Use Product for a product page. Do not relabel a service as a Product just to chase product-specific search features. Google’s product snippet documentation has its own eligibility rules, including a focus on one product or variants of that product, and those rules do not transfer to Service markup. If you also sell physical goods, the Product Schema Generator covers that type separately.

Gathering service facts from a visible web page before writing markup

Five Facts to Gather From the Visible Page

Before writing any code, collect the facts from the page itself. If you cannot find a fact on the page, do not put it in the markup.

  1. Service name. Copy the name from your heading or the first line of the page.
  2. Service type. Write the plain category, using words a customer would recognize.
  3. Provider. Use the business or person named on the page. If you also mark up your business entity, the Organization schema markup guide explains what to include.
  4. Area served. List only places you genuinely cover. If the service is not tied to a place, leave areaServed out rather than inventing a service area.
  5. Description. Summarize the scope in one or two sentences that agree with the copy visitors read.

Wording need not be identical, but the meaning must agree. A page that says “we repair laptops in store” should not carry markup claiming a nationwide mobile service.

An Annotated Service Schema Markup Example

The example below is illustrative. Every name and place is a fictional placeholder, so replace each value with facts your own service page supports.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Kitchen Cabinet Refinishing",
  "serviceType": "Cabinet refinishing",
  "description": "On-site sanding, repainting and resealing of existing kitchen cabinets, with a written quote after a home visit.",
  "provider": {
    "@type": "Organization",
    "name": "Example Finishing Studio",
    "url": "https://www.example.com/"
  },
  "areaServed": {
    "@type": "City",
    "name": "Springfield"
  }
}
</script>

The visible copy on the same page should say something equivalent, for instance: “Example Finishing Studio refinishes existing kitchen cabinets on site in Springfield. We sand, repaint and reseal, and you receive a written quote after a home visit.” The markup restates what readers can already see. It does not add claims, prices or reviews that the page does not show.

Note that areaServed here is one honest city. If you work from a single address but serve a wider region, name the region you genuinely cover and no more.

Add It and Compare It With the Page Copy

Place the script on the page it describes, in the HTML head or body. Google’s general structured data guidelines say markup should represent the page’s content and must not describe content hidden from readers or mislead them. A script block does not replace readable service information.

  1. Write and publish the service copy first, so the page stands on its own.
  2. Paste the JSON-LD into the same page. If you manage a CMS, the article on adding JSON-LD in WordPress compares plugin, theme and manual approaches.
  3. Read the markup against the page. Check the name, scope, provider, area and description.
  4. Remove anything the page does not substantiate, including services, locations, prices and reviews.
  5. When the offer changes, update the page and the markup together.

A mismatch between markup and page is the most common mistake. It usually happens after a redesign or a price change, when someone edits the copy and forgets the script.

Verify With View Page Source, Spider Simulator and a Validator

Verification means confirming that the markup is in the HTML a crawler fetches and that readable service copy exists next to it. Use the exact public URL for every step.

  1. Open View Page Source for the URL and search for application/ld+json. Confirm the expected name, serviceType, provider and areaServed appear in the returned HTML.
  2. Run the same URL through the Spider Simulator. It shows the title, meta description, headings, internal links and text as a crawler reads them. Compare the headings and text it shows with the source, so the service description exists for readers as well as inside the script.
  3. Check the JSON-LD with the Schema Markup Validator. Its description says it checks JSON-LD syntax and key properties, lets you paste code or fetch a URL, and lists errors and warnings. I have not confirmed how it handles the Service type specifically, so treat its result as a syntax check.
  4. For extraction and syntax issues against the full vocabulary, also run the page or code through Schema.org’s own Markup Validator.

These AllEasySEO tools inspect fetched HTML. If they do not show markup that is injected by JavaScript, that alone does not prove Google cannot render it, but it does tell you the markup is not in the initial HTML. Google’s Rich Results Test is built for supported Google rich-result features, so a message about unsupported rich results is not proof that the Service vocabulary is invalid.

Can One Page Describe Multiple Services?

Yes, when the page genuinely explains several distinct services. Describe only the services a visitor can find there, and make each entity’s name and description distinguishable. If the page is centered on one service, lead with that one rather than adding an indiscriminate catalogue.

This is an editorial recommendation, not a Google limit on the number of Service entities. Google’s general guidance is to put markup on the page it describes and make it representative of the page’s main content. If you offer ten services, ten focused pages with one Service each are usually clearer than one page carrying ten entities.

What Service Markup Cannot Guarantee

As checked on November 13, 2026, Google’s supported structured data gallery does not list a dedicated Service rich-result feature. Valid Service markup can describe an offer, but it does not guarantee a special search display, indexing, a ranking improvement or traffic. Google also says that even correctly marked-up pages are not guaranteed rich results.

The documentation is living, so check Google Search Central and Schema.org again before relying on any of this. Treat the markup as a clear, honest description of the page and nothing more.

Frequently asked questions

What is the difference between service schema markup and a schema markup service?

Service schema markup is structured data you add to a page to describe a service you offer. A schema markup service is a paid provider who writes structured data for you. You can hire help, but you still need the markup to match your page and to check the output yourself.

Should I use Service, Product or LocalBusiness?

Use Service for the work you offer, Product for a product page and LocalBusiness for details about a business or location, such as address and hours. Service and LocalBusiness can coexist when both describe the page accurately. Do not label a service as a Product to chase product features.

Can I mark up multiple services on one page?

You can when the page genuinely explains several distinct services. Describe only what visitors can find there and give each entity a distinguishable name and description. For a page about one service, lead with that service. This is an editorial recommendation, not a stated Google limit.

Where do I put the JSON-LD script?

Place it on the page it describes, in the HTML head or body. Google recommends JSON-LD, but the script does not replace readable service information. Visitors should find the same service details in the visible copy, so make sure both agree.

Do I have to fill in areaServed?

No. Include areaServed only when it reflects genuine geographic coverage. If the service is not tied to a place, or you are unsure of your coverage, omit it. Never add extra locations just to appear relevant in more searches.

Will Service markup give me a rich result?

Not necessarily. As checked on November 13, 2026, Google’s supported structured data gallery does not list a dedicated Service rich-result feature. Valid markup describes the offer, but it does not guarantee a special display, indexing, ranking improvement or traffic.

What should I do after adding the markup?

Confirm it appears in the raw HTML with View Page Source, compare it with the page text in the Spider Simulator and run a validator for syntax. Then recheck whenever the offer, provider or coverage changes, and update the page and markup together.

Next steps

Service schema markup is a short, honest description of one service: its name, type, provider, area served and a summary that matches the page. Write the visible copy first, add the JSON-LD to the same page, then check it in the page source, a crawler view and a validator. For the next step, the Schema Markup Generator can build JSON-LD for the types its form offers, so check its type list before assuming it has a dedicated Service form. If it does not, adapt the example above by hand and verify it the same way. Whatever you do, update the page and markup together whenever your offer changes.

Related tools and resources on AllEasySEO:

Sources and further reading

Try these free SEO tools

Free, browser-based and no signup needed.

See all free SEO tools