Organization Schema: There Are No Required Properties (and What to Add Instead)

What is Organization schema?

Organization schema is structured data describing the entity behind a website — its name, its real-world presence, its online presence, and the identifiers that distinguish it from every other business with a similar name. Google’s stated purpose for it is to disambiguate your organization in search results. And unlike most schema types, there are no required properties — Google’s guidance is to add whichever properties actually apply to you.

That last point is worth stopping on, because almost every Organization schema guide published leads with a table of required fields. Google’s documentation says the opposite in plain language. If you have been working from a required-properties checklist, you have been working from something that was never true.

This article is the build guide for one type. Which schema types are worth deploying at all — and which of them AI assistants appear to lean on — is a separate question, answered in structured data for AI search. What follows assumes you have already decided you want an Organization entity and want to construct it correctly.

TL;DR — Key takeaways

• Nothing is required. Google says so directly. Add what applies.
• Properties split into two jobs: disambiguation (iso6523Code, naics) and display influence (logo, knowledge-panel elements).
• Use the most specific subtype — OnlineStore, a LocalBusiness subtype — not bare Organization. Choosing a subtype can add obligations.
• One page, not every page. Home page or a single about page. Sitewide injection is not recommended.
• Logo rules are stricter than most people assume: 112×112px minimum, crawlable, indexable, and legible on white.
• iso6523Code with an ICD prefix is now Google’s preferred identifier over separate duns and leiCode fields.
• Google does not guarantee anything visible comes of it, and a manual action makes the markup be ignored entirely.

There are no required properties

Google’s Organization documentation states it twice — once in the introduction and again above the property table: there are no required properties, and instead you should add as many recommended properties as apply to your page.

This is genuinely unusual. Most Google structured-data types have a required set, and violating it makes the page ineligible for a rich result. Organization does not work that way, because it is not primarily a rich-result type. Google explains the split: some properties are used behind the scenes to disambiguate the organisation — it names iso6523 and naics — while others influence visual elements, such as which logo appears in Search and in the knowledge panel.

So the question is not “which fields must I fill in to be valid?” It is “which facts about this business are worth stating in a machine-readable way?” Those are different questions and they produce different markup.

Google’s own steer is useful here. It recommends focusing on properties that are useful to your users: the name and any alternate name, an indication of real-world presence such as an address or telephone number, and an indication of online presence such as the URL or logo.

That is a good default set, and it is short. Name, URL, logo, description, an address or phone if you have one, and sameAs links. Everything beyond that should earn its place — numberOfEmployees on a consultancy’s about page is noise; vatID on a B2B site in the EU is not.

Pick the most specific subtype, not bare Organization

Most implementations use "@type": "Organization" and stop. Google recommends against that: use the most specific schema.org subtype that matches your organisation, with OnlineStore given as the example for an ecommerce site rather than the broader OnlineBusiness.

There is an asymmetry here worth knowing before you choose. Organization itself has no required properties — but if your site is about a local business with physical premises, Google recommends the most specific LocalBusiness subtypes, which carry their own required fields on top of the Organization ones. Picking a more specific type is the right call for accuracy, and it can hand you obligations the generic type never had. That is a feature, not a trap: a more specific type is a stronger claim, and a stronger claim requires more evidence.

Bare Organization remains correct when none of the subtypes genuinely fit — a consultancy, an agency, a software company with no storefront and no physical premises open to the public. Do not reach for LocalBusiness because it sounds like it produces more results. Claiming to be a local business when you are not is inaccurate markup, and Google’s guidelines are enforceable.

One page, not every page

Google’s technical guidance is direct: put this information on your home page, or a single page that describes your organization, such as an about page — and it explicitly says you do not need to include it on every page of your site.

Sitewide injection is a common CMS-plugin default, and it is not what Google asks for. It also creates a maintenance problem, because the same entity now exists in eighty places and drifts in seventy-nine of them.

The pattern that works: one full Organization entity on one canonical page, and everywhere else that needs to reference the publisher, reference it by @id rather than restating it. That keeps a single source of truth and makes the entity graph explicit instead of duplicated — which is the same discipline that makes the author side of the graph work in E-E-A-T and author entity signals.

The logo rules are stricter than people assume

logo is one of the few Organization properties with hard constraints, and each of them fails quietly. Google publishes the logo constraints:

• The image must be at least 112×112px.
• The image URL must be crawlable and indexable.
• The file format must be supported by Google Images.
• It must look how you intend on a purely white background — Google specifically warns that a mostly-white or grey logo may not.

The second one catches people most often. A logo served from an asset host that is blocked in robots.txt, or sitting behind a noindex, cannot be used no matter how correct the markup is — the same class of problem as anything else that is served but never indexed. Check the image URL the way you would check a page.

