Guide : Organization Schema

TL;DR — Organization schema is a petit block of code que indique search engines who votre business is — votre nom, logo, official website, and social profiles. Unlike la plupart schema, it describes votre company itself, pas le contenu on une page. It helps Google recognize and correctement identifier votre brand, and it may influence afficher elements comme the info box (a “Knowledge Panel”) some brands obtenir in search. It fait pas guarantee que panel, and it fait pas faire vous rank plus élevé.

Ce que Organization schema is

La plupart balisage de données structurées describes what’s on une page — a product’s price, a recipe’s cook temps, a examiner score. Organization schema is différent. It describes the business behind the whole site: votre nom, votre logo, votre official URL, votre social accounts, parfois votre adresse and contact details.

It uses the shared schema.org vocabulary, written as a block of code (JSON-LD) que sits in lune page sans modification how it semble. Quand Google reads it, the message is essentially: “This is who we are.”

Pourquoi it’s worth ajout

Its principal job is helping moteur de recherches identifier votre brand and tell it apart from autre companies with similaire noms. Google’s propre language is deliberately bounded: ajout ce markup “peut aider Google meilleur comprendre votre organization’s administrative details and disambiguate votre organization in résultats de recherche,” and some properties “can influence visual elements in Search results” — choses comme qui logo montre up, or details in the Knowledge Panel, the info box with a logo, liens, and details que some brands obtenir on the correct side (or top) of search results.

“Can help” and “can influence” ne sont pas guarantees. Google doesn’t créer a Knowledge Panel simplement parce que the markup exists — panel afficher dépend on how well-known and well-corroborated the entity is à travers the web. Votre markup is un input Google peut utiliser, pas a switch que turns a panel on.

The choses beginners obtenir incorrect

• It doesn’t guarantee a Knowledge Panel. Correct markup helps; it doesn’t force Google to montrer a panel.
• It’s pas a ranking boost. Organization schema won’t déplacer vous up le résultats. Its objectif is identity and afficher, pas ranking.
• Put it in un placer, pas everywhere. Google recommends the homepage or a unique page que describes votre organization, tel as an “About” page, and dit vous don’t besoin it on every page of le site.
• The logo has a réel minimum size: au moins 112x112 pixels, and the image has to be reachable by Google (pas blocked).

Vouloir the complet property liste, the November 2023 expansion, how sameAs really fonctionne, and the exact échec modes? Switch to the Avancé tab.

TL;DR — Organization schema (schema.org/Organization, JSON-LD) describes the entity behind le site — nom, logo, url, sameAs, plus administrative fields — and its documented job is disambiguation, and some properties peut influence visual elements comme Knowledge Panel/attribution UI — pas ranking. Neither is guaranteed. Google dit là are aucun requis properties (ajouter what’s relevant), and it recommends une fois on the homepage or an À propos de page — Mueller compares site-wide duplication to review-markup spam. The logo nécessite to be ≥112x112px and crawlable/indexable. The November 2023 mettre à jour folded the old Logo docs into Organization and ajouté administrative fields (address, legalName, duns, leiCode, naics, iso6523Code, numberOfEmployees, foundingDate). The commerce-adjacent fields (hasMerchantReturnPolicy, hasMemberProgram, hasShippingService) came plus tard, in separate 2024–2025 updates — pas the 2023 batch. And the core myth to kill: markup ≠ guaranteed Knowledge Panel, and it’s pas a ranking factor.

Ce que Organization schema en réalité fait

Google’s propre framing is precise: ajout Organization données structurées to votre home page “peut aider Google meilleur comprendre votre organization’s administrative details and disambiguate votre organization in résultats de recherche.” Two words là matter — comprendre and disambiguate. Ce markup is how vous tell an engine qui “Acme” vous are, separate from every autre Acme, and hand it the administrative facts (logo, official liens, identifiers) it uses to represent vous.

