Organization and logo: what actually lands in the result

Organization is the schema.org type that describes the company or the project, not the single page: name, URL, logo, official profiles. It goes once, on the home page, and other pages reference it by identifier instead of repeating it.

What Google states

The Organization page, read on 1 November 2026, says there are no required properties and that you should add the ones that apply. Some work behind the scenes to separate your organisation from others sharing its name, for example iso6523Code and naics; others change visible elements, such as the logo in results and in the knowledge panel.

The minimum block

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://ui.eneawork.it/#organization",
  "name": "EneUI",
  "url": "https://ui.eneawork.it",
  "description": "Catalogue of UI components, blocks and icons with licence and measured counts.",
  "logo": {
    "@type": "ImageObject",
    "url": "https://ui.eneawork.it/logo-512.png",
    "width": 512,
    "height": 512
  }
}

The block has five fields and an identifier. @id is what lets other pages write {"@id": "https://ui.eneawork.it/#organization"} instead of copying the whole node: one entity, one identifier. The logo is an ImageObject with declared width and height, so Google does not have to download the image to learn its size.

Checking the node and the logo

cat > check-org.mjs ]*application\/ld\+json[^>]*>([\s\S]*?)/g)];
const nodes = blocks.flatMap(([, raw]) => {
  const data = JSON.parse(raw);
  return data["@graph"] || [data];
});
const org = nodes.find((n) => n["@type"] === "Organization");
if (!org) {
  console.log("no Organization node");
  process.exit(1);
}
console.log("sameAs profiles:", (org.sameAs || []).length);
const logo = typeof org.logo === "string" ? org.logo : org.logo?.url;
if (!logo) {
  console.log("no logo");
  process.exit(0);
}
const res = await fetch(logo);
console.log(logo, res.status, res.headers.get("content-type"));
EOF
node check-org.mjs https://ui.eneawork.it/

The script looks for the Organization node, counts the sameAs profiles and downloads the logo to check status and content type. A logo returning 404 never shows in the result, and no validator flags it as a critical error, because the markup is syntactically correct.

The properties that move something

• name and url: they must match what you use everywhere, from the footer to the social profile.
• logo: absolute URL, declared dimensions, a 200 response, and the same file on every deploy.
• sameAs: official profiles, one per platform; an abandoned profile is data that ages badly.
• description: one sentence, not a slogan; assistants use it when they cite the entity.
• One Organization only: on the home page with @id, and other nodes reference it.

The live record

The catalogue serves the same identity on every page: logo and header hold the blocks where the brand appears, and the 12,808 icons cover the rest of the interface. If the logo in the header and the logo in the markup are two different files, the result shows the first and the identity splits. Checked on 1 November 2026.

The limitation

Organization does not guarantee a knowledge panel. Google builds one when there is enough external evidence, and the markup is one source among several. The same holds for the logo in results: the markup says which image to use, it does not force that image to be used. For a new brand the markup is necessary and not sufficient.

Where to continue

The JSON-LD format and its validation are in how to add schema markup; the node describing an article is in Article schema; the page trail is in BreadcrumbList without errors. To see how assistants cite an entity, the guide is optimising for AI Overviews, and what you can control on WordPress, Wix or React components is in WordPress, Wix or React components.