How does the Organization Schema reflect information about multi-location offices?

How does the Organization Schema reflect information about multi-location offices?

When an organization has multiple office locations, Organization Schema primarily reflects multi-location information by nesting address arrays, using the branchOf property to associate with the main organization, and clearly specifying the location type. Main organization address array: In the main Organization Schema, set the address field as an array containing multiple PostalAddress objects. Each object should fully fill in sub-properties such as streetAddress, addressLocality, addressRegion, and postalCode, corresponding to different office locations respectively. Branch office association: Create a separate Organization Schema for each independent branch office (it is recommended to set the type as BranchOffice), and point to the URL of the main organization through the branchOf property to clearly define the subordinate relationship and avoid information confusion. Supplementary location property: Use the location field to reference Place or PostalAddress type data, and additional details such as openingHours and telephone can be attached to enhance the contextual information of each location. It is recommended to use the JSON-LD format during implementation to ensure standardized address formats and verify through the Rich Results testing tool. For Schema optimization of multi-location organizations, complete hierarchical relationships and accurate address information help improve the clarity of information display in search results.

Keep Reading