Organization Schema for Brand: The Complete 2026 Guide

Organization is a subtype of Thing at the top of the business-related schema hierarchy. It has properties for name, logo, contact information, social profiles, founding date, and corporate hierarchy. Many schema types reference Organization as a property value: Article.publisher, Product.brand, LocalBusiness.parentOrganization, and Event.organizer.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "TechPub Inc.",
  "url": "https://techpub.example.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://techpub.example.com/logo.webp",
    "width": 600,
    "height": 60
  },
  "description": "TechPub publishes technical guides and tutorials for software engineers.",
  "foundingDate": "2018-03-15",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "minValue": 50,
    "maxValue": 200
  }
}

Google doesn't require Organization schema for any specific rich result, but it's foundational for entity understanding.

name must match your brand name exactly — no keyword-stuffed variations. url must match your canonical domain used in Search Console. logo must be at least 112px wide, publicly accessible, and hosted on your domain or a recognized CDN. sameAs lists official social media and external reference profiles — Facebook, LinkedIn, Twitter, Instagram, YouTube, Wikipedia, Crunchbase, GitHub (Schema.org, "Organization Type," 2026).

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "TechPub Inc.",
  "url": "https://techpub.example.com",
  "logo": "https://techpub.example.com/img/logo.svg",
  "description": "Technical publishing company specializing in software engineering guides.",
  "foundingDate": "2018-03-15",
  "foundingLocation": {
    "@type": "Place",
    "name": "San Francisco, California"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "456 Market Street, Suite 300",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94105",
    "addressCountry": "US"
  },
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "telephone": "+141****1234",
      "contactType": "customer service",
      "areaServed": "US",
      "availableLanguage": ["English", "Spanish"]
    },
    {
      "@type": "ContactPoint",
      "telephone": "+141****5678",
      "contactType": "press inquiries",
      "email": "[email protected]"
    }
  ],
  "sameAs": [
    "https://facebook.com/techpub",
    "https://linkedin.com/company/techpub",
    "https://twitter.com/techpub",
    "https://github.com/techpub"
  ]
}

ContactPoint declares specific contact channels with a contactType such as "customer service", "billing support", "technical support", "sales", "press inquiries", or "emergency". Provide telephone, email, areaServed, and availableLanguage where applicable. Google uses this data to generate knowledge panel links and populate local search contact information.

A well-constructed Organization schema with sameAs, logo, and url is one of several signals Google uses for knowledge panel generation. Missing or conflicting schema data can prevent a panel from appearing. A knowledge panel requires a critical mass of authoritative signals including Wikipedia presence, social verification, and consistent structured data (Google, "Knowledge Panel Information," 2025).

For companies operating multiple websites under one brand, deploy Organization schema on every site with identical name and logo but site-specific url. sameAs profiles should be consistent across all sites, signaling to Google that these domains belong to the same entity. For parent-subsidiary structures, use subOrganization and parentOrganization properties.

Host the logo on your primary domain or a dedicated media subdomain. Google recommends SVG for scalable vector graphics or PNG for raster images. Avoid Base64 embedded data URIs within JSON-LD. The logo URL must resolve to a static image file, not a redirect chain or image proxy.

• [ ] Organization schema is present on the homepage and contact page
• [ ] name matches the brand name used across all marketing channels
• [ ] url matches the canonical domain in Search Console
• [ ] logo is at least 112px wide and publicly accessible
• [ ] sameAs links are valid, publicly accessible, and point to official profiles
• [ ] contactPoint matches the contact information on the page
• [ ] Multiple sites of the same brand use consistent Organization data
• [ ] No competing Organization blocks declaring different names on the same domain