Organization schema, explained
Organization describes a company, nonprofit, school or other group. Google has no required properties for it; name, url, logo, sameAs, address and contact details are the ones that matter. Put it on your home page or about page and give it one stable @id.
What it's for
Organization is the schema.org type for "an organization such as a school, NGO, corporation, club, etc." Google says Organization markup on your home page can help it understand your administrative details and disambiguate your organization in search results; some properties can influence which logo it shows, and others are used behind the scenes (Google: Organization).
If customers visit you at a physical location, use LocalBusiness, which is a subtype of Organization. Online-only shops can use OnlineStore (a subtype of OnlineBusiness).
Key properties
| Property | What it holds | |
|---|---|---|
name |
Your organization's name. Google says to use the same name as your site name. | Recommended |
url |
Your website. Google says this helps it uniquely identify the organization. | Recommended |
logo |
Logo image URL, at least 112×112 px, crawlable and indexable. | Recommended |
sameAs |
Your profiles on other sites (LinkedIn, Crunchbase, social accounts, Wikidata). | Recommended |
address |
A PostalAddress; several are allowed. |
Recommended |
telephone, email, contactPoint |
How customers reach you; phone numbers with country code. | Recommended |
legalName, alternateName |
Registered name if different; other names you go by. | Recommended |
description, foundingDate, numberOfEmployees |
Background facts, if applicable. | Recommended |
vatID, taxID, iso6523Code, duns, leiCode, naics |
Business identifiers, if applicable. | Recommended |
@id |
A stable identifier for the organization (JSON-LD, not a schema.org property). | Not a Google property, but keeps references consistent |
Google: "There are no required properties; instead, add the properties that apply to your content."
Minimal example
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Co",
"url": "https://example.com/",
"logo": "https://example.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/example-co/",
"https://www.crunchbase.com/organization/example-co"
]
}
Generate Organization markup with a form, or validate yours.
Common mistakes
- A different organization on every template. If your header, footer and blog plugin each output their own Organization with slightly different names and no shared
@id, you are describing several organizations. Pick one@idand reference it everywhere (how @id works). - Putting it on every page with conflicting details. Google recommends the home page or a single page about the organization, such as the about page; it isn't needed on every page.
- sameAs pointing at pages that only mention you, or at another company with a similar name. List only profiles that are clearly yours (what to include in sameAs).
- Review stars on your own Organization. Pages using Organization or LocalBusiness markup are not eligible for review stars when the organization controls the reviews about itself (review rules).
- A name that doesn't match the site. Google asks for the same
nameandalternateNameas your site name in WebSite markup.
Sources
- schema.org: Organization
- Google Search Central: Organization structured data (last updated 8 September 2026)
Designing one organization graph across several sites and many templates is the kind of work NRLC.ai does as schema markup and structured data consulting.