Organization Schema: Build Your Brand Entity for AI Discovery

Organization schema is how you declare your brand identity to search engines and AI systems. It tells machines who you are, what you do, where to find you, and how to verify your identity across the web. At 7.16% adoption on mobile pages according to the HTTP Archive 2024, Organization is the second most common schema type after WebSite -- yet most ecommerce stores implement it incompletely, missing properties that directly influence Google Knowledge Panels, AI brand mentions, and entity disambiguation. Getting Organization schema right is how you build a machine-readable brand identity that AI systems can trust, cite, and recommend.

Why Organization Schema Matters for Ecommerce

Organization schema serves a fundamentally different purpose than Product or Review schema. While those types describe what you sell, Organization schema describes who you are. This distinction matters enormously for AI systems.

Entity recognition and disambiguation. The web is full of brands with similar or identical names. Organization schema with sameAs links, founding date, location, and unique identifiers helps search engines and AI systems distinguish your brand from others. Without it, Google and AI engines must guess which "Greenfield" you are -- the organic grocery store, the real estate company, or the software platform.

Knowledge Panel eligibility. Google Knowledge Panels -- those information boxes that appear on the right side of search results -- are built from entity data. Organization schema with sameAs links to Wikipedia, Wikidata, and authoritative profiles is one of the strongest signals Google uses to build and maintain Knowledge Panels. When Google updated its Organization schema documentation on February 4, 2025, it expanded the supported properties to include loyalty programs, memberships, and special offers -- signaling that Organization schema is becoming a richer channel for brand information.

AI trust signals. When AI systems like ChatGPT or Perplexity recommend brands, they prefer entities with clear, verified identities. Organization schema provides the "Trust" and "Experience" signals that Google's quality raters evaluate -- verified identity through sameAs links, established history via foundingDate, and authoritative profile connections.

Cross-schema relationships. Organization schema connects to everything else. Your Product schema references your Organization as the manufacturer or seller. Your Article schema references it as the publisher. Your Review schema may reference it as the reviewed entity. A well-defined Organization entity at the center of your structured data graph strengthens every other schema type on your site.

Complete Organization Schema Example

Here is a comprehensive Organization JSON-LD block for an ecommerce brand:

{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "@id": "https://example.com/#organization",
  "name": "GlowLab Skincare",
  "alternateName": "GlowLab",
  "url": "https://example.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/images/logo.png",
    "width": "600",
    "height": "200",
    "caption": "GlowLab Skincare logo"
  },
  "image": "https://example.com/images/storefront.jpg",
  "description": "Clean, science-backed skincare formulated with clinically proven active ingredients. Founded in 2019 in Portland, Oregon.",
  "foundingDate": "2019-03-15",
  "foundingLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Portland",
      "addressRegion": "OR",
      "addressCountry": "US"
    }
  },
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "value": "45"
  },
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "contactType": "customer service",
      "telephone": "+1-503-555-0142",
      "email": "support@example.com",
      "availableLanguage": ["English"],
      "hoursAvailable": {
        "@type": "OpeningHoursSpecification",
        "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
        "opens": "09:00",
        "closes": "17:00"
      }
    }
  ],
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1234 NW Burnside St",
    "addressLocality": "Portland",
    "addressRegion": "OR",
    "postalCode": "97209",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://www.instagram.com/glowlabskincare",
    "https://www.facebook.com/glowlabskincare",
    "https://twitter.com/glowlabskin",
    "https://www.youtube.com/@glowlabskincare",
    "https://www.tiktok.com/@glowlabskincare",
    "https://www.linkedin.com/company/glowlab-skincare",
    "https://www.pinterest.com/glowlabskincare",
    "https://en.wikipedia.org/wiki/GlowLab_Skincare",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.crunchbase.com/organization/glowlab-skincare"
  ],
  "slogan": "Science you can see. Clean you can trust.",
  "knowsAbout": [
    "skincare",
    "vitamin C serum",
    "clean beauty",
    "active ingredients",
    "dermatological testing"
  ],
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "GlowLab Skincare Products",
    "itemListElement": [
      {
        "@type": "OfferCatalog",
        "name": "Serums",
        "url": "https://example.com/collections/serums"
      },
      {
        "@type": "OfferCatalog",
        "name": "Moisturizers",
        "url": "https://example.com/collections/moisturizers"
      },
      {
        "@type": "OfferCatalog",
        "name": "Cleansers",
        "url": "https://example.com/collections/cleansers"
      }
    ]
  }
}

