Read This First — Organization Is Entity Work, Not Page Work
Every other schema type on this site aims at a rich result. Organization does not, and that difference explains everything about how to use it.
No stars, no price, no carousel, no card. If you add it expecting your listing to look different tomorrow, nothing will happen.
What it actually does is define your brand as an entity. Search engines maintain a knowledge base of things they recognise, and they try to work out which of those entities a given website represents. Without explicit signals, that inference comes from scattered mentions across the web, which is error-prone and produces confident wrong answers. Organization markup replaces the guesswork with a declaration.
| What it supports | Detail |
|
Knowledge Panel eligibility |
Contributes to it, does not guarantee it |
|
Entity disambiguation |
Separates you from similarly named organisations |
|
E-E-A-T signals |
Verified identity, founding history, authoritative profile links |
|
AI system recognition |
Increasingly how AI answers identify and cite a brand |
|
A foundation for other markup |
LocalBusiness, Article publisher, Product brand all reference it |
Reports suggest four to eight weeks for new entity connections to be verified and reflected. This is not a change you check the next morning.
Panels rarely appear without press coverage from sources Google recognises, plus consistent identity signals across platforms. Markup is a necessary input, not a sufficient one.
Why You Are Here
The first situation is establishing brand identity for a site that has none declared. Most sites publish nothing machine-readable about who owns them, leaving search engines to infer it.
The second is fixing an incorrect Knowledge Panel or entity association, where the wrong logo, an outdated name, or a competitor's details have become attached to your brand.
The third is foundational work before other markup. Article schema references a publisher, Product schema references a brand, LocalBusiness inherits from Organization. Getting the Organization entity right first makes everything else more coherent.
What This Tool Does
The Organization Schema Generator builds valid Organization JSON-LD from a simple form.
Enter your organisation name, URL, logo, description, address, contact details, and social profile links, and the tool assembles correctly structured JSON-LD with ImageObject, PostalAddress, and ContactPoint nested properly, with the script tag included. Copy it and paste it into your page.
Organization or LocalBusiness
These overlap, and choosing wrongly is common.
| Your situation | Type |
|
Premises customers can visit |
LocalBusiness subtype |
|
Service-area business travelling to customers |
LocalBusiness subtype |
|
Purely online, no public premises |
Organization |
|
Online shop with no storefront |
Organization |
|
Multi-location company |
Organization at brand level, LocalBusiness per location |
|
Charity, school, or institution |
Organization subtype such as NGO or EducationalOrganization |
A multi-location company uses Organization on its main or about page to establish the brand entity, and a LocalBusiness block on each individual location page.
Property Reference
| Propert | Status | Notes |
|
name |
Required |
Errors if missing |
|
logo or image |
Required |
Errors if both are missing |
|
url |
Strongly recommended |
Your canonical homepage |
|
@id |
Strongly recommended |
A stable identifier for the entity |
|
sameAs |
Strongly recommended |
Array of authoritative profile URLs |
|
description |
Recommended |
One clear sentence about what you do |
|
legalName |
Recommended |
Registered name, if it differs from trading name |
|
address |
Recommended |
PostalAddress object |
|
contactPoint |
Recommended |
Structured contact details |
|
telephone |
Recommended |
Full international format |
|
|
Recommended |
Public contact address |
|
foundingDate |
Recommended |
ISO 8601, supports entity history |
|
founder |
Optional |
Person object |
|
numberOfEmployees |
Optional |
QuantitativeValue |
|
parentOrganization |
Optional |
If you are a subsidiary |
|
subOrganization |
Optional |
Divisions or franchises |
|
vatID, taxID, duns |
Optional |
Strong identity verification signals |
|
aggregateRating |
NOT ELIGIBLE |
See the review section below |
Host it on your own domain, use at least 112 by 112 pixels with 512 by 512 preferable for high-resolution panels, keep it in JPG, PNG, or SVG, and make sure it is crawlable and not blocked in robots.txt. A logo Google cannot fetch is a logo that cannot appear.
Giving your organisation a stable identifier, typically your homepage URL with a fragment such as #organization, lets every other schema block on your site reference the same entity rather than creating a new one each time. It is what turns scattered markup into one coherent graph.
sameAs — The Property That Does the Heavy Lifting
If you add one thing beyond name and logo, make it sameAs. It is how you connect the entity on your site to the same entity as it appears elsewhere, which is exactly what disambiguation requires.
| Priorty | Profiles |
|
Highest value |
Wikipedia article, Wikidata entry, Crunchbase profile, LinkedIn company page |
|
Also useful |
X, Facebook, Instagram, YouTube, GitHub for tech companies, industry directories, Companies House or equivalent registry |
The same name spelling, the same logo, the same one-line description, the same primary website link across every profile. Inconsistent signals create disambiguation work rather than removing it.
Example Output
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Digital",
"legalName": "Example Digital Limited",
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png",
"width": 512,
"height": 512
},
"description": "A digital product studio building tools for
small businesses.",
"foundingDate": "2019-04-12",
"founder": { "@type": "Person", "name": "Alex Morgan" },
"address": {
"@type": "PostalAddress",
"streetAddress": "18 Bridge Street",
"addressLocality": "Manchester",
"postalCode": "M3 3AB",
"addressCountry": "GB"
},
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "+44 161 496 0000",
"contactType": "customer support",
"email": "support@example.com",
"availableLanguage": ["English"],
"areaServed": "GB"
}
],
"sameAs": [
"https://en.wikipedia.org/wiki/Example_Digital",
"https://www.wikidata.org/wiki/Q00000000",
"https://www.linkedin.com/company/example-digital",
"https://x.com/exampledigital",
"https://github.com/exampledigital"
]
}
Organization Subtypes
As with LocalBusiness, a more specific type carries more meaning.
| Organization | Subtype |
|
Charity or non-profit |
NGO |
|
School, college, university |
EducationalOrganization |
|
Government body |
GovernmentOrganization |
|
Medical practice or hospital |
MedicalOrganization |
|
Sports club |
SportsOrganization |
|
Newspaper or publisher |
NewsMediaOrganization |
|
Company or business |
Corporation, or Organization |
|
Airline |
Airline |
Connecting Your Entity Graph
Organization becomes considerably more useful when other markup references it rather than repeating it.
// Article publisher
"publisher": { "@id": "https://example.com/#organization" }
// Product brand
"brand": { "@id": "https://example.com/#organization" }
// Relationships between organisations
"parentOrganization": { "@id": "https://parent.com/#organization" }
Reviews — Organization Cannot Show Its Own Stars
Organization is the second type Google names in the self-serving review restriction, alongside LocalBusiness.
This has applied since September 2019. Testimonials on your own site marked up with Organization and aggregateRating will not produce stars, and embedding a third-party review widget does not change that, since Google's wording covers widgets explicitly.
Google has confirmed self-serving review markup does not trigger a manual action. The stars simply will not appear.
On a site that reviews OTHER organisations, such as a directory or review platform. For employer reviews specifically, Google directs you to EmployerAggregateRating rather than a standard review snippet.
Common Mistakes to Avoid
Organization schema contributes to Knowledge Panel eligibility but does not create one. Panels typically require press coverage from sources Google recognises, consistent identity signals across platforms, and time for the Knowledge Graph to reprocess, which reports put at four to eight weeks. Markup is one input among several, and treating it as a switch leads to disappointment.
sameAs does most of the disambiguation work, and leaving it out wastes the property that matters most. Equally, a list of five minor social profiles is far less useful than a Wikidata entry and a LinkedIn page. Prioritise entity databases and authoritative profiles over volume, and make sure the details on those profiles match what your markup says.
Writing out the full organisation object inside every Article publisher and Product brand field creates multiple separate entities that search engines then have to reconcile. Define the organisation once with an @id, then reference that @id everywhere else. One entity referenced many times is coherent; the same details repeated many times is not.
Quick Reference
| Item | Detail |
|
Type |
Organization or a specific subtype |
|
Rich result |
None, by design |
|
Purpose |
Entity definition and disambiguation |
|
Required |
name, plus logo or image |
|
Most valuable |
sameAs and @id |
|
Logo |
Own domain, 512px preferred, crawlable |
|
sameAs priority |
Wikidata, Wikipedia, LinkedIn |
|
Knowledge Panel |
Contributes, does not guarantee |
|
Reprocessing |
Reported at four to eight weeks |
|
Physical premises |
Use LocalBusiness instead |
|
Placement |
Once per site, homepage or About |
|
Other markup |
Reference by @id, do not repeat details |
|
Own reviews |
No stars, no penalty either |
