The wrong type is worse than a missing one. Here is the rule we use, why an address and a phone number change the answer, and what NAP mismatch costs you.
This looks like a trivia question and it is not. LocalBusiness is a subtype of Organization that carries obligations — an address, opening hours, a phone number — and search engines treat those as claims about a real place customers can turn up at. Claim it when it is not true and you get inconsistency penalties in the places you least want them.
The rule
Use LocalBusiness if a customer could physically visit you, or if you serve a defined geographic area from a real base. Use Organization otherwise.
That is the whole rule. A few worked cases:
| You are | Use | Why |
|---|---|---|
| A SaaS company with a WeWork desk | Organization | Nobody visits. A shared address is not a place of business. |
| A dental practice | LocalBusiness (or Dentist) | Patients come to you at a fixed address. |
| A plumber covering three counties, no shopfront | LocalBusiness with areaServed, address optional | Service-area business — a recognised pattern. |
| An agency with a real office clients visit | Both, one block | Genuinely both things. |
| A national e-commerce brand, one warehouse | Organization | The warehouse is not a customer destination. |
| A restaurant group with six locations | Organization for the brand, Restaurant per location page | The brand is not a place; each venue is. |
How our scan decides
On every scan we look at the homepage for a postal address and a phone number. Find both, or an address in a plausible business format, and we generate a LocalBusiness block. Find neither, and we generate Organization. It matches what a crawler infers from the same page, which is the point — you want your declared type and your visible page to agree.
There is a more specific type for most trades — Dentist, Restaurant, LawFirm, AutoRepair, HomeAndConstructionBusiness and a few hundred more. Use the most specific one that is accurate. Dentist tells a machine more than LocalBusiness, which tells it more than Organization.
Being both
You do not need two blocks. @type accepts an array:
{
"@context": "https://schema.org",
"@type": ["Organization", "LocalBusiness"],
"name": "Kirby & Co",
"url": "https://kirbyco.example",
"address": {
"@type": "PostalAddress",
"streetAddress": "14 Wharf Road",
"addressLocality": "Denver",
"addressRegion": "CO",
"postalCode": "80202",
"addressCountry": "US"
},
"telephone": "+1-303-555-0142",
"openingHours": "Mo-Fr 09:00-17:00"
}
One node, both types, no duplication. This is the right shape for an agency, a clinic, or any business that is a company and a place.
NAP consistency, and why it is a finding
NAP is name, address, phone. The rule is that all three must be byte-for-byte consistent across your site, your schema, your Google Business Profile, and every directory that lists you.
Not "roughly the same." Suite 4 and Ste. 4 are different strings. (303) 555-0142 and +1 303 555 0142 are different strings. A machine trying to decide whether two listings are the same business compares strings, and a mismatch lowers its confidence that either is right.
This is why we report NAP mismatch as a finding rather than shipping you a list of directories to submit to. Submitting your business to forty directories with three variations of your address actively makes things worse. Fix the canonical form first, then propagate it.
Multi-location, done properly
The pattern that works:
- The homepage carries one
Organizationblock for the brand. - Each location has its own page, with its own
LocalBusiness(or more specific) block, its own address and phone, and aparentOrganizationpointing at the brand's@id. - The location pages have real, differentiated content — staff, hours, parking, photos. Six near-identical pages with the address swapped are thin pages, and thin pages hurt.
The anti-pattern is stacking six LocalBusiness blocks on the homepage. It reads as one confused entity with six addresses rather than as a brand with six branches.
What to do if you got it wrong
Switch the type, make the visible page agree, and give it time. There is no penalty for having used the wrong type as long as you were not claiming an address you do not have. If you were — a virtual office listed as a shopfront, say — remove the address entirely and move to a service-area model. That is a correction worth making before it is noticed.