How to Fix LocalBusiness Schema When Multiple Service Areas Overlap

By Ryan York•

Learn how to structure LocalBusiness schema for businesses with overlapping service areas to avoid confusion and errors in search results.

How Should You Structure LocalBusiness Schema for Overlapping Service Areas?

Businesses with multiple or overlapping service areas can run into issues with LocalBusiness schema. This guide explains how to structure your schema to avoid errors and ensure accurate search results.

Common Scenarios

  • Multiple locations serving the same city or region
  • Overlapping postal codes or service areas
  • Using the same @id for different locations

Example of a Problem

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "#location-1",
  "name": "Widget Repair",
  "areaServed": ["New York", "Brooklyn"]
}

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "#location-2",
  "name": "Widget Repair",
  "areaServed": ["Brooklyn", "Queens"]
}

Problem: Brooklyn is served by both locations, which can confuse search engines.

How to Fix

  • Use unique @id values for each location
  • Clearly define areaServed for each business
  • Avoid overlapping service areas if possible
  • If overlap is necessary, clarify in the business description

Best Practices

  • Validate your schema with Google's Rich Results Test
  • Use descriptive @id values (e.g., #nyc-location, #brooklyn-location)

Conclusion

Clear, non-overlapping service areas in LocalBusiness schema help search engines accurately represent your business locations.