Schema.org structured data explicitly detailing a specific service offered, the provider, pricing models, and service area.
Service schema uses Schema.org’s Service type to describe an offered service and relevant relationships. It can identify the provider, the geographic area served and associated offers or catalogs. The chosen properties should reflect the service actually explained on the page.
This is distinct from describing the business itself with LocalBusiness or Organization. A provider may offer several different services, each with its own scope and conditions. Keep those relationships clear instead of treating every service as a separate physical business location.
A Schema.org type’s existence does not establish that Google offers a dedicated rich result for it. Markup can be syntactically valid without producing a special search appearance. Do not infer a ranking boost or invent pricing details merely to populate more fields.
Takeaway: Use service markup as an accurate description of the offer. Keep it aligned with the visible scope, provider and genuine coverage rather than treating it as a promise of search features.
Example
A cleaning company describes a scheduled office-cleaning service with a defined coverage area. Its structured data can identify that service and the company providing it. If every job requires a quote, the company should not insert a fabricated fixed price to make the markup look complete.
What to check
Review the vocabulary’s expected property types and any separate search-feature rules. Update the data when the offer changes. A validator can check structure, but someone still needs to confirm that the service claims are true.
For more detail, see Schema.org Service.