Service Schema Generator — Describe and Price Your Offering
Generate clean Service JSON‑LD for consulting, maintenance, and other offerings. Clarify provider, area served, and optional pricing to improve understanding.
Why many service pages underperform
Pain points we solve
- It’s unclear what the service includes or who provides it.
- No geographic context (area served) for where the service is available.
- Pricing is absent or inconsistently formatted, creating confusion.
- Manual JSON‑LD is error‑prone and hard to keep consistent across pages.
How SwiftSchema helps
Solution
The Service generator focuses on the essentials: name, serviceType, provider (Organization or Person), areaServed, and an optional Offer with price and currency.
It outputs copy‑ready JSON‑LD you can paste on service pages and works alongside LocalBusiness for location details or Product for packaged offers.
How it works
How it works
- Choose Service in the generator below.
- Enter service name and optional serviceType (e.g., Consulting, HVAC Repair).
- Add provider details (Organization or Person) and areaServed.
- Optionally include an Offer with price and priceCurrency.
- Copy JSON or Script, paste on the service page, and validate in the Rich Results Test.
Paste once per service. Validate. Ship.
What is Service structured data?
Service markup clarifies your service offerings. Include provider details and optional pricing; pair with LocalBusiness for location pages or Product for packaged offerings.
Use Service when:
- You describe an intangible offering (consulting, repair, maintenance, support, training, installation) rather than a physical product.
- You need to show who provides it (Organization/Person), where it’s available (areaServed), and optionally what it costs.
- You may also list it in a catalog alongside Products; Service keeps the intent clear.
Avoid Service when:
- The page is primarily selling a physical product (use Product, and optionally Offer/ServiceAddOn if bundling services).
- It’s user-generated Q&A (use QAPage) or a static FAQ (FAQPage).
- You cannot show the service on the page itself (hidden, gated, or unrelated content).
Eligibility & status
Service is a contextual type (“not direct”). It does not create its own rich result but improves understanding of what you offer. Pair it with:
- LocalBusiness on location pages to tie the business entity to the service.
- Organization on brand/service overview pages.
- Product if you package the service with a clear SKU/offer.
On-page parity checklist
- H1 and intro clearly name the service; the same name appears in name.
- Provider (brand or practitioner) is visible and matches provider.
- Service coverage or service area is stated on-page; matches areaServed.
- Pricing, if present, is visible and matches offers(including currency and units).
- Contact/CTA links on-page match any URLs in offers.urlorurl.
- Page is indexable with a self-referential canonical.
Property guidance (what to include)
- name (required): Plain, specific service name (“HVAC Tune-Up”, “SEO Consulting”).
- serviceType (recommended): Category/descriptor (e.g., “maintenance”, “analytics implementation”).
- description (recommended): Brief summary of what’s included.
- provider (recommended): @typeOrganization or Person withname; add URL/logo via Organization elsewhere on page or site-wide.
- areaServed (recommended): GeoCoordinates/GeoCircle for local radius; Place/AdministrativeArea/strings for regions/countries.
- offers (optional but useful): OfferwithpriceandpriceCurrency; orpriceSpecificationfor retainers/ranges. Addavailabilityif relevant.
- url (recommended): Canonical URL of the service page.
- inLanguage (optional): If localized, use locale tag.
JSON-LD examples
Minimal service with provider and price
{
"@context": "https://schema.org",
"@type": "Service",
"name": "SEO Consulting",
"serviceType": "Search engine optimization",
"provider": { "@type": "Organization", "name": "ACME Agency" },
"offers": {
"@type": "Offer",
"price": 150,
"priceCurrency": "USD"
},
"url": "https://www.acme.example/services/seo-consulting"
}
Local service with coverage radius
{
"@context": "https://schema.org",
"@type": "Service",
"name": "HVAC Tune-Up",
"serviceType": "HVAC maintenance",
"provider": {
"@type": "LocalBusiness",
"name": "BreezeRight HVAC"
},
"areaServed": {
"@type": "GeoCircle",
"geoMidpoint": { "@type": "GeoCoordinates", "latitude": 30.2672, "longitude": -97.7431 },
"geoRadius": 40
},
"offers": {
"@type": "Offer",
"price": "189",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.breezeright.example/services/hvac-tune-up"
},
"url": "https://www.breezeright.example/services/hvac-tune-up"
}
B2B consulting with retainer pricing
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Analytics Implementation",
"serviceType": "Web analytics setup and training",
"provider": { "@type": "Organization", "name": "DataNorth" },
"areaServed": "United States",
"offers": {
"@type": "Offer",
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "3000",
"priceCurrency": "USD",
"unitCode": "MON",
"name": "Monthly retainer (starting)"
},
"availability": "https://schema.org/InStock"
},
"url": "https://www.datanorth.example/services/analytics-implementation"
}
Implementation steps (detailed)
- Clarify scope: Define what’s included/excluded, where it’s offered, and who delivers it.
- Collect inputs: Service name, type, description, provider name/type, coverage area, pricing (if public), canonical URL.
- Generate JSON-LD: Use this generator; pick Service and fill the fields exactly as they appear on-page.
- Pair with entity markup: Ensure Organization/LocalBusiness markup exists (logo, contact info); link via provider.
- Place schema: One Service JSON-LD block per service page, in <head>or before</body>.
- Validate: Rich Results Test (even though it’s “not direct”) to confirm fields are read and structured.
- Publish and monitor: Watch for crawlability/indexability and keep content in sync with the page.
Common mistakes to avoid
- No currency with price: Always include priceCurrencywhen usingprice.
- Vague provider: Missing Organization/Person name; add it and keep consistent with on-page branding.
- Missing areaServed: Especially for local services; add geography to reduce ambiguity.
- Using Service for physical products: Use Product instead; Service can be used for add-on services.
- Stale pricing: If prices change, update both the page and JSON-LD.
- Hidden or mismatched content: Schema must match what users see; no hidden offers or geos.
Troubleshooting and validation
- Rich Results Test shows warnings: Check for missing priceCurrency, vagueprovider, or absentareaServedwhen geography matters.
- Conflicting entity data: Ensure Organization/LocalBusiness markup matches provider details (name, phone, URL).
- Indexing issues: Confirm the page is indexable; Service data won’t help if the URL is blocked.
- Geo ambiguity: Prefer GeoCircle or administrative area names over vague strings (“nationwide” is fine if true; otherwise specify states/regions).
Maintenance routine
- Update after pricing changes, new service areas, or rebrands.
- Revalidate after template changes to ensure JSON-LD still renders.
- Refresh lastReviewedafter substantial edits; keep provider and areaServed consistent with your footer/nav and business listings.
Required properties
name
Recommended properties
serviceTypedescriptionprovider.nameprovider.@typeareaServedoffers.priceoffers.priceCurrencyoffers.priceSpecification.priceoffers.priceSpecification.priceCurrencyoffers.availabilityurl
Minimal JSON-LD
{
"@context": "https://schema.org",
"@type": "Service",
"name": "SEO Consulting",
"provider": {
"@type": "Organization",
"name": "ACME Agency"
},
"offers": {
"@type": "Offer",
"price": 150,
"priceCurrency": "USD"
}
}FAQs
Service vs Product?Show
Use Service for intangible offerings. Use Product for physical goods.
Do I need a price?Show
Optional. Include an Offer with price and currency when possible.