areaServed
areaServed · Optional
Appears in
What is it?
areaServed describes the geographic region where a service or product is available. It answers the question "where does this business operate?" at the markup level, making coverage data machine-readable for search engines and AI systems.
Schema.org defines areaServed broadly: it applies to any service, offer, or organization. Unlike serviceArea, which is scoped specifically to Organization and LocalBusiness, areaServed can also appear on Offer, Demand, ContactPoint, DeliveryChargeSpecification, and several other types. For Organization markup, both fields can coexist, but areaServed carries the wider semantic scope.
Why this matters for AEO
When a user asks an AI assistant "which plumbers serve downtown Chicago?" or "is this shipping company available in Germany?", the AI pulls from structured data that includes geographic scope. An organization that marks up areaServed with a specific city, state, or country gives AI engines a direct, verifiable answer instead of forcing inference from unstructured text.
Local service queries account for a large share of voice search and AI answer traffic. Organizations that serve multiple regions but only have one website benefit from explicit areaServed markup because it decouples service coverage from the physical address. A law firm headquartered in Austin but licensed across Texas can state all served regions without ambiguity.
What the specs say
Schema.org:areaServed expects an AdministrativeArea, GeoShape, Place, or Text value. The geographic area where a service or offered item is provided. [Source: https://schema.org/areaServed]
Google: Not mentioned in Google's structured data documentation for Organization. Google does not currently list areaServed as a required or recommended field for the Organization rich result. [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]
areaServed vs. serviceArea
These two fields overlap significantly, and both are valid on Organization. The practical distinction:
areaServedis the broader property. It appears on many schema types and captures where a service, product, or offer is available.serviceAreais Organization-specific and scoped to the geographic region the organization serves. It is now marked as superseded byareaServedon schema.org.
Prefer areaServed. It has wider type coverage, broader tooling support, and schema.org formally lists serviceArea as superseded. When migrating from legacy markup that used serviceArea, replace it with areaServed.
How to find your value
- City-based local business — Text string or Place with address
- Regional service provider — AdministrativeArea (state, county)
- National operation — Text "US" or Country node
- Multi-country organization — Array of Text or AdministrativeArea nodes
- Delivery or logistics — GeoShape with polygon or radius
Text values work for simple cases. For programmatic consumption and disambiguation, use structured types like AdministrativeArea or Place.
Format and code
Simple text (minimum viable)
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Carvana",
"areaServed": "United States"
}
Array of text values
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Lush Cosmetics",
"areaServed": ["United States", "Canada", "United Kingdom", "Australia"]
}
AdministrativeArea (state)
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Pacific Gas and Electric",
"areaServed": {
"@type": "AdministrativeArea",
"name": "California"
}
}
Place (city)
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Molly Maid of Chicago",
"areaServed": {
"@type": "Place",
"name": "Chicago Metropolitan Area"
}
}
GeoShape (radius around a point)
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Dave's Plumbing",
"areaServed": {
"@type": "GeoShape",
"circle": "41.8781 -87.6298 50"
}
}
The circle value is latitude longitude radiusInMiles.
Webflow implementation
Static pages
Open Page Settings > Custom Code > Before </body> tag. Add a <script type="application/ld+json"> block with the Organization type and your areaServed value. For businesses serving a single region, hardcode the value as a text string or a typed node.
CMS template pages
If your site manages multiple service area pages through Webflow CMS, bind a text field named "Service Area" to the areaServed value. Use Webflow's custom code embed inside the CMS template with a dynamic binding: {{wf {"path":"service-area"} }}. For multi-value coverage, store a comma-separated list and parse it if needed via custom code.
In Schema HQ
The organization schema editor in Schema HQ exposes areaServed as a configurable field. Set it to a text value or a structured geographic type. Schema HQ writes the JSON-LD to Webflow's custom code slot automatically, and updates propagate to every page that inherits the org schema.
Real examples
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Consumers Energy",
"url": "https://www.consumersenergy.com",
"areaServed": {
"@type": "AdministrativeArea",
"name": "Michigan"
}
}
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "ASOS",
"url": "https://www.asos.com",
"areaServed": ["United Kingdom", "United States", "France", "Germany", "Australia"]
}
Related fields
FAQ
What is the difference between areaServed and serviceArea?
serviceArea is an older Organization-specific field that schema.org has marked as superseded by areaServed. Both express geographic coverage, but areaServed works across more types (Organization, Offer, ContactPoint, etc.) and is the recommended choice going forward.
Can areaServed hold multiple values?
Yes. Pass an array of text strings, AdministrativeArea nodes, or Place nodes. Mixing types in the array is valid. For example, an organization can list individual cities as Place objects and countries as text strings in the same array.
Does Google use areaServed for local search ranking?
Google has not documented areaServed as a ranking signal or rich result field for Organization. It may inform Knowledge Graph entries and AI-generated answers, but it is not a confirmed local SEO ranking factor. Implementing it is low cost and increases the precision of your structured data regardless of direct ranking impact.