serviceArea

serviceArea · Optional

Appears in

Organization

What is it?

serviceArea identifies the geographic region that an organization covers with its services. It was introduced specifically for Organization and LocalBusiness types to answer the question "where does this business operate?" in a machine-readable format.

Schema.org now marks serviceArea as superseded by the more general areaServed property. Both fields remain valid in markup, but areaServed is the preferred choice for new implementations. serviceArea accepts AdministrativeArea, GeoShape, and Place values, the same types as areaServed, minus plain Text.

Why this matters for AEO

AI answer engines parse geographic scope from Organization markup when responding to location-based queries. When a user asks "which electricians operate in Phoenix?" or "does this courier service reach rural areas?", a well-structured serviceArea or areaServed node gives the AI engine a verifiable geographic boundary rather than an inference from unstructured text.

Organizations that serve multiple cities or states but list only one physical address risk being associated exclusively with that location. Explicit service area markup corrects this by separating the concept of "where we are" from "where we serve."

What the specs say

Schema.org:serviceArea expects an AdministrativeArea, GeoShape, or Place value. The geographic area where the service is provided. [Source: https://schema.org/serviceArea]

Google: Not mentioned in Google's structured data documentation for Organization. Google does not list serviceArea as a required or recommended field for Organization rich results. [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]

serviceArea vs. areaServed

• Schema.org status — Superseded
• Types accepted — AdministrativeArea, GeoShape, Place
• Applies to — Organization, LocalBusiness
• Recommendation — Use for legacy compatibility only

For new implementations, use areaServed. For existing markup already using serviceArea, either leave it in place (it remains valid) or migrate to areaServed during the next schema update cycle.

How to find your value

Match your value type to the precision you need:

• Single city: Use a Place node with a name.
• State or province: Use AdministrativeArea.
• Country: Use AdministrativeArea or a text string (only with areaServed).
• Custom delivery radius: Use GeoShape with a circle definition.
• Irregular region: Use GeoShape with a polygon.

Format and code

AdministrativeArea (state-level)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "NV Energy",
  "serviceArea": {
    "@type": "AdministrativeArea",
    "name": "Nevada"
  }
}

Place (city or metro area)

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Priority Plumbing",
  "serviceArea": {
    "@type": "Place",
    "name": "Greater Boston Area"
  }
}

GeoShape (radius)

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "QuickSpark Electric",
  "serviceArea": {
    "@type": "GeoShape",
    "circle": "33.4484 -112.0740 30"
  }
}

The circle value format is latitude longitude radiusInMiles.

Multiple areas using an array

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "CareFirst BlueCross BlueShield",
  "serviceArea": [
    {
      "@type": "AdministrativeArea",
      "name": "Maryland"
    },
    {
      "@type": "AdministrativeArea",
      "name": "Washington, D.C."
    },
    {
      "@type": "AdministrativeArea",
      "name": "Virginia"
    }
  ]
}

Webflow implementation

Static pages

Add a <script type="application/ld+json"> block in Page Settings > Custom Code > Before </body>. Include serviceArea alongside other Organization fields. Text-based coverage values go directly in the JSON string. Place or AdministrativeArea nodes require nested object syntax.

CMS template pages

Store the area name in a Webflow CMS text field. In the CMS page template, use a custom code embed with dynamic field binding to inject the area name into your JSON-LD. For multiple service areas, store them as a comma-separated text field and handle splitting in client-side JavaScript or use multiple CMS fields.

In Schema HQ

The serviceArea field publishes areaServed (the successor field) in the Organization editor. If you have existing serviceArea values, map them to areaServed in Schema HQ. The tool writes clean JSON-LD to your Webflow site's custom code without requiring manual template editing.

Real examples

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Highmark Health",
  "url": "https://www.highmarkhealth.org",
  "serviceArea": [
    {
      "@type": "AdministrativeArea",
      "name": "Pennsylvania"
    },
    {
      "@type": "AdministrativeArea",
      "name": "West Virginia"
    },
    {
      "@type": "AdministrativeArea",
      "name": "Delaware"
    }
  ]
}

Related fields

• areaServed
• location
• address
• hasShippingService

FAQ

Is serviceArea still valid schema markup?

Yes. Schema.org marks it as superseded, not deprecated or removed. Validators will not flag it as an error. New implementations should use areaServed instead, but existing serviceArea markup does not need immediate replacement.

What is the difference between GeoShape circle and polygon?

A circle is defined by a center point (latitude and longitude) plus a radius in miles. A polygon is a sequence of latitude-longitude pairs that trace a boundary. Use circles for simple radius-based delivery zones; use polygons when your coverage area follows irregular boundaries like county lines or delivery districts.

Can serviceArea and areaServed both appear in the same Organization block?

Yes. You can include both in the same markup block, but this is redundant. Choose one, prefer areaServed for new work.