Websites · 10 min

Service Schema Markup: JSON-LD Examples for serviceType, areaServed and Offers

Service schema markup examples in valid JSON-LD: serviceType, areaServed, offers and hasOfferCatalog, plus how to validate them. Copy the code now.
Service Schema Markup: JSON-LD Examples for serviceType, areaServed and Offers
On this page

Service schema markup is a JSON-LD block that describes one service on your page using the schema.org Service type: what it is (serviceType), who provides it (provider), where it is available (areaServed) and what it costs (offers). Below are five copy-paste examples, from a minimal block to a full @graph with a price range and an offer catalog, plus how to validate them. One honest note first: Google has no Service rich result, so this markup describes your business to machines; it does not add stars or prices to your listing.

This reference is for developers, SEO specialists and business owners who maintain service pages (agencies, clinics, contractors, consultancies, training providers) and want markup they can paste and adapt. If you would rather have the markup, the page structure and the content planned together, that is part of NourSky’s SEO and GEO service.

What is service page schema?

Service page schema is structured data that tells search engines and AI systems “this page is about a service, offered by this organization, in these places”. Schema.org defines Service as “A service provided by an organization, e.g. delivery service, print services, etc.” The schema.org Service page lists 22 properties defined directly on the type, from areaServed and audience to termsOfService, plus everything inherited from Thing such as name, description and url.

Which type to put on which page (Organization on the home page, LocalBusiness for a physical branch, Service for each service page) is covered in our practical guide to schema markup for service businesses. This article only deals with the Service block itself.

Which Service properties matter most?

You do not need all 22. These are the ones that carry real information on a typical service page:

Property Expected type (schema.org) What to put in it
name Text The service name as it appears in the page heading
serviceType Text or GovernmentBenefitsType The general category, e.g. “Commercial cleaning” or “Dental implants”
provider Organization or Person Your Organization or LocalBusiness, ideally referenced by @id
areaServed AdministrativeArea, GeoShape, Place or Text Cities, countries, regions or a radius
offers Offer or Demand Price or price range, currency, link
hasOfferCatalog OfferCatalog The packages or sub-services under this service
audience Audience Who it is for, e.g. businesses or homeowners
availableChannel ServiceChannel How it is delivered or booked (phone, online, on site)

Two details people often miss. First, schema.org defines serviceType as “The type of service being offered”, and it is only used on Service, so it belongs on the Service block, not on your Organization. Second, according to the schema.org areaServed page, areaServed supersedes the older serviceArea property, so new markup should use areaServed.

What does a minimal Service schema example look like?

Start here if you only want the essentials. Replace the example values with your own, and keep the text identical to what the page shows.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Commercial Deep Cleaning",
  "serviceType": "Commercial cleaning",
  "description": "Deep cleaning for offices, clinics and retail units, including floors, kitchens and washrooms.",
  "url": "https://www.example.com/services/commercial-deep-cleaning/",
  "provider": {
    "@type": "LocalBusiness",
    "name": "Example Cleaning Co.",
    "url": "https://www.example.com/",
    "telephone": "+966-11-000-0000",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "King Fahd Road",
      "addressLocality": "Riyadh",
      "addressCountry": "SA"
    }
  },
  "areaServed": {
    "@type": "City",
    "name": "Riyadh"
  }
}
</script>

If your business has no public address (an online consultancy, for example), use "@type": "Organization" for the provider instead of LocalBusiness, and drop the address.

How do you mark up areaServed: city, country or radius?

Schema.org accepts four kinds of value for areaServed: AdministrativeArea, GeoShape, Place or plain Text. AdministrativeArea has the subtypes City, Country, State and SchoolDistrict, which covers most service businesses. Use an array when you serve several places.

Several cities and a country

"areaServed": [
  { "@type": "City", "name": "Riyadh" },
  { "@type": "City", "name": "Jeddah" },
  { "@type": "City", "name": "Dammam" },
  { "@type": "Country", "name": "United Arab Emirates" }
]

A radius around your base

For mobile services (home visits, on-site repairs), a GeoCircle describes a radius. On the schema.org GeoCircle page, geoRadius is in metres unless you state another unit, so 30 km is 30000.

"areaServed": {
  "@type": "GeoCircle",
  "geoMidpoint": {
    "@type": "GeoCoordinates",
    "latitude": 21.5433,
    "longitude": 39.1728
  },
  "geoRadius": 30000
}

Only list places you actually serve and that the page mentions. A list of fifty cities in the markup that the page never names is exactly the mismatch Google’s guidelines warn about (more on that below).

