Local Business Schema Markup: JSON-LD Multi-Location Guide

Structured data markup using Schema.org vocabulary in JSON-LD (JavaScript Object Notation for Linked Data) provides search engines with explicit, unambiguous semantic information regarding a company's physical address, geo-coordinates, operating hours, and service catalogs. For multi-location businesses, accurately structuring linked entity data prevents address cannibalization and elevates local map pack prominence.

1. Why JSON-LD Outperforms Microdata and RDFa

Google officially recommends JSON-LD over inline Microdata or RDFa attributes. JSON-LD scripts sit cleanly within an isolated <script type="application/ld+json"> block in the HTML document, entirely separated from presentational styling. This architectural separation prevents accidental markup destruction during frontend design overhauls and simplifies dynamic programmatic rendering.

2. Core Schema Properties for Local Business Entities

When defining a localized commercial entity, selecting the most specific schema subtype available (e.g., Plumber, Dentist, LegalService, or AutoRepair rather than the generic LocalBusiness) provides search algorithms with granular vertical signals:

@type: Highly specific commercial classification matching the organization's trade.
name: Exact legal name matching corporate records and Google Business Profile.
address: Fully populated PostalAddress object including streetAddress, addressLocality, addressRegion, postalCode, and addressCountry.
geo: Precise GeoCoordinates containing latitude and longitude coordinates with up to 6 decimal places of precision.
telephone: International E.164 formatted telephone number (e.g., +1-214-555-0199).
openingHoursSpecification: Structured array detailing exact opening and closing intervals by day of the week.

3. Complete JSON-LD Implementation Example for a Multi-Location Company

The following template illustrates how a parent corporation with multiple regional branches links child business units using the subOrganization property and unique URI fragments:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "HVACBusiness",
      "@id": "https://aoneinfo.com/locations/dallas/#business",
      "name": "Apex Climate Solutions Dallas",
      "url": "https://aoneinfo.com/locations/dallas",
      "logo": "https://aoneinfo.com/assets/img/logo.png",
      "image": "https://aoneinfo.com/assets/img/storefront-dallas.jpg",
      "telephone": "+1-214-555-0145",
      "priceRange": "$$",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "1420 Main Street, Suite 400",
        "addressLocality": "Dallas",
        "addressRegion": "TX",
        "postalCode": "75201",
        "addressCountry": "US"
      },
      "geo": {
        "@type": "GeoCoordinates",
        "latitude": 32.7767,
        "longitude": -96.7970
      },
      "openingHoursSpecification": [
        {
          "@type": "OpeningHoursSpecification",
          "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
          "opens": "07:30",
          "closes": "18:00"
        },
        {
          "@type": "OpeningHoursSpecification",
          "dayOfWeek": "Saturday",
          "opens": "08:00",
          "closes": "14:00"
        }
      ],
      "parentOrganization": {
        "@type": "Organization",
        "name": "Apex Climate Solutions Inc.",
        "url": "https://aoneinfo.com"
      },
      "hasMap": "https://maps.google.com/?cid=102938475612345",
      "sameAs": [
        "https://www.facebook.com/apexclimatesolutions",
        "https://twitter.com/apexclimate",
        "https://www.linkedin.com/company/apex-climate-solutions"
      ]
    }
  ]
}
</script>

4. Preventing Multi-Location Cannibalization with @id URIs

When search bots crawl enterprise domains managing dozens of branch locations, duplicate entity names often create semantic ambiguity. If both the Austin and Dallas branches share the corporate title "Apex Climate Solutions", Google's Knowledge Graph can merge their attributes, producing incorrect phone numbers on search result cards.

