LocalBusiness Schema for Multi-Location Sites: A Practical JSON-LD Pattern
For a multi-location site, put one Organization node on the brand level, and one LocalBusiness node (or a more specific subtype) on each location page. Give every node a stable @id , link each location to the brand with parentOrganization , and make sure the address, phone, and hours in the markup match the visible page and the Google Business Profile exactly. That is most of it. The rest is…
For businesses with multiple locations, a LocalBusiness schema is essential to ensure accurate representation in search results. On the brand level, a single Organization node should be used, with an ID that remains consistent across all pages. Each individual location should have its own LocalBusiness node or a subtype, such as HardwareStore, Dentist, or Restaurant, which should be chosen based on the specific type of location.
This node should include unique identifiers (@id), the location's name, URL, phone number, address details, and geographical coordinates. It's important to maintain the same @id for the organization node on every location page to establish a connection between the locations and the brand. Additionally, the parentOrganization property should link back to the organization's ID.
By adhering to these guidelines and ensuring consistency between visible information and schema markup, businesses can effectively utilize the LocalBusiness schema for multi-location sites.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.