How do you add offers and a price range to a Service?

Use offers with an Offer, and put the price inside a priceSpecification. For services that are quoted per project, minPrice and maxPrice on a PriceSpecification express a range. The schema.org PriceSpecification page asks for a full stop as the decimal separator and an ISO 4217 currency code such as “SAR” or “AED”, not a symbol.

"offers": {
  "@type": "Offer",
  "url": "https://www.example.com/services/commercial-deep-cleaning/",
  "priceSpecification": {
    "@type": "PriceSpecification",
    "minPrice": 800,
    "maxPrice": 2500,
    "priceCurrency": "SAR",
    "valueAddedTaxIncluded": false
  }
}

For hourly or monthly pricing, use UnitPriceSpecification, which adds unitText (a plain label such as “hour”) and unitCode (a UN/CEFACT code):

"offers": {
  "@type": "Offer",
  "priceSpecification": {
    "@type": "UnitPriceSpecification",
    "price": 150,
    "priceCurrency": "SAR",
    "unitText": "hour"
  }
}

If you do not publish prices on the page, leave offers out. Markup should not contain a price the visitor cannot see.

How do you list packages with hasOfferCatalog?

hasOfferCatalog holds an OfferCatalog, which is a list (itemListElement) of offers. Each offer points to a sub-service through itemOffered. The schema.org OfferCatalog page uses this exact pattern in its own cleaning-company example, and it also notes that hasOfferCatalog can sit on an Organization, a Person or a Service.

"hasOfferCatalog": {
  "@type": "OfferCatalog",
  "name": "Commercial cleaning packages",
  "itemListElement": [
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Office cleaning, weekly contract"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Post-renovation cleaning"
      }
    }
  ]
}

What does a complete Service JSON-LD example look like?

This is the version we would put on a real service page: an @graph with the Organization defined once under an @id, and the Service referencing it. The same Organization @id can then be reused on every service page, so all your services point to one entity.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "LocalBusiness",
      "@id": "https://www.example.com/#organization",
      "name": "Example Cleaning Co.",
      "url": "https://www.example.com/",
      "telephone": "+966-11-000-0000",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "King Fahd Road",
        "addressLocality": "Riyadh",
        "addressCountry": "SA"
      },
      "sameAs": [
        "https://www.linkedin.com/company/example-cleaning"
      ]
    },
    {
      "@type": "Service",
      "@id": "https://www.example.com/services/commercial-deep-cleaning/#service",
      "name": "Commercial Deep Cleaning",
      "serviceType": "Commercial cleaning",
      "description": "Deep cleaning for offices, clinics and retail units, including floors, kitchens and washrooms.",
      "url": "https://www.example.com/services/commercial-deep-cleaning/",
      "provider": { "@id": "https://www.example.com/#organization" },
      "audience": {
        "@type": "BusinessAudience",
        "audienceType": "Offices, clinics and retail businesses"
      },
      "areaServed": [
        { "@type": "City", "name": "Riyadh" },
        { "@type": "City", "name": "Jeddah" }
      ],
      "offers": {
        "@type": "Offer",
        "url": "https://www.example.com/services/commercial-deep-cleaning/",
        "priceSpecification": {
          "@type": "PriceSpecification",
          "minPrice": 800,
          "maxPrice": 2500,
          "priceCurrency": "SAR"
        }
      },
      "hasOfferCatalog": {
        "@type": "OfferCatalog",
        "name": "Commercial cleaning packages",
        "itemListElement": [
          {
            "@type": "Offer",
            "itemOffered": { "@type": "Service", "name": "Office cleaning, weekly contract" }
          },
          {
            "@type": "Offer",
            "itemOffered": { "@type": "Service", "name": "Post-renovation cleaning" }
          }
        ]
      }
    }
  ]
}
</script>

Two choices in this example are deliberate. sameAs points to profiles on other sites, which Google’s Organization structured data documentation recommends to help it tell your organization apart from others. And the provider is a LocalBusiness; Google’s local business documentation advises using “the most specific LocalBusiness sub-type possible”, so a dental clinic would use Dentist rather than the generic type.

Should you use ProfessionalService for a service business?

No. Many tutorials still recommend it, but the schema.org ProfessionalService page now says the general type “was deprecated due to confusion with Service”. Describe the business with the most specific LocalBusiness subtype that fits (LegalService, AccountingService, Dentist and so on) or with Organization, and describe each offering with Service.

Does Google show a rich result for Service schema?