Google aussi splits the properties by objectif: “Some properties are utilisé behind the scenes to disambiguate votre organization from autre organizations (comme iso6523 and naics), pendant que others peut influence visual elements in Résultats de recherche (tel as qui logo is affiché in Résultats de recherche and votre knowledge panel).” So the markup fait two jobs — quiet identity confirmation, and a possible influence on visible UI comme the logo and Knowledge Panel details. Neither of ceux is a ranking lever, and neither is a guarantee — Google’s propre verbs are “can help” and “can influence,” pas “will show” or “will rank.”

Ce is the entity couche of données structurées. It sits alongside the Entity & Identity Schema hub, and its fermer relatives — LocalBusiness Schema (a subtype pour businesses with a physical emplacement and hours) and Person Schema (pour individuals and authors) — do the même identity job pour différent entity types. Organization is the un vous utiliser pour the company or brand itself.

Aucun requis properties — ajouter what’s relevant

Ce surprises personnes: Google states “Là are aucun requis properties; à la place, we recommend ajout as nombreux properties que are relevant to votre organization.” A sparse-but-accurate block (nom, logo, url, a few bon sameAs) is legitimate and souvent meilleur que a padded un stuffed with guessed identifiers. Google doesn’t nom a défini “core,” but name, logo, url, and sameAs are a reasonable practical starting point — they’re the ones la plupart tied to the visible/disambiguation elements Google describes.

Où to put it — and pourquoi pas every page

Placement is a documented rule, pas a preference: “We recommend placing ce information on votre home page, or a unique page que describes votre organization, Par exemple the à propos de us page. Vous don’t besoin to inclure it on every page of votre site.”

John Mueller has reinforced ce directement. His guidance is que Google seulement nécessite to trouver it somewhere obvious — the home page or contact/À propos de page — and he warned contre le site-wide instinct by comparison to review-markup spam: putting company markup on every page in the hope of getting an enhancement everywhere is the incorrect mental model, the même mistake as sprinkling examiner stars à travers a whole site. (Paraphrased from Mueller’s comments as reported by Moteur de recherche Journal; treat as a paraphrase, pas a verbatim quote.)

The practical takeaway is unchanged: un instance, on the homepage or À propos de page.

The complet property liste (and the November 2023 expansion)

Google’s pris en charge Organization properties, as documented:

address · alternateName · contactPoint · description · duns · email · foundingDate · globalLocationNumber · hasMerchantReturnPolicy · hasMemberProgram · hasShippingService · iso6523Code · legalName · leiCode · logo · naics · name · numberOfEmployees · sameAs · taxID · telephone · url · vatID

The administrative batch — legal nom, adresse, contact info, business identifiers (duns, leiCode, naics, iso6523Code), numberOfEmployees, foundingDate — arrived in November 2023, quand Google folded the old standalone Logo structured-datune page into the Organization documentation and expanded bien au-delà the original logo + url pair. Sites que déjà had logo + url markup didn’t besoin to modifier anything. (The November 2023 expansion is summarized from Google’s blog announcement, qui couldn’t be re-fetched verbatim during research — treat the specifics as paraphrase.)

The commerce-adjacent objects are pas partie of que 2023 batch — chaque landed in its propre, plus tard mettre à jour, confirmed contre Google’s live search-updates history:

• hasMerchantReturnPolicy (organization-level retourner policies) — ajouté June 11, 2024.
• hasMemberProgram (loyalty programs) — ajouté June 10, 2025.
• hasShippingService (shipping policies) — ajouté November 12, 2025.

Chaque of ceux has its propre documentation, availability rules, and precedence behavior contre product-level markup and Merchant Center settings. Valid Organization markup doesn’t by itself guarantee Merchant Center acceptance or Search afficher pour quelconque of les.

Groupe the rest roughly comme ce:

• Core identity: name, alternateName, legalName, url, logo.
• Contact / emplacement: address, contactPoint, telephone, email.
• Business identifiers (disambiguation): duns, leiCode, naics, iso6523Code, globalLocationNumber, taxID, vatID.
• Profiles: sameAs.
• Org-level facts: numberOfEmployees, foundingDate.
• Commerce & membership (separately dated, voir ci-dessus): hasMerchantReturnPolicy, hasShippingService, hasMemberProgram.

sameAs: ce que it’s pour, and ce que belongs là

sameAs is the identity-confirmation lever. Google’s propre description: it’s “the URL of une page on un autre website with additional information à propos de votre organization” — its exemple is a social media or review-site profile page. Schema.org’s broader definition is a bit stricter: a référence page que “unambiguously indicates the item’s identity,” comme a Wikipediune page, a Wikidata entry, or the official website. En pratique, point it at pages que reliably represent votre organization — official social accounts, Wikipedia, Wikidata, Crunchbase, LinkedIn — but neither definition exige vous to literally propre every URL; une page vous don’t operate (a verified Wikipedia entry, Par exemple) encore qualifies si it unambiguously identifies vous. The job is disambiguation, pas link-building.

Two cautions. Premier, sameAs is pas itself a ranking factor and ne fait pas guarantee a Knowledge Panel — it’s un corroborating signal among the nombreux Google weighs. Second, a sameAs pointing at the incorrect profile (a différent company’s page, an unrelated Wikipedia entry) peut actively confuse the entity match. Tester votre sameAs valeurs as carefully as you’d tester a canonical.

sameAs aussi obtient confused with knowsAbout, qui is a différent property entirely: sameAs = identity (qui entity vous are), pendant que knowsAbout = topical expertise (ce que the entity is knowledgeable à propos de). Ils aren’t interchangeable and don’t do the même job.

Logo requirements and courant échecs

The logo has hard requirements: per Google’s docs, “the image doit be 112x112px, at minimum. The image URL doit be crawlable and indexable.” Où ce silently fails:

• Aussi petit — sous 112x112px and it won’t qualify même si the JSON-LD validates.
• Blocked — the image URL is disallowed in robots.txt or behind a redirection chain Google can’t resolve, so it can’t récupérer it.
• Incorrect image — the markup points at something que isn’t votre réel on-page logo.

A JSON-LD block peut validate perfectly and encore échouer to produce the logo vous wanted parce que the image didn’t meet ces conditions.

Exemple JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Co",
  "legalName": "Example Company, Inc.",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://en.wikipedia.org/wiki/Example_Co",
    "https://www.crunchbase.com/organization/example"
  ]
}

Placer que une fois — homepage or À propos de page. Ajouter address, contactPoint, and identifiers seulement où they’re accurate.

Reusing the Organization node à travers votre graph (optional)

Si votre site emits multiple JSON-LD nodes — a WebSite, a Person/author node, an Article publisher — vous pouvez give the Organization a stable @id and référence que même @id from the autre nodes au lieu de repeating the complet object:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Co",
      "url": "https://example.com/",
      "logo": "https://example.com/logo.png"
    },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "https://example.com/",
      "publisher": { "@id": "https://example.com/#organization" }
    }
  ]
}

Ce isn’t a Google requirement — leur docs don’t mandate an @id or quelconque particulier graph shape. It’s a graph-hygiene pratique: un canonical Organization definition que autre nodes point to, au lieu de several slightly différent copies drifting out of sync. It doesn’t modifier ranking or eligibility on its propre.

Ce que Bing fait

Bing supports schema.org markup (JSON-LD, Microdata, RDFa) and validates it contre the declared types — si a valeur doesn’t match the attendu données type, Bing’s robots d’exploration ignore que annotation, so vérifier avant publishing. Bing doesn’t apparaître to publish a dedicated Organization-specific référence comparable to Google’s; its general structured-data aider is the closest official source. Treat the Bing side of ce topic as modest in scope. (Bing’s guidance ici is paraphrased from its Webmaster Outils aider, qui couldn’t be re-fetched verbatim during research.)

Validate avant vous ship