Resolving this requires assigning a persistent, distinct Canonical Entity URI (@id) to every physical branch. Appending a clean fragment identifier (such as #branch or #location) anchored to the branch landing page URL guarantees that each store operates as an independent node in Google's Knowledge Graph.

5. Schema Validation and Rich Results Testing Workflows

Before deploying schema updates to production environments, validate the JSON-LD payload across both canonical testing utilities:

Schema.org Validator: Verifies syntax compliance against standard vocabulary definitions, flagging missing parent objects or malformed data types.
Google Rich Results Test: Confirms whether Google recognizes the payload as eligible for rich SERP enhancements (such as star ratings, breadcrumbs, and business panels).
Search Console Enhancements Tab: Monitor weekly error reports under the "Merchant listings" or "Local business" diagnostic panels to identify newly deprecating schema parameters.

6. Dynamic PHP Generation for Scale

Avoid hardcoding static JSON-LD tags into templates. Instead, fetch location metadata from your relational database and dynamically serialize it via PHP's native json_encode() function:

<?php
// dynamic_schema.php - Render validated JSON-LD from database records
$location_data = [
    '@context' => 'https://schema.org',
    '@type'    => $location['schema_type'],
    '@id'      => $location['canonical_url'] . '#store',
    'name'     => $location['name'],
    'url'      => $location['canonical_url'],
    'telephone'=> $location['phone_formatted'],
    'address'  => [
        '@type'           => 'PostalAddress',
        'streetAddress'   => $location['address_street'],
        'addressLocality'  => $location['city'],
        'addressRegion'    => $location['state_code'],
        'postalCode'       => $location['zip'],
        'addressCountry'   => 'US'
    ],
    'geo' => [
        '@type'     => 'GeoCoordinates',
        'latitude'  => (float)$location['latitude'],
        'longitude' => (float)$location['longitude']
    ]
];

echo '<script type="application/ld+json">' . 
     json_encode($location_data, JSON_UNESCAPED_SLASHES | JSON_PRETTY_PRINT) . 
     '</script>';
?>

7. Modeling Complex Opening Hours and Holiday Exceptions

Many commercial establishments operate with seasonal shifts, lunch closures, or emergency after-hours dispatch. Schema.org supports nested OpeningHoursSpecification arrays to explicitly model these conditions:

"openingHoursSpecification": [
  {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "08:00",
    "closes": "12:00"
  },
  {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "13:00",
    "closes": "17:30"
  },
  {
    "@type": "OpeningHoursSpecification",
    "validFrom": "2026-12-24T00:00:00",
    "validThrough": "2026-12-25T23:59:59",
    "opens": "00:00",
    "closes": "00:00"
  }
]

8. Debugging Common Google Search Console Schema Validation Errors

When monitoring Search Console structured data reports, three errors frequently occur on multi-location websites:

Missing field 'priceRange': Google expects a relative indicator (e.g., "$$" or "$$$") describing commercial affordability. Always provide this field to avoid warning flags.
Missing field 'hasMap': Link directly to your verified Google Maps share URL containing your unique CID identifier.
Invalid geo coordinate formatting: Ensure latitude and longitude values are passed as floating-point numeric values rather than string literals with non-standard compass characters.

9. Integrating GeoShape Polygon Boundaries for Service-Area Businesses

For contractors who travel to customer homes without maintaining a public walk-in showroom, define your operational radius using a GeoCircle or GeoShape specification:

"areaServed": {
  "@type": "GeoCircle",
  "geoMidpoint": {
    "@type": "GeoCoordinates",
    "latitude": 32.7767,
    "longitude": -96.7970
  },
  "geoRadius": "40000" // 40-kilometer radius boundary around Dallas city center
}

10. Server-Side Rendering (SSR) of Schema in Single Page Applications (SPA)

Client-side rendered Single Page Applications (built on React, Vue, or Angular) often defer the execution of JSON-LD scripts until after client JavaScript bundles hydrate. If a search engine crawler renders the initial HTML snapshot without executing JavaScript, critical structured data can be completely missed.

To ensure infallible schema ingestion:

Server-Side Injection: Render the <script type="application/ld+json"> block directly within the server-rendered HTML response headers or <head> tag using Next.js metadata API or Nuxt useHead() composables.
Static HTML Verification: Test your pages by fetching them using curl or inspecting the raw HTML source (press Ctrl+U in Chrome) to verify that the complete JSON-LD markup is present in the raw stream before any client scripts run.
Dynamic Entity Graph Linking: Connect your LocalBusiness entity to employee author profiles using the employee and knowsAbout schema properties to cement authentic E-E-A-T credentials across technical topics.

11. Automated Schema Monitoring and CI/CD Quality Gates

To protect structured data from accidental regressions caused by code updates, incorporate automated schema testing directly into your continuous integration (CI) pipeline:

Automated Smoke Tests: Write Playwright or Cypress end-to-end integration tests that query the DOM for script[type="application/ld+json"] and validate that the output string successfully parses into a valid JSON object.
Google Search Console API Polling: Implement a weekly cron job utilizing the Search Console API to programmatically detect any spikes in structured data validation warnings or parsing syntax errors.
Dynamic Entity Synchronization: If your company updates operating hours or relocates a physical store, ensure your backend database automatically updates both the frontend schema scripts and downstream API syndication feeds simultaneously.

Local Business Schema Markup: Complete JSON-LD Implementation for Multi-Location Companies