Organization Schema: Tell Search Engines Who Is Behind Your Site
Organization schema describes the company behind a website: its name, logo, address, contact details, profiles elsewhere and official identifiers. Google uses it to tell organizations apart, to pick the logo in results and knowledge panels, and to read store policies. It has no required properties at all, which is exactly why it is so often left half done. Here is the full list, verified against Google's documentation on November 21, 2026.
What Organization Schema Does
Google's Organization structured data documentation says the markup helps Google understand an organization's administrative details and tell it apart from others, and it can influence the logo shown in Search results and in knowledge panels. A merchant can also put its return and shipping policies here once, instead of on every product.
Some properties work behind the scenes: Google says identifiers such as iso6523Code and naics help it tell one organization from another. Others, such as logo, can change what people see. It does not make a rich result of its own. Think of it as the record Google keeps about you, written in your own words.
It matters more as more answers come from AI systems that need to know which company a page belongs to. Clear, consistent facts in one place are easier to trust than facts scattered across pages that disagree.
Organization Properties at a Glance
Google lists no required properties. It recommends adding every property that applies. Grouped so you can see what you have and what you miss:
| Group | Recommended properties | Notes |
|---|---|---|
| Name | name, alternateName, legalName | Match your site name |
| Web | url, sameAs | sameAs takes several URLs |
| Image | logo | At least 112x112 px |
| About | description, foundingDate, numberOfEmployees | Dates in ISO 8601 |
| Contact | email, telephone, contactPoint | Phone with country code |
| Address | address | Several allowed |
| Identifiers | iso6523Code, vatID, taxID | Prefer iso6523Code |
| Other IDs | duns, leiCode, naics, globalLocationNumber | Use what you have |
| Commerce | hasMerchantReturnPolicy, hasShippingService | Store wide defaults |
| Loyalty | hasMemberProgram | Member prices, points |
Pick the Most Specific Subtype
Google recommends the most specific Schema.org subtype of Organization that matches you. The type tells parsers what kind of organization they are reading about before they read a single property.
| You are | Use this type | Also follow |
|---|---|---|
| An online shop | OnlineStore | Merchant listing rules |
| An online service | OnlineBusiness | This guide |
| A restaurant or physical store | A LocalBusiness subtype | Local business rules |
| A school or university | EducationalOrganization | This guide |
| A company in general | Organization | This guide |
Google writes that an ecommerce site should use OnlineStore rather than OnlineBusiness, and that a local business should use the most specific LocalBusiness subtype and follow the local business requirements on top of the Organization ones. A subtype inherits every Organization property, so nothing in the table above is lost by choosing one.
Do not stack several unrelated types on one entity just to cover more ground. One accurate type, filled in well, says more than three vague ones.
The Logo: Rules and Numbers
| Rule | Value |
|---|---|
| Minimum size | 112 x 112 px |
| Crawlable and indexable | ✓ |
| Format | Any Google Images format |
| Looks right on white | ✓ |
| ImageObject needs | contentUrl or url |
The crawlable rule is the one that bites. We learned it on our own site, with the favicon rather than the logo: in our SEO pass on neova.app on November 20, 2026, the favicon files sat behind a Disallow: / rule in robots.txt, so Google showed a plain letter instead of our logo next to neova.app. Allowing /favicon and /apple-touch-icon.png fixed it. A logo URL in Organization markup is subject to the same robots.txt rules. Test it with the robots.txt tester guide before you blame the markup.
Identifiers: D-U-N-S, LEI, VAT and More
Official identifiers are the strongest way to say which company you are. Google prefers one property, iso6523Code, with a prefix that names the registry:
| Identifier | iso6523Code prefix | Example |
|---|---|---|
| D-U-N-S | 0060 | 0060:123456789 |
| GS1 GLN | 0088 | 0088: plus 13 digits |
| LEI | 0199 | 0199: plus 20 characters |
The older duns and leiCode properties still work, but Google recommends the iso6523Code form. vatID and taxID should match the country in address.
A Valid Organization Schema JSON-LD Example
A small online shop with one address, two profiles and a store wide return policy:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example Outdoor",
"legalName": "Example Outdoor LLC",
"alternateName": "ExOut",
"url": "https://www.example.com/",
"logo": "https://www.example.com/img/logo-512.png",
"description": "Trail running and hiking gear, designed and shipped from Colorado.",
"email": "hello@example.com",
"telephone": "+1-303-555-0142",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main Street",
"addressLocality": "Boulder",
"addressRegion": "CO",
"postalCode": "80302",
"addressCountry": "US"
},
"sameAs": [
"https://www.linkedin.com/company/example-outdoor",
"https://www.youtube.com/@exampleoutdoor"
],
"foundingDate": "2019-04-01",
"iso6523Code": "0060:123456789",
"numberOfEmployees": {
"@type": "QuantitativeValue",
"minValue": 11,
"maxValue": 50
},
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30
}
}
</script>
The @id gives the organization a stable name inside your markup, so the publisher of an Article or the seller of a Product can point to it instead of repeating it. SEO ProCheck explains that pattern in its guide to writing JSON-LD with @id.
Where to Put It
Google recommends the home page or one page that describes the organization, such as the about page. It does not need to be on every page.
| Page | Organization markup |
|---|---|
| Home page | ✓ |
| About page | ◐ |
| Every page, full block | – |
| Article publisher, by @id | ✓ |
| Product seller, by @id | ✓ |
Pick one page as the home of the full record and keep it current. Two different full blocks on two pages, with two phone numbers, is worse than one.
Common Organization Schema Mistakes
| Mistake | Effect | Fix |
|---|---|---|
| No logo | Google picks its own image | Add a 112 px logo |
| Logo blocked by robots.txt | Logo cannot be fetched | Allow the file |
| sameAs to unrelated profiles | Mixes up identities | Only your own profiles |
| Phone differs from Business Profile | Conflicting facts | Use one number |
| Name differs from site name | Two names for one brand | Match them |
| Self served review stars | Not eligible for stars | Remove the rating |
On the last row: Google's review snippet rules say an organization's own pages with ratings it controls about itself are not eligible for review stars. SEO ProCheck's Organization schema check lists what it looks for.
Check Organization Schema With Neova
Neova reads JSON-LD, microdata and RDFa from every HTML page of a crawl and gives each type a verdict. The checks for Organization markup:
- Organization or Person Markup Lacks Identifying Properties, when Organization lacks
name,url,logoorsameAs - Organization Markup Disagrees With Google Business Profile, comparing phone and street address on the home page, through DataForSEO
- Structured Data Has Syntax Errors
- Structured Data Lacks Recommended Properties, for features Google documents
- HTML Page Has No Structured Data
- Structured Data Type Common in Its Page Group Is Missing
Neova runs on Mac, Windows and Linux, and the Free plan crawls up to 1,000 URLs with every check. See Features or download Neova.
Questions
Does Organization schema have required properties?
No. Google lists none and recommends every property that applies, starting with name, url and logo.
What size should the Organization logo be?
At least 112 by 112 pixels, in a format Google Images supports, at a URL Googlebot can crawl and index. Check that it still reads on a white background.
Should Organization schema be on every page?
No. Google recommends the home page or one page about the organization. Other pages can refer to it by its @id, for example as an article's publisher.
Organization or LocalBusiness?
Use LocalBusiness, a subtype of Organization, for a place customers visit, with an address and opening hours. Use Organization for a company in general or one that sells only online.
What should go in sameAs?
URLs of other pages about your organization that you control or that clearly describe you: social profiles, a Wikipedia article, a business directory listing. Never profiles of other companies.