usdigitalmarketingindex.com SEO
How should a company with multiple offices distinguish Organization and LocalBusiness entities in schema?
Updated November 15, 2026
Describe the company once, as an Organization, on the home page or a single about page, and describe each office separately, as a LocalBusiness, on that office’s own page. The Organization entity carries what is true of the company as a whole: its legal name, logo, main website, and official profiles. Each LocalBusiness entity carries what is true of one place: its street address, its phone number, its opening hours. The branch entities then point back to the company with schema.org’s parentOrganization property, so the relationship is stated instead of implied. Every entity must correspond to something real. Markup for an office that does not exist, or identifiers invented to fill a field, misdescribe the business.
Legal organization identity
Google’s documentation for Organization markup says: “Adding organization structured data to your home page can help Google better understand your organization’s administrative details”, and that for this type “There are no required properties; instead, add the properties that apply” (Google’s Organization structured data documentation).
For the company-level entity, include what you can verify.
| Property | Content |
|---|---|
| name | The company's name as it trades |
| legalName | The registered name, if different |
| url | The main website |
| logo | The official logo |
| sameAs | Official profiles on other sites that the company controls |
| Identifiers such as vatID or iso6523Code | Only where the company holds them |
| contactPoint or telephone | A company-wide contact line, if one exists |
Place it on one page. The organization is described once, and other pages refer to it.
Branch-specific locations
Each office gets its own page and its own entity. Google’s LocalBusiness documentation lists two required properties, address and name, and advises using the most specific business type that fits (Google’s LocalBusiness structured data documentation).
| Property | Branch-level content |
|---|---|
| name | The branch's name as it is known, for example the company name with the location |
| address | The full postal address of that office |
| telephone | That office's number |
| openingHoursSpecification | That office's hours |
| geo | That office's coordinates |
| url | The URL of that branch's page |
| parentOrganization | A reference to the company entity |
One page, one location. A page listing every office in a table is a directory, and the markup for each office belongs on that office’s page.
Identifiers and phone rules
Three rules keep the entities distinct.
- Give each entity an @id, a stable URL-shaped identifier of your own choosing on your own domain. The company might be identified as its home page URL with #organization appended, and each branch as its page URL with #localbusiness. These identify the entity within your markup. They are not registrations with any outside body.
- Use real external identifiers only. sameAs lists pages that are about the same entity, such as the company’s official social profiles. A branch’s sameAs lists that branch’s own profiles, if it has any. Do not copy the company’s profiles onto every branch, and do not invent identifiers.
- Phones follow the entity. The company entity carries a head-office or central number. Each branch carries the number that reaches that branch. If every office shares one central number, state it on the company and repeat it on a branch only if it is what a customer of that branch should call.
Visible content must match. Google’s structured data guidelines say “Don’t mark up content that is not visible to readers of the page” (Google’s structured data general guidelines). The address, hours, and phone in a branch’s markup appear on that branch’s page.
Example entity graph
A company with two offices. All names, addresses, and numbers are placeholders.
On the home page:
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Northgate Plumbing",
"legalName": "Northgate Plumbing Ltd",
"url": "https://www.example.com/",
"logo": "https://www.example.com/images/logo.png",
"sameAs": [
"https://social.example.net/northgateplumbing"
]
}
On the Ashby office page:
{
"@context": "https://schema.org",
"@type": "Plumber",
"@id": "https://www.example.com/locations/ashby/#localbusiness",
"name": "Northgate Plumbing Ashby",
"url": "https://www.example.com/locations/ashby/",
"telephone": "+1-555-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "12 Mill Road",
"addressLocality": "Ashby",
"addressRegion": "OH",
"postalCode": "00000",
"addressCountry": "US"
},
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}],
"parentOrganization": {
"@id": "https://www.example.com/#organization"
}
}
The Corwin office page carries the same structure with its own @id, name, URL, phone, address, and hours, and the same parentOrganization reference.
Plumber is a subtype of LocalBusiness, used here as the most specific type. Each block sits in a script element of type application/ld+json on its page.
Checks before publishing:
| Check | Pass condition |
|---|---|
| Company entity | Present once, on the home or about page |
| Each branch entity | On that branch's page only |
| Address and phone in markup | Match the visible page, and match the branch's Business Profile |
| @id values | Unique per entity, stable, on your domain |
| parentOrganization | Points to the company's @id |
| sameAs | Real pages about that entity |
| Entities | Each corresponds to a real, operating location |
| Validation | Passes the Rich Results Test without errors |
Service-area operations with no premises open to customers need care. LocalBusiness requires an address, so a team that works from a private address should not be given a public street address in markup that the business does not otherwise publish.
Schema describes the offices on your website. Whether each office can have its own listing on Google Maps is governed by Google’s Business Profile rules, a separate matter covered in the guide to when a separate Google Business Profile is appropriate for an additional branch.
The rule: one Organization for the company, one LocalBusiness per real office, each on its own page, each pointing to its parent.
Add your comment to this answer