Service identity
Unique identifier, usually your service page URL + #service.
Provider
Cities, states, regions, or country codes where this service is available.
What this service produces, each becomes a Thing in serviceOutput.
Offer catalog (service packages)
Individual sub-services that make up your complete catalog.
Main offer / pricing
Call-to-action (potentialAction)
Hours available (optional)
Other optional fields
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Service",
"hoursAvailable": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Monday",
"opens": "09:00",
"closes": "17:00"
}
]
}
</script>How to use
Define the service
Give the service an @id (your page URL plus #service), a name, and a short description, then pick one of the 18 service types or type a custom one instead.
Set provider, areas, and packages
Fill the Provider card, add each city or region as an Area served chip, and build your Offer catalog with Add service to catalog, one entry per package you sell.
Price it and copy
Optionally add a price, availability, booking URL, and a potentialAction such as ReserveAction, plus opening hours. Then press Copy script and place the JSON-LD on the service page.
Why Service Schema Generator
- Full Service schema with @id linkage, offer catalog, hours, CTA, brand, and provider.
- 18 ready-to-pick service types plus free-text override for niche offerings.
- Offer catalog generates a separate Service per package with its own description.
- Potential action (Reserve / Order / Quote) wraps your booking URL.