Organization schema markup (schema.org/Organization) is structured data you add to a website to formally identify the company behind it. It covers your legal name, web presence, contact details, logo, and social profiles in a single machine-readable block. You place it on the homepage or a dedicated About page — wherever your core business identity lives — and it becomes the authoritative source search engines pull from when building your entity profile.

This is one of the foundational schema types I implement for almost every client. Without it, search engines piece together your business identity from random page text, third-party directories, and social bios — sources you do not control. Organization schema markup gives you control of that first impression in the knowledge graph.

What Organization Schema Actually Does for Your Site

Google uses Organization markup to populate the Knowledge Panel that appears when someone searches your brand name directly. It also feeds AI-powered search features — including AI Overviews and LLM-based retrieval systems — that assemble entity profiles from structured data rather than scraping prose. Getting this right means your name, logo, and contact information come from a source you authored rather than inferred from inconsistent text across the web.

Schema is not a direct ranking factor. What it does is help Google understand who you are as an entity, which feeds confidence scoring for E-E-A-T signals, rich results eligibility, and Knowledge Panel generation. The same principle applies across content types — from recipe schema markup to e-commerce — where structured data shapes how Google classifies the page, not just whether it ranks. Organizations with clean, verified structured data consistently see better branded SERP features than those relying on prose alone.

The sameAs array is particularly important. By listing your LinkedIn company page, Twitter/X profile, Crunchbase entry, Wikipedia page (if you have one), and other authoritative profiles, you give Google the connective tissue it needs to merge disparate mentions of your brand into one confirmed entity node in the knowledge graph. Disambiguation is where most organizations fail — they have a name, but no cross-platform proof it is the same entity.

Required and Recommended Properties

Schema.org defines required and recommended properties differently by context. For Organization, nothing is technically required by the schema vocabulary itself, but Google has well-documented expectations for what it uses in rich results and Knowledge Panels. Here is the working set I use:

  • @type — Organization or a more specific subtype (see below)
  • name — legal or canonical business name, exactly as it appears across your profiles
  • url — canonical homepage URL
  • logo — an ImageObject pointing to your logo file; Google requires at least 112×112 px and recommends 600×60 px or larger for search use
  • sameAs — array of authoritative profile URLs (LinkedIn, Twitter/X, Facebook, Crunchbase, Wikipedia, Wikidata)
  • contactPoint — a ContactPoint with contactType, telephone, and areaServed
  • address — a PostalAddress with street, city, state, and postal code
  • foundingDate — four-digit year the company was established
  • description — a concise summary of what the organization does, matching visible page copy
  • numberOfEmployees — a QuantitativeValue object; useful for B2B credibility signals

Organization Subtypes: When to Go More Specific

One of the most common mistakes I see is leaving @type at the generic Organization level when a more precise subtype is available. Schema.org has a rich hierarchy beneath Organization, and using the right node gives search engines better classification signals:

  • LocalBusiness — any business with a physical location that serves local customers; this type (and its children like Restaurant, MedicalBusiness, LegalService) unlocks Local Pack eligibility
  • Corporation — incorporated companies; adds properties like tickerSymbol for publicly traded entities
  • EducationalOrganization — schools, universities, training providers
  • NGO / GovernmentOrganization — nonprofits and government bodies
  • ProfessionalService — consulting firms, agencies, freelance practices

You can also use an array for @type — for example, ['Organization', 'LocalBusiness'] — when both types apply. This is valid JSON-LD and gives more classification signals without conflicting with either type. The same multi-type approach appears in specialized contexts like automotive schema markup, where dealer pages often combine AutoDealer with LocalBusiness.

JSON-LD Example for Organization Schema Markup

The preferred format for implementing organization schema markup is JSON-LD, placed in a <script> tag in your page <head>. It does not require any changes to visible HTML and is the format Google explicitly recommends.

<script type='application/ld+json'>
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Salterra Digital Services",
  "url": "https://www.salterra.com",
  "description": "Full-service digital marketing and web design agency specializing in SEO, schema markup, and conversion optimization.",
  "foundingDate": "2011",
  "logo": {
    "@type": "ImageObject",
    "url": "https://www.salterra.com/logo.png",
    "width": 600,
    "height": 60
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Tempe",
    "addressRegion": "AZ",
    "postalCode": "85281",
    "addressCountry": "US"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "telephone": "+1-480-555-0100",
    "areaServed": "US",
    "availableLanguage": "English"
  },
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "value": 12
  },
  "sameAs": [
    "https://www.linkedin.com/company/salterra",
    "https://twitter.com/salterra",
    "https://www.facebook.com/salterra",
    "https://www.crunchbase.com/organization/salterra"
  ]
}
</script>

How to Add Organization Schema in WordPress

In WordPress, the cleanest approach depends on what plugins you are running. If your site runs on a different platform, see the guide on schema markup for Squarespace for platform-specific implementation details. If you use Yoast SEO or Rank Math, both have Organization settings in their configuration wizard — Yoast calls it "Knowledge Graph & Schema," Rank Math labels it under "Local SEO." These cover the basics but often miss foundingDate, numberOfEmployees, and a robust sameAs array.

For complete control, I add a custom JSON-LD block directly in the theme's functions.php or via a Code Snippets plugin using wp_head action. This fires on the homepage only (is_front_page()) and outputs exactly what I need without depending on plugin settings that clients accidentally override. The full guide on adding schema markup covers both approaches in detail.

How to Test Organization Schema Markup

After implementing, validate with two tools:

  • Google Rich Results Test (search.google.com/test/rich-results) — shows what Google sees and flags critical errors vs. warnings
  • Schema Markup Validator (validator.schema.org) — validates against the schema.org vocabulary; catches type mismatches and missing recommended properties

Common errors to watch for: a logo URL that returns a 404, sameAs links that redirect to a generic profile page rather than your specific profile, or a contactPoint telephone number formatted without the country code prefix. Google Search Console will also surface structured data errors under the "Enhancements" section once the page is indexed.

Organization Schema and AI Search

As of mid-2026, AI Overviews and LLM-based search features increasingly use structured data as a trusted input layer rather than free-form text. When an AI system needs to answer "Who is behind [company]?", a well-formed Organization block gives it a machine-readable answer it can use with confidence. Pages without it force the model to parse prose, which introduces ambiguity and occasionally wrong information.

The sameAs property is especially relevant here. LLMs are trained on web data and cross-reference entities across sources — your Organization markup creates a verifiable anchor point that helps those cross-references resolve correctly. It is a modest thing to implement and one of the higher-leverage structured data investments available for established businesses.

Common Organization Schema Mistakes

  • Marking up information that does not appear on the page. The golden rule: only mark up content the user can see. If your address is not on the page, do not put it in the schema — or add it to the page first. This visibility rule applies equally to specialized types like SoftwareApplication schema markup, where pricing and feature details must be visible on the page to be marked up.
  • Using the generic Organization type when a more specific subtype — LocalBusiness, MedicalBusiness, EducationalOrganization — would give better signals.
  • Letting sameAs URLs go stale. Profile URLs change; a dead link in sameAs actively hurts entity disambiguation.
  • Pointing logo to a transparent PNG that fails Google's minimum dimension requirements, causing it to be skipped in rich results.
  • Placing the Organization block on every page of the site. It belongs on the homepage or About page — once, not everywhere.

For related implementation guidance, see my notes on WebSite schema markup and Person schema markup — these three types form the identity layer most sites need before moving on to content-type markup. For sites using hierarchical navigation, adding BreadcrumbList schema markup is the natural next step after the identity layer is in place. For a review of your entire structured data setup, schema markup consulting is where I can help directly.