Local Business Schema for Service Area Businesses

Local business schema is one of the most consequential schema types for service businesses, and one of the most consistently misimplemented. The mistakes are not subtle. Businesses claim service areas they do not actually cover. Addresses point to old offices. Phone numbers differ between the schema and the contact page. Opening hours are wrong by a season.

These are not technical schema errors. They are data accuracy failures. And they matter because Google and AI systems use local business schema as a primary trust signal for geographic relevance.

The critical difference between LocalBusiness and ServiceArea

Most service businesses are not retail businesses. They do not have a storefront that customers visit. They travel to clients, or they work remotely. This creates a structural schema problem: LocalBusiness schema is built around a physical address, but service area businesses primarily serve clients who are not at that address.

The correct approach is to use the areaServed property to define where you actually work, alongside the address property to define where your office is registered. These are different things and they should not be conflated.

Why address-only schema fails for service area businesses

A Munich-based employment law firm that serves clients across Bavaria cannot simply list their Munich office address and expect Google to understand they are relevant for searches from Nuremberg, Augsburg, or Regensburg. The areaServed property makes that explicit.

areaServed versus serviceArea — which to use

areaServed is the correct property for LocalBusiness schema on service businesses. serviceArea is a property of the Service type and is used at the individual service level. Use both for complete coverage: areaServed on the LocalBusiness block to define your operating geography, and serviceArea on individual Service blocks to specify geographic scope at the service level.

Full LegalService schema for a Munich firm

{
  "@context": "https://schema.org",
  "@type": "LegalService",
  "name": "Northside Legal GmbH",
  "image": "https://northside-legal.de/images/office.jpg",
  "url": "https://northside-legal.de",
  "telephone": "+49-89-123-4567",
  "email": "kontakt@northside-legal.de",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Maximilianstraße 35",
    "addressLocality": "Munich",
    "postalCode": "80539",
    "addressRegion": "Bavaria",
    "addressCountry": "DE"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 48.1374,
    "longitude": 11.5755
  },
  "areaServed": [
    {
      "@type": "State",
      "name": "Bavaria"
    },
    {
      "@type": "City",
      "name": "Munich"
    },
    {
      "@type": "City",
      "name": "Nuremberg"
    },
    {
      "@type": "City",
      "name": "Augsburg"
    }
  ],
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "18:00"
    }
  ],
  "priceRange": "€€€",
  "sameAs": [
    "https://www.linkedin.com/company/northside-legal-gmbh",
    "https://www.google.com/maps/place/Northside+Legal+GmbH",
    "https://www.anwalt.de/northside-legal"
  ],
  "hasMap": "https://maps.google.com/?q=Northside+Legal+GmbH+Munich"
}

openingHoursSpecification — getting it right

Opening hours are one of the most commonly drifted fields in local business schema. Businesses change their hours seasonally, update them for public holidays, or simply edit the website and forget the schema. The result is that schema hours conflict with the contact page hours, which conflict with the Google Business Profile hours.

For professional services firms that offer out-of-hours consultations or emergency availability, use separate OpeningHoursSpecification blocks for different day sets rather than trying to compress everything into one block.

geo coordinates — why they matter

The geo property with GeoCoordinates is more precise than an address string for AI systems trying to map your business to geographic queries. An address requires geocoding — a process that introduces potential error. Direct coordinates do not.

Get your coordinates from Google Maps (right-click on your location and select the coordinates). They should match your physical registered address, not a nearby landmark.

sameAs and name authority

The sameAs array is how AI systems cross-reference your entity against other data sources. Every entry in sameAs is a vote of confidence that your business identity is consistent and verifiable.

• LinkedIn company page URL (not a personal profile)
• Google Maps place URL for your registered business
• Industry directory listings (Anwalt.de for law firms, Berater.de for consultants, etc.)
• Wikidata entry if your firm has one
• Official chamber of commerce or professional association listing

In site scans we've run, firms with three or more active sameAs links show measurably stronger entity recognition in AI system responses compared to firms with none. The correlation is not causal proof, but the pattern is consistent.

Schema drift in local business schema

Local business schema drifts in predictable ways. Office moves are the most common cause — the new address goes on the contact page and Google Business Profile, but the schema keeps pointing to the old address for months. Phone number changes create the same problem.

A secondary drift pattern is areaServed expansion: the firm starts serving a new city or region, but the schema only lists the original service area. Machines continue to exclude the firm from queries in the new geography.

1. Add a LocalBusiness schema review step to your annual business review process. Check address, phone, hours, and areaServed against your current reality.
2. When you update your contact page or Google Business Profile, check whether local schema needs to be updated at the same time.
3. If you are expanding into new service areas, update areaServed before announcing the expansion publicly — not after.

For businesses with multiple locations, the complexity multiplies. See Multi-Location Schema Strategy for Service Businesses. Loopful monitors local schema fields for drift against live page content and fires alerts before mismatches become indexing problems.