Organization Schema Generator
Establish your brand identity in Google's Knowledge Graph with Organization schema
Configure Schema
Article: Blog posts, news articles, guides
Generated Schema
// Fill in the form to generate schema markup
Other Schema Generators
About Organization Schema Generator
Organization schema markup establishes your brand's identity in Google's Knowledge Graph — the database of entities that powers Google's understanding of who and what exists in the world. When Google has a strong Organization entity for your brand, it can display a Knowledge Panel in search results showing your logo, description, social profiles, and contact information when users search for your brand name directly.
Beyond Knowledge Panels, Organization schema contributes to Google's understanding of your brand across all your content. It establishes your brand name, logo, and website as a verified entity, which can strengthen E-E-A-T signals for all content on your site. It's also referenced by other schema types — Article schema's publisher property, Product schema's seller property, and LocalBusiness schema all build on a well-defined Organization entity.
Organization schema should be implemented on your homepage and potentially your About page — these are the canonical locations for brand-level information. It's also appropriate to reference your Organization in other schema types across your site, creating a consistent entity that Google can recognize and trust across all your content.
Organization Schema and the Knowledge Graph
Google's Knowledge Graph is a structured database of entities and relationships — people, organizations, places, products, and concepts. When Google creates a Knowledge Graph entry for your organization, it can display rich brand information directly in search results without users needing to visit your site. This is the foundation of brand knowledge panels.
Organization schema doesn't guarantee a Knowledge Panel — Google decides independently whether to create one based on your brand's prominence, the quality of available information, and signals from across the web. However, Organization schema is a foundational input into that decision and ensures Google has accurate, authoritative information about your brand regardless of whether a panel appears.
The sameAs property in Organization schema is particularly powerful — it links your schema entity to your profiles on authoritative platforms like LinkedIn, Twitter, Facebook, Wikipedia, Wikidata, and Crunchbase. These links help Google reconcile your brand's presence across the web into a single unified entity, strengthening entity recognition and the likelihood of Knowledge Panel generation.
Key Considerations
Place on Homepage
Organization schema belongs on your homepage — it's the canonical location for site-wide brand information. Your homepage Organization schema defines your brand entity for Google. Other pages can reference this entity, but the primary Organization schema should live at your root URL.
Logo Specifications
The logo image should be a clean version of your logo on a white or transparent background. Google recommends logos that are at least 112x112px for Knowledge Panel display. Include the logo as an ImageObject with url, width, and height properties. The logo URL should be permanent — changing it frequently can confuse Google's entity associations.
sameAs for Entity Disambiguation
Include sameAs URLs pointing to your official profiles on LinkedIn, Twitter, Facebook, YouTube, GitHub, Wikipedia (if applicable), and Wikidata (if applicable). These links help Google merge your various web presences into a single recognized entity. More high-authority sameAs links strengthen entity recognition.
Contact Information
Include contactPoint with telephone, contactType (customer service, sales, technical support), and areaServed. For businesses with multiple departments, include multiple contactPoint objects. Accurate contact information in schema contributes to your local and brand search presence.
Common Organization Issues
Logo Issues
- •Logo image too small for Knowledge Panel display requirements
- •Logo URL returning 404 or being inaccessible to Google crawler
- •Logo not representing the actual brand (generic or placeholder image)
- •Missing ImageObject type wrapping the logo URL
Identity Issues
- •Organization name inconsistent with brand name used elsewhere
- •Missing or incorrect url property — must point to canonical homepage
- •sameAs links pointing to inactive or incorrect social profiles
- •Missing @id property for entity reference from other schemas
Implementation Issues
- •Organization schema placed on every page instead of homepage
- •Duplicate Organization schemas with conflicting information
- •Missing description — reduces Knowledge Panel richness
- •foundingDate format incorrect — must be ISO 8601 date
Implementation Guide
Complete Organization JSON-LD Schema
Full Organization schema for your homepage:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example Company",
"url": "https://www.example.com",
"logo": {
"@type": "ImageObject",
"url": "https://www.example.com/logo.png",
"width": 300,
"height": 100
},
"description": "Example Company builds developer tools that help web developers and designers work faster.",
"foundingDate": "2023",
"numberOfEmployees": {
"@type": "QuantitativeValue",
"value": 10
},
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer service",
"email": "hello@example.com",
"availableLanguage": "English"
},
"sameAs": [
"https://twitter.com/example",
"https://linkedin.com/company/example",
"https://github.com/example",
"https://facebook.com/example"
]
}
</script>Reference Organization from Other Schemas
Use @id to reference your Organization entity from Article and Product schemas:
// In your Article schema — reference Organization as publisher:
{
"@type": "Article",
"publisher": {
"@type": "Organization",
"@id": "https://www.example.com/#organization"
// @id reference — Google knows this is the same entity
// as defined in your homepage Organization schema
}
}
// In your Product schema — reference Organization as brand or seller:
{
"@type": "Product",
"brand": {
"@type": "Brand",
"@id": "https://www.example.com/#organization"
}
}
// The @id creates a consistent entity graph across your site
// Google can recognize it's all the same organizationSoftwareApplication Schema for SaaS/Tools
For software products and tools, extend with SoftwareApplication type:
{
"@context": "https://schema.org",
"@type": ["Organization", "SoftwareApplication"],
"name": "Pacgie",
"url": "https://www.pacgie.com",
"applicationCategory": "DeveloperApplication",
"operatingSystem": "Web Browser",
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "USD"
},
"description": "Free developer tools for web developers and designers.",
"sameAs": [
"https://twitter.com/pacgie",
"https://github.com/pacgie"
]
}Common Use Cases
- New websites establishing brand identity with Google's Knowledge Graph
- Companies wanting a brand Knowledge Panel in search results
- Sites where Organization entity is referenced in Article and Product schemas
- Brands with significant social media presence wanting entity unification
- SaaS products establishing software identity alongside company identity
Pro Tip
After implementing Organization schema, claim and complete your Google Business Profile and ensure your brand name is consistent across all platforms listed in sameAs. Google cross-references your Organization schema with data from across the web — consistency between your schema and your external profiles accelerates Knowledge Graph entity recognition and strengthens brand authority signals.