• Résultats enrichis Tester — checks the logo/organization elements Google peut surface.
• Balisage de données structurées Validator — validates the Organization type and tout its properties, rich result or pas.
• Recherche Google Console — monitor pour structured-data errors post-deploy.

Validation confirms the markup is well-formed. It can’t confirmer you’ll obtenir a Knowledge Panel — that’s earned via broader corroboration, pas markup alone.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est: schema.org/Organization (JSON-LD) describes the entity behind le site — nom, logo, url, sameAs, plus administrative fields — pas une page’s content.
• Ce que it fait: Google dit it helps “comprendre votre organization’s administrative details and disambiguate votre organization in résultats de recherche.” Some properties peut influence visual elements comme Knowledge Panel and attribution UI — sans guaranteeing soit. It is pas a ranking factor.
• Aucun requis properties: Google explicitly dit ajouter what’s relevant; core recommended définir is name, logo, url, sameAs. Sparse-but-accurate beats padded.
• Placement: une fois, on the homepage or À propos de page — pas every page. Mueller likens site-wide duplication to review-markup spam (paraphrased).
• Logo: doit be ≥112x112px and crawlable/indexable; validating JSON-LD doesn’t aider si the image is aussi petit or blocked.
• November 2023 expansion: folded the old Logo docs into Organization and ajouté administrative fields — address, legalName, duns, leiCode, naics, iso6523Code, numberOfEmployees, foundingDate. The commerce-adjacent objects came plus tard, in separate updates: hasMerchantReturnPolicy (June 2024), hasMemberProgram (June 2025), hasShippingService (November 2025).
• sameAs: liens to pages que reliably represent the organization (Wikipedia, Wikidata, LinkedIn, Crunchbase, official socials) pour identity confirmation — pas strictly limited to pages vous propre; pas a ranking factor, doesn’t guarantee a panel, and a incorrect target peut conflate entities. Distinct from knowsAbout (topical expertise, pas in Google’s current Organization property table).
• Knowledge Panel: earned via corroboration à travers trusted sources — markup is un input, jamais a guaranteed trigger.
• Connexe types: Entity & Identity Schema (hub), LocalBusiness Schema (physical emplacement), Person Schema (individuals/authors).
• Validate: Résultats enrichis Tester + schema.org Validator + Search Console.

Documentation officielle

Primary-source documentation from the moteur de recherches.

Google

• Organization données structurées — the core référence: definition, placement guidance, the “no required properties” line, disambiguation-vs-visual split, the complet property liste, and the 112x112px logo requirement.
• Introduction to données structurées — JSON-LD recommendation and how Google uses données structurées to comprendre entities.
• Expanding markup prise en charge pour Organization details (Nov 2023) — the announcement que folded the Logo docs into Organization and ajouté the administrative fields.
• Résultats enrichis Tester — checks the surfaceable organization/logo elements.
• Balisage de données structurées Validator — validates the Organization type and every property.
• schema.org/Organization — the vocabulary itself.

Bing / Microsoft

• Bing Webmaster Outils — données structurées aider — Bing’s general prise en charge pour schema.org / JSON-LD and its type-validation behavior.

Quotes from the source

On-the-record statements from Google’s Organization structured-data documentation. Ces were verified contre the live docs page during research.

Google docs — ce que it’s pour

• “Adding organization structured data to your home page can help Google better understand your organization’s administrative details and disambiguate your organization in search results.” — Recherche Google Central, Organization données structurées.
• “We recommend placing this information on your home page, or a single page that describes your organization, for example the about us page. You don’t need to include it on every page of your site.”
• “There are no required properties; instead, we recommend adding as many properties that are relevant to your organization.”
• “Some properties are used behind the scenes to disambiguate your organization from other organizations (like iso6523 and naics), while others can influence visual elements in Search results.”
• “The image must be 112x112px, at minimum. The image URL must be crawlable and indexable.” (on the logo)

Organization schema property référence

