How to Create Organization Schema: A Complete 2026 Guide

Chapter 1. Before you start

Organization schema is the entity record for your brand. It tells search engines and LLMs who you are, where you are, how to reach you, and which other profiles on the web belong to the same entity. It powers Knowledge Panels, populates the brand-info pane in AI Overviews, and is the foundation every other schema on your site references via publisher or provider.

• Confirm your canonical brand name and legal name. They are often different. Use the commercial name in name and the legal name in legalName.
• Locate your high-resolution logo as a publicly accessible URL. Minimum 112x112 pixels. Square or rectangle, both fine. PNG with transparency is the standard.
• Gather every canonical profile URL: Wikipedia, Wikidata, LinkedIn, X/Twitter, Crunchbase, Instagram, YouTube, Facebook, and any industry profile (G2, Trustpilot, BBB).
• Confirm your registered business address. Required for LocalBusiness subtypes; recommended even for online-only brands as a Trust signal.
• Pick a contact email and phone. They go into contactPoint and surface in some search features. Use the customer-facing channels, not internal ones.

Chapter 2. Pick the right subtype

Use the most specific subtype that applies. Google's structured data policies explicitly call this out: OnlineStore beats Organization for ecommerce; Restaurant beats LocalBusiness for restaurants; NewsMediaOrganization beats Organization for publishers. The specific subtype unlocks property fields the parent type does not have.

The full subtype hierarchy is at schema.org/Organization. When in doubt, browse from the parent type down through the more specific children until you find the one that matches what your business actually is.

Chapter 3. Required and recommended properties

Google's documentation states there are no strictly required properties for Organization schema. Instead, the recommendation is to ship as many recommended properties as apply to your business. The practical floor below is what we ship on every client deployment.

{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "@id": "https://www.example.com/#organization",
  "name": "Example Brand",
  "legalName": "Example Brand, Inc.",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/brand/logo.png",
  "description": "One-sentence brand description.",
  "foundingDate": "2019",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Example_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/example-brand",
    "https://x.com/examplebrand",
    "https://www.crunchbase.com/organization/example-brand"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "Customer Service",
    "email": "support@example.com",
    "telephone": "+1-555-123-4567"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1 Main St",
    "addressLocality": "Anytown",
    "addressRegion": "CA",
    "postalCode": "94000",
    "addressCountry": "US"
  }
}

Each field above is recommended by Google. For full subtype-specific fields (e.g. hasMerchantReturnPolicy, hasShippingService, and hasMemberProgram on OnlineStore), see the Search Central Organization documentation.

Chapter 4. Which sameAs links matter most?

sameAs is the single most under-shipped Organization property and the highest-leverage one for AI search visibility. Every URL you list in sameAs reinforces the entity record - Knowledge Graph uses them for disambiguation, LLMs use them to tighten the entity embedding in vector space.

If your brand does not have a Wikipedia or Wikidata entry yet, building one is the highest single-action lift available for AI-engine visibility. Wikipedia accounts for roughly 53% of the top-1,000 ChatGPT-cited pages and is the most cited domain in Google AI Overviews. Wikidata is the backbone Google Knowledge Graph queries for entity disambiguation.

Chapter 5. Validate before you deploy

Two validators, two purposes. Run both before you deploy a single change to production.

1. Paste your JSON-LD into validator.schema.org. This validates against the Schema.org vocabulary itself - it tells you if your types and properties exist and are used correctly.
2. Paste the same code into the Google Rich Results Test. This validates against Google's specific requirements for rich result eligibility - which can differ from Schema.org's general vocabulary.
3. Fix every critical error from both. Non-critical warnings are worth fixing but not blocking.
4. Once live, monitor Search Console → Enhancements for the Organization rich result report to catch errors at scale across your site.

Chapter 6. Where do you place Organization schema on the site?

Organization schema goes on your homepage and About page only. Not every page. Shipping it sitewide is a common Yoast / Rank Math plugin default that creates duplicate entity definitions Google has to reconcile - the opposite of what schema is for.

On the homepage, embed the JSON-LD inside <script type="application/ld+json"> tags in <head> or before </body>. Either location works; head is conventional. On the About page, ship the same Organization block plus any About-specific schema (founders as Person entries, history as Event entries, etc.).

Use the @id property to give your Organization a stable identifier (https://www.example.com/#organization is the convention). Other schemas across your site reference this @id via publisher or provider - which lets you ship the full Organization details once and reference them everywhere else without duplication. See post #1, the GA4 setup guide, for an example of the @id reference pattern in BlogPosting schema.

Chapter 7. The breakages we see most often

Ranked by frequency across 47 ecommerce schema audits over the past 24 months:

• No sameAs entries: brand entity can't be disambiguated from same-named competitors. 31 of 47 audited stores.
• Base Organization type used when a subtype exists: OnlineStore or specific LocalBusiness subtype is correct. 26 of 47.
• Schema duplicated sitewide instead of homepage + About only: conflicting entity definitions. 22 of 47.
• Self-serving aggregateRating or review on the org's own page: Google policy violation. 17 of 47.
• Logo URL returns a small or non-existent image: rich result eligibility broken. 14 of 47.
• No @id on the Organization: other schema can't reference it cleanly. 9 of 47.
• Microdata or RDFa used instead of JSON-LD: harder to maintain, Google's recommended format is JSON-LD. 6 of 47.

We track Organization schema completeness continuously through our Sentry product; the structured-data rule set catches the breakages above on running sites.