Understanding Each Property

Identity Properties

@type -- Google recommends using the most specific Organization subtype that matches your business. For ecommerce, use OnlineStore (a subtype of Organization). Other options include Corporation, LocalBusiness, MedicalBusiness, etc.

@id -- A unique, stable identifier for your organization entity. Use a hash URL like https://example.com/#organization. This allows other schema blocks on your site to reference your Organization without repeating all its properties. Keep this consistent across every page.

name -- Your official brand name as it appears in business registrations and across the web.

alternateName -- Common abbreviations or alternative names people use for your brand. If customers call you "GlowLab" instead of "GlowLab Skincare," include both.

url -- Your canonical homepage URL.

Visual Identity

logo -- Google recommends using an ImageObject with explicit width and height dimensions rather than a simple URL string. The logo should be a high-resolution image (minimum 112x112 pixels, recommended 600 pixels wide) in a supported format (PNG, JPG, SVG, WebP).

image -- A representative image of your business -- storefront, team photo, or brand hero image.

The sameAs Property: Entity Verification

The sameAs property is the most strategically important property in Organization schema. It tells search engines and AI systems: "This organization is the same entity described at these external URLs."

What to include in sameAs:

  • Social media profiles (Instagram, Facebook, Twitter/X, YouTube, TikTok, LinkedIn, Pinterest)
  • Wikipedia page (if you have one)
  • Wikidata entry (strongly recommended for Knowledge Panel eligibility)
  • Crunchbase profile
  • Industry directory listings
  • Better Business Bureau page
  • Other authoritative profiles

What not to include:

  • Product review sites (those should be in Review schema)
  • Pages that are about you but not official profiles you control
  • Broken or outdated URLs

Why sameAs matters for AI: When Google sees your entity linked to trusted sources via sameAs, it gains confidence in your entity's authenticity. This directly impacts Knowledge Graph inclusion probability. AI systems like ChatGPT and Perplexity cross-reference entity data across sources -- if your Organization schema says you are "GlowLab Skincare" and your Wikipedia page, Crunchbase, and social profiles confirm this, the AI trusts the entity data more highly.

Consistency is critical. Your brand name must be spelled and formatted identically across your Organization schema and all sameAs targets. Inconsistent naming ("GlowLab Skincare" vs "Glow Lab" vs "GLOWLAB") confuses entity resolution.

Contact Information

contactPoint -- Customer service contact information. Include telephone, email, available languages, and hours. This data appears in Knowledge Panels and is used by AI assistants when users ask how to contact your brand.

address -- Your physical business address. Even for online-only stores, a registered business address strengthens your entity profile.

Temporal and Contextual Properties

foundingDate -- When your company was founded. This signals establishment and longevity. AI systems use this when answering questions like "How long has GlowLab been in business?"

knowsAbout -- Topics your organization has expertise in. This helps AI systems understand what questions your brand is qualified to answer, influencing citation decisions for topic-related queries.

Connecting Organization Schema to Product Schema

The @id property creates a bridge between your Organization schema and every Product on your site:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Vitamin C Brightening Serum",
  "brand": {
    "@type": "Brand",
    "name": "GlowLab Skincare"
  },
  "manufacturer": {
    "@id": "https://example.com/#organization"
  },
  "offers": {
    "@type": "Offer",
    "seller": {
      "@id": "https://example.com/#organization"
    }
  }
}

