Skip to main content
Back to glossary

Glossary

Service Schema

Schema.org

Service Schema

Service is a Schema.org type for describing an individual service: name, description, provider, price, and area served. It is more granular than ProfessionalService.

Why It Matters for GEO

Service schema allows you to list each distinct offering. AI engines can then cite a specific service ("GEO Audit") rather than your company in general.

When someone asks an AI "Where can I get a GEO audit done in France?" the AI needs to find a service, not just a company. Service schema creates a distinct, machine-readable entity for each offering you provide. This allows AI to match specific user queries to specific services — increasing the precision and relevance of citations you receive. Generic company mentions are less actionable for users than "Company X offers this exact service at this price range."

How to Optimize

  1. Create one page per main service
  2. Include a detailed description
  3. Add an Offer if pricing is available
  4. Link to the provider (Organization)

Example

{
  "@type": "Service",
  "name": "Full GEO Audit",
  "description": "25-point analysis...",
  "provider": {"@id": "#org"},
  "offers": {
    "@type": "Offer",
    "price": "500",
    "priceCurrency": "EUR"
  }
}

Practical Example

A digital marketing agency offers five distinct services: SEO audits, GEO optimization, content strategy, technical SEO, and schema implementation. Rather than one generic "Services" page, they create a dedicated page for each service with its own Service schema, price range, and description. When users ask Perplexity or ChatGPT for help finding specific services, the agency appears in results for each individual offering. Their citation rate across five query types is five times higher than a competitor who bundles everything on a single services page without individual schema.

Common Mistakes

  • One schema for all services: Bundling every service into a single Service entry makes the markup too vague to match specific queries. Each service should have its own entity and page.
  • No pricing information: Including at least a price range in the Offer property makes your service dramatically more useful to AI engines answering "how much does X cost?" type queries.
  • Missing the provider link: Without referencing the parent Organization via the provider property, the service entity is disconnected from your brand. AI cannot attribute it to your company.
  • Vague descriptions: "We offer digital marketing services" is not machine-actionable. "We provide GEO audits that analyze 25 technical and content signals to improve AI search visibility" gives AI specific, useful information to work with.