Schema Markup·4 min read

Organization Schema and Knowledge Panels: A Guide

Type your company name into Google and look at the right side of the page. If a panel appears with your logo, description and profiles, Google has a clear picture of your company. If it doesn't, or the panel shows someone else's data, you have an identity problem that content alone won't fix. Organization markup doesn't create a knowledge panel, but it is the clearest first-party statement of who you are, and this guide covers how to make that statement well.

Open the free Organization Schema Generator All insights

How Organization markup feeds knowledge panels

The scenario behind the search.

Knowledge panels aren't submitted, they're inferred. Google assembles an entity from sources like Wikipedia, Wikidata, business registries, social profiles, news mentions and your website, then decides whether the evidence agrees. A startup that rebranded last year, an agency sharing a name with a bigger firm, or any company with a generic name tends to get a fragmented panel or none.

Organization markup is your contribution to that process. It states the name, legal name, logo, founding date and the exact set of profiles that belong to you, all published on the one domain you control. It doesn't guarantee a panel, but it gives Google consistent facts to check.

Logo and sameAs: the identity core

The two properties that do the heavy lifting.

Google's logo guidelines ask for a crawlable image at least 112x112 pixels, in a format Google Images supports, that looks right on a plain white background. This is the file that can appear next to your brand in search, so use a PNG or JPG of the real logo, not a tiny favicon or an SVG sprite.

sameAs is how you tell Google which profiles are yours. Each URL asserts that a LinkedIn page, X account, YouTube channel or Wikipedia article is the same organization. Quality beats volume: five active official profiles beat fifteen entries padded with dead accounts, because every link is a claim Google may check.

A worked Organization example with a sameAs array

The minimum block worth publishing.

For a fictional analytics firm, the essential markup reads: {"@type": "Organization", "@id": "https://northbeam.io/#organization", "name": "Northbeam Analytics", "url": "https://northbeam.io", "logo": "https://northbeam.io/logo.png", "sameAs": ["https://linkedin.com/company/northbeam", "https://x.com/northbeamhq"]}.

A handful of properties, and the entity is anchored: a name, the main domain, a logo and two profiles. The @id gives the company a fixed identifier, so Article, Service and other markup on your site can point to it with a short reference instead of repeating the details. In the Organization Schema Generator, once the website URL is filled, a Use link under the Entity @id field sets it to that URL plus #organization.

Start with the minimum and grow it as facts settle. A young company whose address changes every year is better served by five accurate properties than fifteen that need regular correction, because a wrong fact costs more than a missing one.

Types, identifiers and auto-fill

What the fuller form adds.

Paste your homepage URL and press Auto-fill from website. The crawler reads your homepage plus contact and about pages for the name, logo, description, address, phones, emails and social links, and it leaves anything you've typed alone. Then pick a more specific type if one fits, such as Corporation, OnlineStore or NGO; the dropdown has eleven.

The form also has fields for the business identifiers Google's documentation lists: VAT ID, tax ID, DUNS, LEI, NAICS and ISO 6523 codes. Fill only the ones your business actually has. Add contact points for each department, with languages, a founder, a brand and knowsAbout topics, then copy the script or download it as a .json file.

Organization vs LocalBusiness: choosing the right type

Entity identity or physical presence.

The answer is clean. LocalBusiness, a subtype of Organization, exists for places customers visit or areas a business serves: it adds opening hours, geo coordinates and price range. Organization is for the company as an entity, independent of any door people walk through.

A software company, a publisher or a fully remote agency wants Organization. A dental office wants LocalBusiness, built with the Local Business Schema Generator, which has the hours and map fields. A company with headquarters plus retail locations can use both, Organization for the company and LocalBusiness per location, joined through consistent names and @id references.

Organization schema mistakes that muddy your identity

Self-inflicted damage.

The recurring failures are all consistency problems:

Different organization names across markup, footer, LinkedIn and registries, leaving Google several candidate entities instead of one.
A logo URL that breaks after a redesign, silently removing your image from consideration.
sameAs arrays containing personal accounts, dead profiles or a directory you don't control.
Two conflicting Organization blocks on the same site, often one from a plugin and one added by hand, each claiming different facts.

Habits that keep Organization markup trustworthy

Treat it like configuration.

Generate one main block and publish it on your homepage or about page. Google doesn't need it on every page, and if your template adds it sitewide, every copy must be identical. Recheck the markup after every rebrand, address change or social account move; stale identity data is worse than sparse data.

Use knowsAbout deliberately: a handful of topics your company demonstrably publishes on connects the entity to a subject area. If you support customers in several languages, keep the language lists on your contact points accurate too.

Organization Schema Generator among the related tools

The entity hub and its spokes.

Founders who are public figures deserve their own markup from the Person Schema Generator, linked back through worksFor. Your about page can carry AboutPage markup from the About Page Schema Generator, with this same organization as its main entity, referenced by the same @id.

Many platforms already output some Organization markup, so check your homepage with the Schema Markup Extractor before adding a block. For a site-wide audit that compares existing JSON-LD with what each page should carry, the Automatic Schema Markup Generator crawls the whole site.

Try it now

Open Organization Schema Generator

The tool is one click away. No sign up, no upload, no payment.

Open Organization Schema Generator

Write a review