Organization Schema: A Practical Setup Guide
Organization schema is the JSON-LD block that tells search and AI engines who you are. Here is exactly which properties to fill in and how to verify it worked.
Organization schema is a block of JSON-LD that states your legal name, URL, logo and other profiles as machine-readable facts, not page copy a crawler has to infer. Add it once, keep it accurate, and every system resolving entities — a knowledge panel, an AI assistant's retrieval step — has one clear record to work from.
That single block is one piece of a larger practice: ai brand visibility is the full picture of how a company becomes a citable, correctly described entity across search and AI answers, and this guide is the narrow, mechanical part of it.
On this page
What does organization schema actually do?
It gives a structured, unambiguous answer to a question every system asking "who is this" has to solve some other way otherwise: reading prose and guessing. Google's own documentation frames the payoff as helping search "better understand your organization's administrative details and disambiguate your organization in search results" [1], and disambiguation is exactly the problem when your brand name is generic or shared with something else.
There are no required fields. That surprises people who expect a strict checklist, but it is Google's own position: implementation is optional, and no feature is guaranteed to appear because the markup exists [1]. What that means in practice is that the value comes from which properties you choose to fill in, not from technically having the tag on the page.
Which properties should you actually fill in?
Start with the ones that carry real information: name, alternateName if you go by a shorter or different form, url, logo, and sameAs. Google explicitly recommends adding "an indication of real-world presence (for example, address or telephone) and online presence (for example, url or logo)" [1], which is a reasonable floor.
Past that floor, the fuller Google list includes description, email, foundingDate, contactPoint, legalName, and sameAs for your other profiles [1]. Not every business needs every one of these; a two-person consultancy gains little from numberOfEmployees, and a private company may reasonably skip vatID. Fill in what is true and current, and leave out what would need updating every quarter.
Think of it as two tiers rather than one long list. The first tier answers "who are you, and where do you live online" — name, url, logo, sameAs. The second tier adds administrative color that helps disambiguation in edge cases: a foundingDate separates you from an older company with a similar name, a legalName distinct from your trading name clarifies which entity actually signs contracts, and contactPoint gives a system a real channel rather than a guessed one. Skip the second tier entirely and you still get most of the benefit; skip the first and the markup is close to decorative.
One property worth a specific word of caution is description. It is tempting to paste marketing copy in here, but a structured-data description is read as a factual field, not a pitch. Two or three plain sentences about what the company does, in the same register as a Wikipedia opening line, outperforms anything written to persuade — the audience for this field is software, not a reader deciding whether to buy.
| Property | Why it is worth doing first |
|---|---|
| name / alternateName | The base fact every other system checks first |
| url | Confirms which domain is the canonical one |
| logo | Feeds the logo shown in search results and panels; minimum 112×112px [1] |
| sameAs | Links your site to LinkedIn, Wikidata and any other verified profile |
| contactPoint / email | Useful, but lower leverage than the four above |
The logo property has a real technical requirement worth knowing before you paste a URL in: Google specifies a minimum of 112 by 112 pixels, a crawlable and indexable URL, and a file format its Image system supports [1]. A logo that fails silently on a transparent background is a common miss — Google's own advice is to check how it looks "on a purely white background" [1].
How do you connect it to a knowledge panel and Wikidata?
Through sameAs. This is the array of URLs — your LinkedIn company page, your X or Twitter profile, your Wikidata item if you have one — that tells anything reading the markup "these are all the same organization." It is the single property most responsible for tying independent signals together into one entity, which is exactly the mechanism behind getting a Google knowledge panel.
A Wikidata item is worth having in that list specifically because Wikidata does not require a Wikipedia article first. Its own notability rule accepts "a clearly identifiable conceptual or material entity that can be described using serious and publicly available references" [3] — meaning a real company with public coverage can qualify even with no separate encyclopedia entry. The full mechanics of creating that item are in wikidata for businesses; the short version here is that once it exists, its URL belongs in your sameAs array and nowhere else does the loop close.
Write the base block
name, url, logo and description, matching your other properties exactly — the same legal name, the same URL format, everywhere.
Add every verified profile to sameAs
LinkedIn, X, Wikidata, Crunchbase if you have one. Only profiles that actually name your organization, never a placeholder.
Place it once
Homepage or About page. Duplicating it with drifted details across templates creates the exact ambiguity the markup exists to remove.
Validate, then re-check monthly
A schema testing tool confirms the syntax parses. It does not confirm the facts are still true, which is a separate, recurring check.
What does the JSON-LD look like in practice?
A minimal, real example, trimmed to the properties worth having:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Acme Analytics",
"url": "https://acmeanalytics.com",
"logo": "https://acmeanalytics.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/acme-analytics",
"https://www.wikidata.org/wiki/Q0000000"
]
}
Notice what is absent: no keyword-stuffed description, no invented founding date, no employee count nobody bothered to update. Schema.org's own reference defines Organization as, plainly, "an organization such as a school, NGO, corporation, club, etc." [2] — a factual record, not a marketing surface. Treat it that way and it stays trustworthy the next time something reads it.
What actually breaks this markup?
Three things, in order of how often we see them. First, drift: the sameAs list gets set up once and never updated when a profile changes or a new one launches, so it quietly under-represents the entity for years. Second, duplication with contradiction: a second Organization block gets added on a landing page with a slightly different name or url, and now two records disagree about who you are. Third, a logo URL that returns a 404 or sits behind a script, which fails Google's crawlable-image requirement silently [1] — nothing errors, it simply stops counting.
A fourth, quieter failure is worth naming because it is almost invisible without checking: the markup renders correctly in the page source but only after client-side JavaScript runs. A crawler that reads the raw HTML response — which is how a good share of retrieval happens — never sees it at all. If your organization block is injected by a script rather than present in the server-rendered HTML, view the page's source (not the rendered DOM) and confirm it is actually there before assuming the setup is finished.
None of these four break the page visibly. That is what makes them expensive: a validator run once at launch says green, the team moves on, and the record quietly goes stale or invisible for a year before anyone checks it again. The fix in every case is the same low-effort habit — re-run a source check whenever a profile, a logo, or a legal name changes, not on a fixed schedule that may or may not line up with when something actually moved.
The markup itself is never the hard part. Keeping the sameAs list current as the company adds and drops profiles is the actual maintenance job, and it is the one nobody assigns to anyone.
Once your organization record is accurate, the next highest-leverage move is usually earning a mention on someone else's page rather than editing your own further — see getting featured in best-of lists for how that outreach actually works, and where it fits after the technical setup is done.
Questions people also ask
Is organization schema required for AI engines to cite my brand?
No. It is not a citation mechanism by itself, and Google states plainly that no property is required. What it does is remove ambiguity about who you are, which is a precondition for the knowledge panel and entity linking that citation tends to follow.
Where on the site should the markup live?
Your homepage and, if you have one, a dedicated About or Company page. Google's own guidance says to place it there rather than repeating it on every template page, where a stale or inconsistent copy is more likely to appear.
What is the single highest-value property to add if I only have time for one?
sameAs. It is the list of your other verified profiles, and it is the property that ties your website to your LinkedIn page, your Wikidata item and any directory listing that also names you — the connective tissue entity resolution runs on.
Do I need a Wikipedia page before I add a sameAs link to Wikidata?
No. Wikidata's own notability rule accepts a well-documented, real, identifiable entity even with no separate Wikipedia article, as long as it is backed by public references — see the sibling guide on wikidata for businesses.
Will adding this markup get me a knowledge panel?
Not by itself. It is one of several inputs a panel draws on, alongside your Google Business Profile and independent coverage. Treat it as removing a blocker, not pulling a lever.
Sources
- Organization (Organization, LocalBusiness, Corporation) — Google Search Central (checked 23 September 2026)
- Organization - schema.org — Schema.org (checked 23 September 2026)
- Wikidata:Notability — Wikidata (checked 23 September 2026)
Get an audit of your entity signals, not just a schema check
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- AI brand visibility: how to measure and grow itHow often ChatGPT, Perplexity, Gemini and Google AI Mode name or cite your brand, how to measure it on a schedule, what moves the number and what it costs.
- Wikidata for Businesses: A Setup GuideA Wikidata item is a free, structured entity record that search and AI engines can read directly. Here's who qualifies and how to create one.
- How to Get a Google Knowledge PanelGoogle Knowledge Panels are generated automatically, not requested. Here's how to qualify, claim one that already exists, and improve your odds of earning one.
- How to Get Featured in Best-Of ListsAI assistants cite third-party listicles more than brand marketing pages. Here's how to find the lists that already rank and get added to them.