Written by Chris Drinkard
14 years in hospitality management
5 years helping independent hotels grow their online presence. Passionate about AI, search, and digital strategy.
What is Organization Schema?
Organization schema is structured data that tells search engines about your business or company. It defines your brand identity, contact information, social profiles, and company structure in a format that Google can understand and use to enhance search results.
Why Organization Schema Matters
- ✓ Establishes brand identity with search engines
- ✓ Increases chances of triggering a Knowledge Panel
- ✓ Links your website to social media profiles
- ✓ Provides consistent business information across platforms
- ✓ Builds the foundation for other schema types
- ✓ Enhances branded search results appearance
Organization schema is foundational—it's often the first structured data type you should implement. Other schema types like Article, Product, and JobPosting can reference your Organization, creating a connected web of structured data that strengthens your overall search presence.
Organization Types & Subtypes
Schema.org provides specific Organization subtypes. Using the most accurate type helps Google understand your business better:
Organization
The generic parent type. Use when no specific subtype fits or for general corporate entities.
Corporation
For incorporated companies, especially publicly traded ones. Can include tickerSymbol property.
LocalBusiness
For businesses with physical locations customers visit. Includes address, hours, and geo-coordinates.
EducationalOrganization
For schools, universities, training centers, and educational institutions.
GovernmentOrganization
For government agencies, departments, and public institutions at any level.
NGO / NonprofitOrganization
For non-profit organizations, charities, and NGOs.
SportsOrganization
For sports teams, leagues, and athletic organizations.
Organization Schema & Knowledge Panels
One of the primary benefits of Organization schema is improving your chances of triggering a Google Knowledge Panel—the information box that appears on the right side of search results for branded queries.
What Triggers a Knowledge Panel?
Google creates Knowledge Panels by combining information from multiple sources:
- • Wikipedia entry: The strongest signal for Knowledge Panel eligibility
- • Wikidata entity: Structured data in Wikidata helps Google verify information
- • Organization schema: Confirms details like name, logo, and social profiles
- • Google Business Profile: For local businesses, GBP data is essential
- • Authoritative mentions: References from trusted news and industry sources
Pro Tip: Claim Your Knowledge Panel
If your organization has a Knowledge Panel, you can claim it through Google Search. Search for your brand, click "Claim this knowledge panel" at the bottom, and verify your ownership. This allows you to suggest edits and keep information accurate.
Required & Recommended Properties
While Organization schema has no strictly required properties, including comprehensive information significantly improves its effectiveness:
| Property | Importance | Description |
|---|---|---|
| name | Essential | Official organization name |
| url | Essential | Official website URL |
| logo | Essential | Company logo image URL |
| sameAs | Recommended | Array of social profile URLs |
| description | Recommended | Brief description of the organization |
| address | Recommended | Physical headquarters address |
| contactPoint | Optional | Customer service, sales contacts |
| foundingDate | Optional | When the organization was founded |
| founder | Optional | Person or people who founded the organization |
| numberOfEmployees | Optional | Employee count or range |
Step-by-Step Implementation
Complete Organization Schema Example
Here's a comprehensive Organization schema with all recommended properties:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Corporation",
"alternateName": "Example Corp",
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png",
"width": 600,
"height": 60
},
"image": "https://example.com/company-photo.jpg",
"description": "Example Corporation is a leading provider of innovative software solutions for businesses worldwide.",
"foundingDate": "2010-01-15",
"founders": [
{
"@type": "Person",
"name": "Jane Smith",
"jobTitle": "CEO"
},
{
"@type": "Person",
"name": "John Doe",
"jobTitle": "CTO"
}
],
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Innovation Way",
"addressLocality": "San Francisco",
"addressRegion": "CA",
"postalCode": "94105",
"addressCountry": "US"
},
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "+1-800-555-0123",
"contactType": "customer service",
"availableLanguage": ["English", "Spanish"]
},
{
"@type": "ContactPoint",
"telephone": "+1-800-555-0124",
"contactType": "sales",
"availableLanguage": "English"
}
],
"sameAs": [
"https://www.linkedin.com/company/example-corp",
"https://twitter.com/examplecorp",
"https://www.facebook.com/examplecorp",
"https://www.youtube.com/@examplecorp",
"https://www.instagram.com/examplecorp"
],
"numberOfEmployees": {
"@type": "QuantitativeValue",
"minValue": 100,
"maxValue": 250
}
}
</script> Corporation Schema Example
For publicly traded companies, use Corporation with stock ticker:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Corporation",
"name": "Example Inc.",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"tickerSymbol": "EXMP",
"exchange": "NASDAQ",
"legalName": "Example Incorporated",
"taxID": "12-3456789",
"address": {
"@type": "PostalAddress",
"streetAddress": "1 Corporate Plaza",
"addressLocality": "New York",
"addressRegion": "NY",
"postalCode": "10001",
"addressCountry": "US"
},
"sameAs": [
"https://www.linkedin.com/company/example-inc",
"https://twitter.com/exampleinc"
]
}
</script> Minimal Organization Schema
At minimum, include these essential properties:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company Name",
"url": "https://yourcompany.com",
"logo": "https://yourcompany.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/yourcompany",
"https://twitter.com/yourcompany"
]
}
</script> Corporate Hierarchy & Subsidiaries
For companies with parent-subsidiary relationships, use parentOrganization
and subOrganization to show the structure:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Subsidiary Brand",
"url": "https://subsidiary.com",
"logo": "https://subsidiary.com/logo.png",
"parentOrganization": {
"@type": "Corporation",
"name": "Parent Holdings Inc.",
"url": "https://parentholdings.com"
}
}
</script> Or from the parent's perspective:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Corporation",
"name": "Parent Holdings Inc.",
"url": "https://parentholdings.com",
"subOrganization": [
{
"@type": "Organization",
"name": "Subsidiary Brand A",
"url": "https://subsidiarya.com"
},
{
"@type": "Organization",
"name": "Subsidiary Brand B",
"url": "https://subsidiaryb.com"
}
]
}
</script> Common Mistakes to Avoid
❌ Adding Organization Schema to Every Page
Organization schema only needs to appear once—typically on your homepage and/or About page. Adding it to every page is unnecessary and can clutter your structured data.
❌ Using Wrong Organization Type
Using LocalBusiness for an online-only company or Corporation for a small startup is misleading. Choose the type that most accurately describes your organization.
❌ Mismatched Information
The name, logo, and address in your schema must match what's visible on your website and other official sources. Inconsistencies confuse Google and can reduce trust signals.
❌ Including Unofficial Social Links
Only include social profiles you officially control in sameAs. Don't add fan pages, unofficial accounts, or profiles you don't actively maintain.
❌ Missing Logo Requirements
Logo images should be in a supported format (PNG, JPG, GIF, SVG, WebP), properly sized, and on the same domain as your website. Use high-resolution logos for best results.
Testing & Validation
After implementing Organization schema, validate it with these tools:
Schema Markup Validator
The official Schema.org validator checks your markup against the full vocabulary.
Open Schema Validator →Google Rich Results Test
While Organization doesn't have specific rich results, this tool validates general schema syntax.
Open Rich Results Test →Monitoring Your Knowledge Panel
- Search for your brand name to see if a Knowledge Panel appears
- Check if information displayed matches your schema markup
- Monitor for any suggested edits if you've claimed your panel
- Review Google Search Console for any structured data errors
Related Schema Guides
Organization schema works alongside other structured data types. Explore our other schema implementation guides:
Frequently Asked Questions
Where should Organization schema be placed?
Organization schema should be placed on your homepage and About page. It only needs to appear once per domain - don't add it to every page. Some implementations also include it in a site-wide header or footer component for consistent presence.
Does Organization schema guarantee a Knowledge Panel?
No, Organization schema alone doesn't guarantee a Knowledge Panel. Google creates Knowledge Panels based on multiple signals including Wikipedia entries, authoritative mentions, and overall web presence. However, Organization schema helps Google understand your brand and increases the likelihood of a panel appearing.
Should I use Organization or LocalBusiness schema?
Use LocalBusiness if you have a physical location customers visit. LocalBusiness is a subtype of Organization with additional properties for address, hours, and geo-coordinates. For online-only businesses or corporate entities without customer-facing locations, Organization is more appropriate.
How do I link my Organization schema to social profiles?
Use the 'sameAs' property with an array of your official social media profile URLs. Include LinkedIn, Twitter/X, Facebook, Instagram, YouTube, and any other verified profiles. This helps Google understand which social accounts belong to your organization.
Can I nest multiple organizations in one schema?
Yes, you can use 'parentOrganization' and 'subOrganization' properties to show company hierarchies. This is useful for subsidiaries, divisions, or franchise relationships. Each organization should also have its own standalone schema on its respective website.
Check Your Organization Schema
Run a free SEO audit to verify your Organization schema is properly implemented and discover other opportunities to improve your structured data.
Run Free SEO Audit
Linking Social Profiles
The
sameAsproperty is crucial for connecting your organization to its social media presence. This helps Google understand which social accounts are officially yours.Best Practices for sameAs