Department Schema

Department and
Subdepartment Schema

Schema for businesses where different departments have different hours and contacts.

Where to find it: Hospital, university, large retail schema | Department property in LocalBusiness

What It Is

The Department property within LocalBusiness schema allows businesses with distinct operational departments — a hospital with emergency, radiology, and cardiology departments; a car dealership with Sales, Service, and Parts; a university with multiple schools — to communicate each department's individual hours, contact information, and location within the parent entity's schema. Schema type relationships: Hospital > department > Hospital or Physician or HealthClub; Automobile dealer > department > AutoRepair or AutoDealer.

Why It Matters

For complex organizations where different departments genuinely have different hours, phone numbers, and locations within the same building or campus, a single-entity schema provides incomplete information. Department schema gives Google structured data for each operational unit — enabling Knowledge Panel sections that display department-specific hours and contacts, improving the user experience for queries like 'hospital radiology hours' or 'car dealership service department phone number'.

Root Diagnostics

Common Causes

Understanding why this failure occurs is the first step to fixing it permanently.

Single Schema for Multi-Department Organizations

A hospital or car dealership with a single LocalBusiness schema — providing only the main reception hours and phone, leaving all department-specific information unstructured.

Department Pages Without Schema

Individual department pages exist on the website but have no schema — leaving Google to infer department information from unstructured page content.

Missing parentOrganization Links

Department schemas implemented without linking back to the parent entity — creating isolated schema blocks that Google can't connect to the parent organization's entity model.

Incorrect Department Type Selection

Using a generic type for departments that have specific applicable subtypes — an auto dealership service department should use AutoRepair, not a generic LocalBusiness.

Interactive Standard Operating Procedure

The Fix Blueprint (Interactive SOP)

Check off each step to monitor your implementation progress live!

Implementation Progress: 0% Completed (0/7)

1. Identify Businesses With Genuine Distinct Departments

Review the client portfolio for businesses that have multiple departments with separate contact information, hours, and operational identities — hospitals, large medical practices, car dealerships, universities, large retailers.

2. Build a Department Property Object for Each Department

Within the parent LocalBusiness schema, add a department property containing an array of department objects. Each department object includes: @type (most specific applicable type), name, telephone, and openingHoursSpecification.

3. Add URL to Each Department if a Dedicated Page Exists

If each department has its own page on the website, include the url property in the department object pointing to that page. This strengthens the department entity signal by connecting schema to content.

4. Create Dedicated Department Pages With Individual Schema

For departments substantial enough to have their own pages: implement standalone LocalBusiness or appropriate subtype schema on each department page in addition to the department object in the parent schema.

5. Link Parent and Department Schemas Bidirectionally

In the parent schema: reference departments via the department property. In each department's schema: reference the parent via parentOrganization. This bidirectional linking creates a coherent entity hierarchy.

6. Validate the Full Parent Plus Department Schema Structure

Paste the complete parent schema — including all department objects — into Rich Results Test. Validate each department page's schema separately. Confirm no errors in either the parent or department-level schemas.

7. Monitor Knowledge Panel for Department Information

After deployment, track the parent entity's Knowledge Panel in Google Search. Department information may begin appearing in expanded Knowledge Panel sections as Google processes the structured department data.

Tools

Google Rich Results Test
Free | Validates complex parent-department schema structures — test both the parent schema and each department page schema separately
schema.org/LocalBusiness
Free | Department property documentation and type hierarchy for identifying correct department @types
Google Search (Knowledge Panel monitoring)
Free | Monitor the parent entity's Knowledge Panel for department information appearing over time after schema deployment

Time to Fix

1–2 hours

Department Audit

2–4 hours

Schema Build & Validation

Pro Tip

Department schema is especially high-value for hospitals and medical practices.

Google's health-specific local features actively use Department schema to display which departments accept which types of appointments, what their individual hours are, and which physicians practice in each department. For healthcare clients in particular, department schema implementation is one of the highest-value schema deliverables — it directly improves the structured data that Google uses to power health-specific search features that drive patient appointment bookings.

Ep 6: Multi-Location Schema Architecture Ep 8: Google Business Profile and Schema Ali...

Department andSubdepartment Schema