Here's a question that trips up a surprising number of site owners once they start looking into structured data: should my business use Organization schema, or LocalBusiness schema? Both describe a company. Both can include a logo, contact details, and social links. On the surface, they look almost interchangeable, which is exactly why so many sites end up picking the wrong one, or worse, adding both incorrectly and confusing search engines instead of helping them.
The short answer is that these two schema types serve different purposes, and picking the right one depends on how your business actually operates — whether it's tied to a physical location customers visit, or whether it exists primarily online or across multiple locations. This guide breaks down the real difference, walks through when each one fits, and shows you how to combine them properly if your business genuinely needs both. If you'd rather skip the manual coding once you know which type fits, our
Organization Schema Generator builds correctly formatted JSON-LD for you in seconds.
What Is Organization Schema?
Organization schema is the broader, more general schema type. It represents a company or entity as a whole — its name, logo, official website, and connections to social profiles or other organizations. It doesn't assume you have a physical storefront or a specific service area; it simply says "this entity exists, here's what it's called, and here's how to verify it."
This makes Organization schema the right foundation for almost any business, including software companies, online-only stores, media publishers, and multi-location brands that don't want to tie their core identity to one specific address.
What Is LocalBusiness Schema?
LocalBusiness schema is more specific. It's designed for businesses that operate from a physical location customers can actually visit — a restaurant, a dental clinic, a retail store, a law office. It extends Organization schema with additional location-specific properties: a street address, opening hours, geographic coordinates, and a price range.
In technical terms, LocalBusiness is actually a subtype of Organization within the schema.org vocabulary, which is part of why the two get confused so often. LocalBusiness inherits everything Organization schema has, then adds the physical-location details on top.
SEO Tip: If you're ever unsure which one applies, ask yourself one question: "does a customer physically walk into a location to interact with this business?" If yes, LocalBusiness is likely the better fit. If no, Organization is usually correct.
Key Differences at a Glance
| Aspect | Organization Schema | LocalBusiness Schema |
|---|
| Best for | Online businesses, software companies, multi-location brands, publishers | Physical, location-based businesses like restaurants, clinics, and retail stores |
| Address requirement | Optional | Expected, and typically required for full benefit |
| Opening hours property | Not typically used | Commonly included (openingHoursSpecification) |
| Geographic coordinates | Not applicable | Supported (geo property), useful for maps and local search |
| Relationship in schema.org | Parent/general type | Subtype of Organization |
| Typical search benefit | Knowledge panel, brand entity recognition | Local pack visibility, map listings, local search rankings |
When to Use Organization Schema
- Your business operates primarily online, with no physical location customers visit.
- You run a software company, SaaS product, media outlet, or content publisher.
- You have multiple locations and want a single, unified brand entity rather than location-specific data on your main homepage.
- You're focused on general brand recognition and Knowledge Panel eligibility rather than local map visibility.
When to Use LocalBusiness Schema
- You run a business customers physically visit — a restaurant, salon, clinic, retail shop, or law office.
- You want to appear in Google's local pack or map results for location-based searches.
- You have specific opening hours, a service area, or a price range worth surfacing directly in search results.
- You operate multiple branches and want each individual location page to carry its own address and hours.
Common Mistake: Using LocalBusiness schema on a company's general homepage when the business actually has ten different branch locations. This creates ambiguity about which physical address the schema is even describing. In multi-location setups, LocalBusiness typically belongs on individual location pages, while Organization schema covers the brand as a whole.
Can You Use Both Together?
Yes, and for multi-location businesses, this is often the correct setup rather than an either-or choice. Here's how it typically works:
- Add Organization schema site-wide, representing the overall brand — name, logo, main website, and social profiles.
- Add LocalBusiness schema specifically on each individual location or branch page, including that location's address, hours, and coordinates.
- Use the parentOrganization property within each LocalBusiness entry to connect it back to the main Organization entity, making the relationship explicit rather than implied.
Best Practice: Keep your business name, logo, and contact details consistent between your Organization schema and any LocalBusiness entries. Inconsistent naming across the two is one of the most common reasons search engines fail to connect them as the same brand.
Example: Organization Schema (Online Business)
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example SaaS Co",
"url": "https://examplesaas.com",
"logo": "https://examplesaas.com/logo.png",
"sameAs": ["https://linkedin.com/company/examplesaas", "https://twitter.com/examplesaas"]
}
Example: LocalBusiness Schema (Physical Location)
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Coffee Shop",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "73301"
},
"openingHours": "Mo-Fr 07:00-18:00",
"telephone": "+1-512-555-0100"
}
Common Mistakes When Choosing Between the Two
| Mistake | Why It's a Problem |
|---|
| Using LocalBusiness for an online-only company | Adds address-related properties that don't apply, which can look inaccurate or incomplete to search engines |
| Using only Organization schema for a physical retail store | Misses out on local pack visibility, map listings, and opening hours display |
| Duplicating the same schema type twice on one page | Creates conflicting signals about which data is accurate |
| Forgetting parentOrganization on multi-location LocalBusiness entries | Leaves the connection between branch and brand implicit instead of explicit |
| Inconsistent business name across both schema types | Weakens entity recognition and can confuse Google's knowledge graph |
Expert Advice: If you're a service-area business that travels to customers rather than having them visit a fixed address — like a mobile repair service or a home cleaning company — look specifically at the areaServed property under LocalBusiness rather than forcing a fixed street address that doesn't reflect how you actually operate.
Frequently Asked Questions
1. Is LocalBusiness schema a type of Organization schema?
Yes, technically LocalBusiness is a subtype of Organization within the schema.org vocabulary, which is why the two share many of the same core properties.
2. Can an online-only business still use LocalBusiness schema?
It's not recommended, since LocalBusiness schema is built around location-specific data like an address and opening hours, which don't apply to a purely online business.
3. Does using LocalBusiness schema guarantee a spot in Google's local pack?
No, it improves eligibility and accuracy of information, but ranking in the local pack still depends on factors like proximity, relevance, and overall business prominence.
4. What happens if I use both schema types incorrectly on the same page?
Search engines may receive conflicting signals about your business identity, which can weaken entity recognition rather than strengthen it.
5. Should a multi-location restaurant chain use Organization or LocalBusiness schema?
Typically both — Organization schema for the overall brand, and separate LocalBusiness schema on each individual restaurant's location page.
6. Does LocalBusiness schema require a physical street address?
In most cases, yes, since the schema is designed around location-based details, though service-area businesses can use the areaServed property instead of a fixed address.
7. Can I use a more specific LocalBusiness subtype, like Restaurant or Dentist?
Yes, schema.org includes many specific LocalBusiness subtypes, and using the most accurate one available often provides richer, more relevant search features than the generic LocalBusiness type.
8. Is Organization schema necessary if I already have LocalBusiness schema?
For a single-location business, LocalBusiness schema alone is usually sufficient, since it already inherits Organization properties. Separate Organization schema becomes more valuable once a business has multiple locations under one brand.
9. Does the choice between these two schema types affect Knowledge Panel eligibility?
Organization schema is more directly tied to broader brand entity recognition, which plays into Knowledge Panel eligibility, while LocalBusiness schema is more closely tied to local search features specifically.
10. Can I test which schema type is currently active on my site?
Yes, use Google's Rich Results Test or view your page source and search for "@type" within a script tag labeled application/ld+json to see exactly which schema type is currently implemented.
Conclusion
Organization schema and LocalBusiness schema aren't competing options — they're tools built for different situations, and picking the wrong one just leaves search engines with a slightly inaccurate picture of your business. If you operate online or across multiple locations, start with Organization schema as your foundation. If customers walk through your door, LocalBusiness schema is what actually earns you visibility in local search and map results.
Once you know which type fits your business, you can build correctly formatted, error-free JSON-LD in seconds using our
Organization Schema Generator, without worrying about missing brackets or incorrect property names.