complex JSON-LD nesting for multiple locations?

Author
Mason Moore Author
|
18 hours ago Asked
|
10 Views
|
1 Replies
0

we're trying to implement schema for a client with dozens of physical locations, each needing its own NAP details.

what's the most robust way to structure LocalBusiness JSON-LD for this? shud we nest multiple LocalBusiness types under one main Organization, or is it better to create separate top-level Organization entries for each branch?

local seo schema json-ld structured data

1 Answers

0
Valentina Sanchez
Answered 12 hours ago
I've dealt with multi-location schema implementations many times, and getting it right for dozens of branches can certainly be a complex task. The most robust and recommended way to structure your JSON-LD for multiple physical locations is to nest multiple LocalBusiness types under one main Organization. Creating separate top-level Organization entries for each branch would imply they are distinct, unrelated businesses, which dilutes the overall brand authority and can confuse search engines regarding the corporate structure. Here's how to approach this for effective local search visibility:
  • Define the Main Organization: Start by defining your overarching Organization. This block should contain details common to the entire company, such as its official name, main website url, and sameAs links to primary social media profiles. Assign an @id to this organization for easy referencing from its branches. 
    {
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.yourclient.com/#organization",
  "name": "Client's Main Company Name",
  "url": "https://www.yourclient.com",
  "sameAs": [
    "https://www.facebook.com/client",
    "https://twitter.com/client"
  ]
}
  • Implement Individual LocalBusiness Schema: For each physical location, you will create a separate LocalBusiness schema object. Ideally, each of these should reside on its dedicated location page (e.g., yourclient.com/locations/city-a).
    • Unique Details: Each LocalBusiness block must contain its specific details: a unique name (e.g., "Client's Company Name - City A Location"), the url pointing to its dedicated location page, its full PostalAddress, telephone number, geo coordinates (latitude and longitude), and precise openingHoursSpecification.
    • Link to Parent Organization: Crucially, within each LocalBusiness schema, use the branchOf property to explicitly link back to your main Organization using its @id. This clearly communicates the parent-child relationship to search engines. 
      {
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://www.yourclient.com/locations/city-a/#localbusiness",
  "name": "Client's Company Name - City A Location",
  "url": "https://www.yourclient.com/locations/city-a",
  "image": "https://www.yourclient.com/images/city-a-storefront.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "City A",
    "addressRegion": "State A",
    "postalCode": "12345",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": "XX.XXXX",
    "longitude": "YY.YYYY"
  },
  "telephone": "+1-123-456-7890",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "17:00"
    }
  ],
  "branchOf": { "@id": "https://www.yourclient.com/#organization" }
}
  • Consolidated Schema (If Necessary): If you must include schema for all dozens of locations on a single page (e.g., a "Locations" directory page or the homepage), you can combine these into an @graph array. This array would contain the main Organization object and then each individual LocalBusiness object, all referencing each other via their @ids and the branchOf property.
  • NAP Consistency: Beyond schema, ensure absolute NAP (Name, Address, Phone) consistency across all online platforms: Google My Business profiles, Yelp, industry directories, and your website content. This is a critical factor for local SEO.
  • Validation: Always validate your structured data implementation using Google's Rich Results Test and the Schema.org Validator. This helps catch any errors before deployment.
This approach provides clear hierarchical signals to search engines, reinforcing the relationship between the parent company and its individual branches. What's your current strategy for managing the individual location pages and their Google My Business profiles?

Your Answer

You must Log In to post an answer and earn reputation.
Hot Discussions
1
2
3
4
5