What Is Organization Schema?
Organization schema is structured data that states in machine-readable form who publishes a website: the entity behind it, its administrative details, and the profiles it controls elsewhere.
Organization schema is structured data that states in machine-readable form who publishes a website: the entity behind it, its administrative details, and the profiles it controls elsewhere. It is not a credential you award yourself. The markup makes your claims legible to a parser, which is a different thing from making them credible to anyone.
Why declaring the entity is worth doing
Without it, Google works out who you are by inference. It reads your footer, your About page, your contact details and whatever third-party sources mention your name, then decides which of the several businesses using that name you happen to be. Usually it gets there. Sometimes it does not, and the failure is expensive.
The visible symptoms are a knowledge panel that pulls the wrong logo, brand searches that surface a competitor with a similar name, or an entity that never consolidates at all. Markup does not invent any of this. It states plainly what your site already communicates, which means the underlying pages have to communicate something worth stating. If nothing on the site establishes who runs the business or why they would know, the fix is the pages that carry your credibility, not the markup describing them.
How Google reads organisation markup
- It belongs on one page, not all of them. Google’s documentation recommends placing it on your home page or a single page describing the organisation, such as an about page, and states you do not need it on every page of the site.
- Nothing is mandatory. The Organization documentation lists no required properties. You add the ones that apply, which is unusual and tells you how the data is used: as corroboration, not as a form to complete.
- Some properties work silently, others are visible. Google says identifiers such as iso6523 and naics are used behind the scenes to disambiguate your organisation from others, while properties such as logo can influence visual elements in Search results and the knowledge panel.
- The format is a script block, not visible text. JSON-LD in the head or body is what Google recommends, and it sits alongside every other type you publish. The general rules on how structured data is read still apply: it has to represent the page honestly.
- sameAs is the corroboration hook. It points at profiles you demonstrably control on other platforms, which is how a standalone claim on your own domain becomes something checkable.
Read the property list as two groups. One group resolves ambiguity about identity; the other affects presentation. Neither group is a ranking input.
| Property | What it is doing |
|---|---|
| name and legalName | Separates the trading name from the registered entity |
| url | Anchors the organisation to a specific domain |
| logo | Can influence which logo Google shows in Search and the knowledge panel |
| sameAs | Links the entity to profiles it controls elsewhere |
| vatID, naics, iso6523 | Disambiguation behind the scenes, never displayed |
| address and contactPoint | Administrative detail Google can associate with the entity |
The blunt version
Organization markup does not create E-E-A-T. There is no property for experience, none for expertise, and nothing you can set to true that makes a business authoritative. Look at the property list and the point becomes obvious: it holds names, identifiers, addresses and links. Those describe an entity. They do not evaluate one.
A well-marked-up untrustworthy business remains an untrustworthy business, now described precisely. That is the trade the industry keeps getting wrong. Schema plugins are sold as trust packages because trust is the thing clients want and markup is the thing that can be delivered in an afternoon. One is a business problem and the other is a code change, and only one of them appears on an invoice.
What markup genuinely buys you is disambiguation: Google knowing which entity your site belongs to and which off-site signals attach to it. That is worth having, and it is a smaller claim than the one usually made. If you want the larger outcome, the work sits in named authors, verifiable credentials, real corroboration from sources you do not own, and everything else covered in what trustworthy content means to Google. Markup describes that work. It cannot substitute for it.
Example
Say two independent firms trade as Meridian Legal, one in Leeds and one in Auckland, both with .com domains. Neither publishes Organization markup. Google has to decide which mentions, reviews and citations belong to which business, and it does so from context alone. The Leeds firm then adds markup on its home page: legal name, registered address, VAT identifier and sameAs links to the profiles it actually controls. Nothing changes in the rankings that week. What changes is that the entity resolves cleanly, and the reviews earned in Leeds stop being ambiguous. The markup did not make the firm more credible. It made the credibility it already had attach to the right company.
FAQ
Does Organization schema improve rankings?
Not on its own. Google describes it as helping Search better understand your organisation’s details and disambiguate you from other organisations. That is an identity function, not a scoring one. Sites with excellent markup and thin content rank exactly as their content deserves, which is the whole point of the distinction.
Which pages should carry the markup?
Your home page, or a single page that describes the organisation such as an about page. Google’s documentation states you do not need it site-wide. Repeating identical Organization markup on every URL adds weight to your pages and gives Google nothing it did not already have from the first instance.
What belongs in sameAs?
Profiles the organisation genuinely controls, and only those. Listing a Wikipedia article you did not write or a directory entry you cannot edit misrepresents the relationship. Two or three accurate profiles do more for entity resolution than a dozen speculative ones, because the property is a corroboration link rather than a citation list.
Related terms
- JSON-LD vs Microdata — the two ways of expressing this markup, and why one of them is recommended.
- Unlinked Brand Mention — entity corroboration you cannot declare yourself, which is where the harder work sits.
- Schema Markup — the wider vocabulary that Organization is one type within.
If someone quotes you for E-E-A-T schema, ask which property carries the expertise. There is not one, and the answer to that question tells you what the rest of the proposal is worth.