No. Google’s structured data search gallery lists the markup types that can produce search features (Article, Breadcrumb, Event, Local business, Organization, Product, Review snippet, Video and others), and Service is not among them. Even for supported types, Google is clear in its structured data general guidelines:

“Using structured data enables a feature to be present, it does not guarantee that it will be present.” (Google Search Central)

So why add it? Because the markup still does useful work:

  • It states the facts explicitly. Service name, category, provider, cities and price range are given as data instead of being inferred from layout. That helps search engines and AI assistants match the page to queries such as “commercial cleaning in Jeddah”.
  • It connects your pages. Each Service points to one Organization @id, which ties your services to the same entity that your Organization markup describes.
  • It carries supported types with it. The same page can also hold BreadcrumbList or LocalBusiness markup, which do appear in the gallery.

Where rich results do apply, the effect can be measurable. Google’s introduction to structured data cites Rotten Tomatoes measuring a 25% higher click-through rate on pages with structured data, Food Network seeing a 35% increase in visits, and Nestlé reporting an 82% higher click-through rate for pages shown as rich results. Those figures are for supported features, not for Service markup, so treat them as context rather than a forecast.

How do you validate Service schema markup?

Use both of Google’s recommended tools, because they answer different questions. According to Google’s testing page, the Rich Results Test shows “which Google rich results can be generated”, while the Schema Markup Validator checks “all Schema.org-based structured data” without Google-specific warnings.

  1. Check the JSON syntax. A missing comma or a trailing comma breaks the whole block. Paste it into any JSON linter first.
  2. Run the Schema Markup Validator (validator.schema.org). This is the tool that tells you whether your Service block is read correctly: types, properties and nesting.
  3. Run the Rich Results Test on the live URL. For a Service block it will usually report no eligible rich result. That is expected; use it to check the other types on the page, such as Breadcrumb or LocalBusiness.
  4. Compare markup with the visible page. Google’s guidelines say “Don’t mark up content that is not visible to readers of the page.” Every name, city and price in the JSON-LD should appear in the page text.
  5. Watch Search Console after publishing for structured data reports on the supported types.

What are the most common Service schema mistakes?

  1. One Service block for all services. Each service page gets its own Service with its own name and url.
  2. Prices that are not on the page. If the visitor cannot see the price, it should not be in offers.
  3. Using serviceArea instead of areaServed, or listing every city in the country when the page names three.
  4. Currency symbols (“SR”, “$”) instead of ISO 4217 codes (“SAR”, “USD”).
  5. Duplicated Organization data with different names or phone numbers on each page. Define it once with an @id and reference it.
  6. Translated markup that does not match. On bilingual sites the Arabic page needs Arabic values in its own markup, not the English block copied over. Our notes on Arabic RTL web design bugs cover other problems that appear when one template serves both languages.

Service pages that search engines and AI can read

NourSky plans service pages, their content and their structured data together, for Arabic and English sites in Saudi Arabia, the UAE and the Gulf.

Talk to our team →

Frequently asked questions

What is the difference between serviceType and name in Service schema?

name is the name of your specific service as shown on the page, such as “Commercial Deep Cleaning”. serviceType is the general kind of service it belongs to, such as “Commercial cleaning”. Several services can share one serviceType.

Can I put Service schema on my home page?

You can, but it is usually clearer to put Organization markup on the home page and one Service block on each service page, so each URL describes one thing. Google’s Organization documentation suggests the home page or an about page for Organization markup.

Is Service schema the same as LocalBusiness schema?

No. LocalBusiness describes the business itself, including its address and opening hours, and can produce a Google search feature. Service describes one offering of that business and has no rich result of its own. On a service page they work together: the Service names the LocalBusiness as its provider.

Keep reading

More from Insights.

Property Management CRM in Saudi Arabia: What Landlords and Managers Need
CRM & Sales · 8 min
What a property management CRM in Saudi Arabia should hold, how it works alongside Ejar, and how to handle renewals, WhatsApp rent reminders and owner reports.
AI Workflow Automation in Saudi Arabia: What to Automate First
AI Agents · 8 min
Which AI workflows pay back first for Saudi businesses, what to keep human, WhatsApp and PDPL basics, and the questions to ask an automation partner.
WhatsApp AI Agent for Quotes: Collect Details, Send Estimates, Hand Off to Your Team
AI Agents · 9 min
How a WhatsApp AI agent collects details, quotes only from your approved price table, and hands serious enquiries to your team with the context attached.
Ready when you are

Reading helps. A working system helps more.

Tell us where inquiries slip through today. You leave the call with a clear next step, not a sales pitch.