By referencing @id: "https://example.com/#organization", you connect each product to your full Organization entity without duplicating all the organization data on every product page. Search engines and AI systems follow the @id reference to build a complete picture: this product is made by GlowLab Skincare, which was founded in 2019 in Portland, has these social profiles, and is known for skincare expertise.

Brand vs. Organization vs. Manufacturer

These three relationships serve different purposes:

  • brand -- The commercial brand the product is sold under. Use the Brand type with a name property.
  • manufacturer -- The entity that actually makes the product. Reference your Organization by @id.
  • seller (inside Offer) -- The entity selling the product. For direct-to-consumer stores, this is your Organization.

For stores that sell their own branded products, all three typically point to the same entity. For stores that sell multiple brands, brand varies per product while seller stays constant.

Social Profiles and Their Impact

Each social profile in your sameAs array serves a verification function:

Instagram and TikTok -- Signal consumer brand relevance and visual identity. AI systems check if the follower counts and content themes match your stated brand identity.

LinkedIn -- Signals business legitimacy and employee count. AI systems can cross-reference your stated numberOfEmployees with LinkedIn data.

YouTube -- Signals content authority. A YouTube channel with educational content about skincare reinforces the knowsAbout claims in your Organization schema.

Wikipedia and Wikidata -- The strongest verification signals. A Wikipedia page means your brand has been deemed notable by independent editors. A Wikidata entry provides a structured, machine-readable identity that Google's Knowledge Graph directly consumes.

Crunchbase -- Signals business legitimacy, funding history, and industry classification.

Shopify Implementation

On Shopify, Organization schema belongs on your homepage. Here is a Liquid snippet:

{% if template == 'index' %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "@id": "{{ shop.url }}/#organization",
  "name": {{ shop.name | json }},
  "url": "{{ shop.url }}",
  "logo": {
    "@type": "ImageObject",
    "url": "{{ shop.url }}{{ settings.logo | image_url: width: 600 }}",
    "width": "600",
    "height": "200"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": {{ shop.email | json }}
  },
  "sameAs": [
    {% if settings.social_instagram_link != blank %}"{{ settings.social_instagram_link }}"{% endif %}
    {% if settings.social_facebook_link != blank %},  "{{ settings.social_facebook_link }}"{% endif %}
    {% if settings.social_twitter_link != blank %}, "{{ settings.social_twitter_link }}"{% endif %}
    {% if settings.social_youtube_link != blank %}, "{{ settings.social_youtube_link }}"{% endif %}
  ]
}
</script>
{% endif %}

For the @id to work across your site, reference it in your product template as well:

"manufacturer": {
  "@id": "{{ shop.url }}/#organization"
}

Common Organization Schema Mistakes

Using Organization instead of a specific subtype. Google recommends using OnlineStore, LocalBusiness, Corporation, or another specific subtype instead of the generic Organization type. The more specific type gives search engines and AI better context.

Inconsistent @id across pages. If your homepage uses https://example.com/#organization but your product pages reference https://www.example.com/#organization (note the www), the connection breaks. Use the exact same @id string everywhere.

Missing sameAs links. An Organization schema without sameAs is a brand without verification. Include every official profile you control.

Stale contact information. If your phone number or email changes, your schema must update. AI assistants that provide your old contact information damage customer trust.

Logo as a simple URL string. Google recommends an ImageObject with explicit dimensions, not just a URL. This helps Google select the right version of your logo for Knowledge Panels.

Omitting foundingDate. This is a missed opportunity. AI systems use founding date to assess brand maturity and longevity, particularly when answering comparative queries.

Organization schema is the foundation of your brand's machine-readable identity. Every other schema type on your site connects back to it. Invest the time to make it complete, accurate, and consistent, and every AI system on the web will understand not just what you sell, but who you are.

Up next

Article Schema

Article schema for blog content and AI citation.