Service Area Schema

Service Area
Business Schema

Schema for businesses that serve customers at their location rather than a fixed address.

Where to find it: LocalBusiness schema on homepage | areaServed property

What It Is

Service area businesses (SABs) — plumbers, electricians, cleaning services, lawn care companies — operate from a home base or office but serve customers at the customer's location. For SABs, the standard address-focused LocalBusiness schema needs modification: the address may be hidden, and the areaServed property defines the geographic territory the business serves. Key fields include areaServed (an array of Place, City, or AdministrativeArea entities), hasMap (a Google Maps service area URL), and serviceType.

Why It Matters

Service area businesses represent a large portion of most local agency portfolios — any trade or home services business qualifies. Without areaServed schema, Google must infer the service territory from unstructured content and GBP settings alone. With correctly implemented areaServed schema, Google has explicit, structured data defining exactly which geographic areas the business is eligible to serve — improving visibility for location-modified queries across the entire service territory.

Root Diagnostics

Common Causes

Understanding why this failure occurs is the first step to fixing it permanently.

Standard Address Schema on SABs

Implementing a full physical address schema on a home-based SAB — exposing the owner's home address and sending incorrect signals about where customers are actually served.

Missing areaServed Property

SAB schema that omits the areaServed property entirely, leaving Google without structured geographic territory data and relying only on unstructured page content.

GBP Service Area Mismatch

areaServed schema listing cities that aren't in the GBP service area settings — creating conflicting geographic signals that Google resolves by defaulting to the more conservative GBP setting.

Overly Broad Territory Claims

areaServed listing an entire state or region when the business realistically serves a much smaller area — reducing the credibility of the geographic signal.

Interactive Standard Operating Procedure

The Fix Blueprint (Interactive SOP)

Check off each step to monitor your implementation progress live!

Implementation Progress: 0% Completed (0/7)

1. Determine Address Visibility Status

Establish whether the business has a public-facing address (office, warehouse, retail location) or operates from a hidden address (home-based, no public storefront). This determines how to structure the address field.

2. Configure Address for Hidden-Address SABs

For businesses with no public address: populate only addressLocality (city), addressRegion (state), and addressCountry in the PostalAddress — omit streetAddress entirely. This is Google's recommended approach for home-based SABs.

3. Build the areaServed Array

List every city, county, or region the business actually serves. Use AdministrativeArea or City @types for each entry. Be precise — only list areas the business genuinely covers with reasonable response times.

4. Implement GeoShape for Radius-Based Service Areas

For businesses that define their service area as a radius rather than named locations: use GeoShape with a circle definition specifying center coordinates (the business location) and radius in meters.

5. Add serviceType or makesOffer Properties

Include the serviceType property listing the services offered, or use makesOffer to create structured service offering entities. This adds categorization depth beyond the @type alone.

6. Align GBP Service Area With Schema areaServed

Open GBP and compare the service area settings against the schema areaServed array. Every area listed in schema should also be in GBP settings — and vice versa. Mismatches create conflicting signals.

7. Validate With Rich Results Test

Test the schema with Google's Rich Results Test. The non-standard address format (no streetAddress) sometimes generates warnings — confirm these are warnings, not errors, and that the schema resolves correctly.

Tools

Google Business Profile
Free | Service area settings that must align with schema areaServed — the authoritative geographic territory declaration for GBP-integrated local rankings
Google Rich Results Test
Free | Validates SAB schema structure and confirms the non-standard address format resolves without critical errors
schema.org/areaServed
Free | Reference documentation for areaServed property types — AdministrativeArea, City, GeoShape, and Place options

Time to Fix

1–2 hours

Schema Build

30 minutes

GBP Alignment Check

Pro Tip

GBP service area and schema areaServed must tell the same story.

Google's local algorithm uses both the schema areaServed and the GBP service area settings to determine which geographic queries the business is eligible for. A business with schema areaServed listing Denver and Boulder but a GBP service area limited to Denver Metro only creates a conflicting signal — Google defaults to the more conservative GBP setting. Always configure both simultaneously and treat them as a single coordinated signal, not two independent settings.

Ep 3: NAP Consistency and Schema Alignment Ep 5: Opening Hours and Special Hours Schema

Service AreaBusiness Schema