Recommended core (identity match + possible visual-element influence)

Autre identity / contact properties

Business identifiers (disambiguation, ajouté/expanded Nov 2023)

Org-level facts (ajouté/expanded Nov 2023)

Commerce & membership (chaque ajouté separately, plus tard — pas the Nov 2023 batch)

Fast facts

• Aucun requis properties — ajouter what’s relevant; recommended core is name, logo, url, sameAs.
• Placement: Google recommends une fois, homepage or À propos de page — pas every page.
• Logo: ≥112x112px, crawlable and indexable.
• Objectif: disambiguation; some properties peut influence visual elements comme Knowledge Panel/attribution UI — pas ranking, and neither is guaranteed.
• Aucun guaranteed panel: markup is un input; panels are earned via corroboration.
• sameAs ≠ knowsAbout: identity vs. topical expertise (knowsAbout isn’t in Google’s current Organization property table).
• Validate: Résultats enrichis Tester + schema.org Validator.

Erreurs fréquentes (myths En pratique)

The échec modes I voir la plupart souvent — chaque is a réel façon to waste effort or quietly break the markup.

1. Expecting a guaranteed Knowledge Panel. Correct, complet Organization schema ne fait pas force Google to créer or mettre à jour a Knowledge Panel. Panels are earned via corroboration à travers independent, trusted sources; votre markup is un input, pas a trigger. Ship the markup, alors garder building the entity’s real-world footprint.

2. Putting it on every page. Ce is the la plupart courant structural mistake. Google’s docs dire un instance — homepage or À propos de page — is suffisant, and Mueller has comparé le site-wide instinct to review-markup spam (paraphrased). Duplicating it everywhere buys vous nothing.

3. A logo que fails silently. The JSON-LD validates, but the logo is sous 112x112px, blocked in robots.txt, behind a broken redirection, or simply the incorrect image. Google can’t utiliser ce que it can’t récupérer — validation of the markup dit nothing à propos de the image.

4. Incorrect sameAs targets. sameAs devrait point at pages que reliably represent votre organization (Wikipedia, Wikidata, LinkedIn, Crunchbase, official socials) — pas strictly limited to pages vous propre. Pointing it at a différent company’s page or an unrelated entry peut conflate votre entity with someone else’s — worse que leaving it out.

5. Treating it as a ranking lever. Organization schema’s documented objectif is disambiguation and visual/afficher elements, pas organic ranking. Ajout it (or filling every property) won’t déplacer positions.

6. Padding every property with guessed données. Là are aucun requis properties. A sparse-but-accurate block beats un stuffed with invented identifiers or valeurs you’re pas certain à propos de. Ajouter what’s vrai and relevant; leave the rest out.

7. Marking up the incorrect entity or page. Organization is pour the company/brand itself. Pour a physical emplacement with hours, utiliser LocalBusiness Schema (a subtype); pour an individual or author, utiliser Person Schema. And put the block on une page que represents the organization (home/À propos de), pas on an arbitrary content page.

Validation tests

Tester the publié entity graph

Tester to run — parse the live JSON-LD with the Schema Validator. Attendu result — un coherent Organization identity with valid URLs and seulement supportable properties. Échec interpretation — plugins/templates emit duplicates or malformed valeurs. Monitoring window — immediate. Rollback trigger — revert si the modifier breaks parsing or creates competing organization identities.

Tester logo and identity références

Tester to run — récupérer the declared logo URL and examiner url and sameAs destinations. Attendu result — every URL is public, successful, and belongs to the organization represented. Échec interpretation — an asset déplacé or an identity lien is stale/unsupported. Monitoring window — immediate and après brand/domain changements. Rollback trigger — supprimer unsupported références plutôt que leaving misleading identity claims.

Testez vos connaissances: Organization Schema

Five rapide questions on Organization schema, ce que Google uses it pour, and the mistakes que break it. Pick an réponse pour chaque, alors vérifier.

Journal des modifications