Service Schema
Service schema is the Schema.org type that declares a page is about a service offered by a provider. Required for service-business sites to enable rich results, AI Overview citation, and accurate entity disambiguation. Wired with name, description, provider, areaServed, serviceType, and pricing properties.
Also called: Service JSON-LD, Schema.org Service · Last updated: May 27, 2026 · By Joseph W. Anady
Why it matters.
Service schema converts a service page from generic text into a structured entity Google and AI engines can extract precisely. The schema declares: this is a Service named X, offered by Organization Y, in geographic area Z, with pricing tier W. This precision enables search engines to surface your service for buyer-intent queries that match the structured properties.
How it works.
Service schema lives in a JSON-LD block on each service-specific page. Required: @context, @type, name. Recommended: description, provider (with @id to Organization), areaServed, serviceType, offers (with PriceSpecification), audience, hasOfferCatalog. Often combined with FAQPage and BreadcrumbList in the same page.
2026 reality check.
Service schema is required for AI Overview citation on service-intent queries ('how much does X cost', 'who provides X near me', 'best X for Y'). Pages without Service schema compete at a disadvantage. AI engines use the structured properties (areaServed, serviceType, offers) to match buyer queries to relevant providers.
Data points
- Schema.org Service documented at https://schema.org/Service
- Subtypes include GovernmentService, ProfessionalService, FinancialProduct, etc.
- Required for AI Overview citation on service-intent queries
- AI engines extract areaServed, serviceType, and offers for buyer-query matching
- Service + Organization + Person + BreadcrumbList is the typical service-page schema stack
First-hand insight from ThatDeveloperGuy.
ThatDeveloperGuy uses Service schema on 9 service pages (web development, SEO, AEO, AIO, GEO, schema markup, mobile app development, section 508 compliance, plus 5 Tier-4 service expansions like website redesign, migration, maintenance, ada-compliance, small-business-websites). Each Service schema references the TDG Organization via @id, declares areaServed United States, includes pricing tiers as offers, and lists audience type. Pages with proper Service schema rank higher for service-intent queries in our internal testing.
How TDG approaches it
TDG's Service schema includes specific serviceType matching NAICS codes (541511 Custom Computer Programming Services, 541512 Computer Systems Design Services), areaServed United States, audience BusinessAudience or ConsumerAudience, hasOfferCatalog with all pricing tiers, provider @id reference to main Organization. Cross-referenced via BreadcrumbList for navigation context.
Common mistakes.
- Missing provider reference (must @id to Organization, not duplicate Organization properties)
- Skipping areaServed (Google can't surface for geographic queries without it)
- Vague serviceType (use specific values like 'Custom Computer Programming' not 'Programming')
- Failing to include offers/pricing (AI Overview cites pricing for cost-intent queries)
- Missing audience (helps disambiguate B2B vs consumer)
FAQ.
Should I use Service or Product schema?
Service for intangible offerings (web development, consulting, legal advice). Product for tangible goods or SaaS subscriptions. Some hybrid offerings (web hosting) can use either; pick the dominant intent.
How specific should serviceType be?
Very. Use industry-standard category names matching NAICS or SIC codes when applicable. 'Custom Computer Programming' beats 'Programming Services' beats 'IT Help'.
Do I need separate Service schema per pricing tier?
Not required. One Service with multiple offers in hasOfferCatalog is cleaner. Separate Services if tiers differ enough that they're functionally separate offerings.
Does Service schema help with Local Pack ranking?
Indirectly. Local Pack uses LocalBusiness schema. Service schema on service pages reinforces topical authority for the service, which improves ranking signals overall.
Can I combine Service + Offer + Audience?
Yes. Each Service can have multiple offers, each offer can declare different audience types (e.g., business vs consumer pricing). All schema-valid.
Maintained by Joseph W. Anady at ThatDeveloperGuy. Back to glossary · Suggest a term