How should departments with different details be nested in LocalBusiness?

Definition: A department is a nested business object inside a parent local business. When a department has details that differ from the main store, such as its opening hours or telephone number, place those details on that department object.

Key facts

• Google's Local Business structured data documentation says to use one element in the department property for each department.
• Google says that properties differing from the main store are defined individually in the respective department element.
• Google describes department as a nested item for a single department and allows any property from its LocalBusiness table on that item.
• Schema.org defines department as a relationship between an organization and one of its departments, with examples that include a store with a pharmacy and a bakery with a cafe.
• Google names JSON-LD as its general recommendation when the site's setup allows it, while its documentation says that the three supported formats are acceptable when valid and properly implemented.

What belongs in the parent object?

The parent object describes the main business location. Google’s example uses @type Store, gives the store its name, address, geographic coordinates, URL, price range, telephone number, and opening hours, then adds a department array. The parent retains facts that describe the store as a whole. A department object is a nested LocalBusiness item, so it can carry the properties that describe that department.

Google’s example starts the relationship like this:

{
  "@context": "https://schema.org",
  "@type": "Store",
  "name": "Dave's Department Store",
  "department": [
    {
      "@type": "Pharmacy",
      "name": "Dave's Pharmacy"
    }
  ]
}

The same page identifies the nested type as LocalBusiness, while its example uses the more specific Pharmacy type.

How should different department details be represented?

Give each department its own object inside the parent’s department array. Put a department-specific telephone number, opening-hours specification, price range, image, address, or other supported property inside that object when it differs from the main store. Google’s full example gives the pharmacy its own telephone number and opening hours, including weekday and weekend schedules.

The department name follows Google’s naming guidance. For a department that is not separately branded, include the store name and department name in the form {store name} {department name}, such as gMart Pharmacy. If the department name is explicitly branded, Google gives Geek Squad as a name by itself alongside Best Buy as the store name. Schema.org adds that a department relationship can allow different URLs, logos, and opening hours.

What should you check before publishing?

Keep the markup on the page to which it applies. Google’s structured data introduction says that in-page structured data describes that page and says not to add information that is not visible to the user. The Local Business documentation requires the required properties for eligibility for a rich result and presents recommended properties as additional information.

Use valid JSON-LD or another supported format, then test the result with Google’s Rich Results Test. For each department, compare the object with the department’s visible name, contact details, address, and hours. Google’s guidance favors complete and accurate recommended properties over a larger set of incomplete or inaccurate ones.

Related terms

• Structured data
• JSON-LD
• Organization structured data

FAQ

Should every department repeat the main store’s properties?

No. Google says to define properties that differ from the main store in each department element. Repeat a property when the department’s own markup needs to state that department detail, such as its telephone number or opening hours.

Can a department have its own opening hours?

Yes. Google explicitly uses opening hours as an example of a distinct department property, and its department example gives the pharmacy its own openingHoursSpecification values.

Should the department name include the store name?

For a department without an explicitly branded name, Google specifies the store name followed by the department name. An explicitly branded department can use its department name by itself.

Sources

1. Google Search Central, "Local business (LocalBusiness) structured data", 8 September 2026
2. Google Search Central, "Intro to structured data markup in Search", 10 December 2025
3. Schema.org, "LocalBusiness", undated

---

Check how a page reads to answer engines. Open the GEO score analyzer