The fourth is the one nobody tests. If your brand mark is white with a transparent background, it renders as nothing on the white surfaces Google puts it on. That is not a markup error and no validator will flag it.

If you use the ImageObject type rather than a plain URL, the ImageObject alternative must carry a valid contentUrl or url following the same rules.

The identifiers that do disambiguation work

This is the part almost no guide covers, and it is where the disambiguation actually happens.

iso6523Code is now the preferred identifier. Google encourages iso6523Code over the separate duns and leiCode fields. The format is an ICD prefix, a colon, then the identifier. The common ICD values Google lists are 0060 for a Dun & Bradstreet DUNS number, 0088 for a GS1 Global Location Number, and 0199 for a Legal Entity Identifier. So an LEI becomes "iso6523Code": "0199:724500PMK2A2M1SQQ228".

If you already emit duns or leiCode, this is a small, high-value change — you are moving from a field Google says it would rather you replaced to the one it prefers.

vatID is a user-facing trust signal. Google describes it as an important trust signal for users on the grounds that people can look the business up in public VAT registries. For a European B2B company this is one of the cheapest credibility signals available, and virtually nobody emits it.

name and alternateName must match your site name. Google says to use the same name and alternateName that you’re using for your site name. If your markup says “Acme Software Ltd” and your site name says “Acme”, you are describing two entities.

sameAs is external corroboration. It takes URLs of pages on other websites carrying additional information about the organisation, and you can provide several. This is the property that connects your assertion to independently verifiable profiles, which is the same mechanism that underpins entity confidence in topical authority. Point it at profiles that genuinely describe the same entity and that you control or are named on — not at every social account that exists.

What it will not do

Two limits, both stated by Google, and both worth setting expectations against before anyone asks why the knowledge panel has not changed.

Nothing is guaranteed. Google does not guarantee that features that consume structured data will show up in search results. Correct markup makes you eligible for a set of behaviours. It does not purchase them. This is the same expectation-setting that applies across rich results generally, and it is the honest framing to give a stakeholder.

Inaccurate markup can be worse than none. Google warns that violating the structured-data guidelines may trigger a manual action, and that when a structured-data manual action is applied, the structured data on the page is ignored — the page can still rank, but the markup stops doing anything. So an Organization block claiming a physical address the business does not have, or a LocalBusiness type it does not qualify for, is not a harmless exaggeration. It is a route to having all your markup discounted.

Markup describes reality. It does not create it. The other types in this cluster follow the same rule — breadcrumb and FAQ schema both fail in exactly this way when they describe something the page does not contain — and the construction detail for the types that do produce visible results is in creating rich snippets with JSON-LD.

Whatever you deploy, re-check it on a cadence rather than at launch. Entities drift: sameAs URLs move, addresses change, legal names change at incorporation events. A quarterly sweep inside the recurring technical SEO audit catches that; nothing else will, because none of it produces an error.

Frequently asked questions

Which Organization schema properties are required?

None. Google’s documentation states there are no required properties and recommends adding whichever recommended properties apply to your organisation. Guides that publish a required-fields table for this type are wrong. A sensible default set is name, URL, logo, description, sameAs, and an address or telephone number if you have one.

Where should Organization schema go?

On your home page, or on a single page that describes the organisation such as an about page. Google explicitly says it does not need to be on every page. Reference it by @id from elsewhere instead of repeating it sitewide.

Should I use Organization or LocalBusiness?

Use the most specific subtype that genuinely matches. LocalBusiness subtypes are for businesses with physical premises, and they bring their own required and recommended fields in addition to the Organization ones. If you have no premises open to the public, bare Organization — or a subtype like OnlineStore for ecommerce — is the accurate choice.

Does Organization schema produce a rich result?

Not in the way Product or Review markup does. Google frames it as helping disambiguate your organisation, with some properties influencing visual elements such as which logo is shown in Search and in the knowledge panel. Treat it as entity clarification, not as a SERP feature you are buying.

What size does the logo need to be?

At least 112×112px. The URL must also be crawlable and indexable, the format must be one Google Images supports, and the image must look as intended on a purely white background — which is the constraint that quietly breaks white or very light logos.

How many sameAs links should I include?

As many as genuinely describe the same entity. There is no stated limit. The value is corroboration, so a handful of authoritative profiles that clearly refer to your organisation is worth more than an exhaustive list of every account anyone ever registered.

Does Organization schema help with AI search visibility?

It contributes to a clear, machine-readable entity, which is the same thing publisher identity depends on. But no assistant documents how it consumes Organization markup, and there is no measurement to point at, so anyone promising a citation uplift from it is guessing. What can be said about schema and AI citations is in the structured data for AI search guide linked above.