$devtoolkit.sh/templates/schema/organization

Organization JSON-LD Schema Template

Organization structured data is typically placed on your homepage and serves as the foundational brand signal that establishes your entity in Google's Knowledge Graph. Unlike product or article schema that targets specific content pages, Organization schema tells Google who you are as a company — your name, logo, website, contact information, and social media presence. This information populates the Knowledge Panel that appears on the right side of search results when users search for your brand name.

The Organization type (or its subtype Corporation) should be added to your homepage with the @id property set to a canonical URL representing your organization — typically your domain with a trailing # to avoid confusion with the webpage URL itself (e.g., "https://example.com/#organization"). This @id is then referenced from other pages using the sameAs pattern to build a connected entity graph across your site.

Logo requirements for rich results: the logo image should be a permanent, publicly accessible URL, at least 112×112 pixels, and at most 512KB in file size. Rectangular logos are preferred over square logos for most display contexts. Google specifically notes that logos with transparent backgrounds may not display correctly in all contexts — use white or brand-appropriate background fill.

The sameAs property is one of the most powerful fields in the Organization schema. It accepts an array of URLs that identify the same organization on other platforms: your LinkedIn company page, Twitter/X profile, Facebook page, Instagram, YouTube channel, Crunchbase profile, and Wikipedia article if one exists. Google uses these to connect your organization's identity across the web and build a more complete Knowledge Graph entity. Include every verified social profile — even platforms you do not actively use are useful for disambiguation.

Contact information in Organization schema should reflect your primary customer contact channels. Use the contactPoint property with ContactPoint objects for each contact method: customer service phone, technical support email, sales inquiries. Specify contactType and availableLanguage to help Google surface the right contact for users. The hasMap property with a Google Maps URL is useful for physical locations.

For companies with multiple locations, use the subOrganization property to link to Location or LocalBusiness entities for each office, or use the PostalAddress property on the Organization itself for single-location businesses.

Template Preview

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Company Name",
  "url": "https://example.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/logo.png",
    "width": 512,
    "height": 512
  },
  "description": "Brief description of what your company does.",
  "foundingDate": "2020",
  "sameAs": [
    "https://twitter.com/yourhandle",
    "https://linkedin.com/company/yourcompany",
    "https://github.com/yourorg"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "[email protected]",
    "availableLanguage": "English"
  }
}

Customize this template with your own details using the free generator:

Open in Generator

FAQ

Will Organization schema guarantee a Google Knowledge Panel?
No. Organization schema helps Google understand your brand entity, but Knowledge Panels are granted algorithmically based on entity authority, search volume for your brand, and consistency of information across the web. Schema is a signal, not a guarantee. To improve your chances, ensure your organization information is consistent across your website, Google Business Profile, LinkedIn, Wikipedia (if applicable), and major directories.
Should I use Organization or Corporation schema type?
Corporation is a more specific subtype of Organization appropriate for registered corporations. Organization is the correct type for non-profit organizations, partnerships, sole proprietorships, government agencies, and any entity that is not specifically a corporation. If you are a registered corporation, use Corporation — more specific types provide better signals. Both inherit the same properties.
Where should I place the Organization schema — only on the homepage?
The canonical Organization schema block typically goes on your homepage because that page represents your organization. However, you should also include it in your site-wide header or footer template using the @id reference so Google encounters it on every page crawl. On interior pages, you can reference the organization entity by its @id rather than repeating the full object.

Related Templates

/templates/schema/organizationv1.0.0