Rich result: supported

Organization schema markup

Identifies the company behind the site, its logo, contact details and official profiles.

Does Google still show a rich result for this?

Supported, feeding the knowledge panel. As with Article, Google states there are no required properties — add the ones that apply.

When to use it

Once, on the home page or a single about-us page. Not repeated across every page of the site.

Recommended properties

name
alternateName
url
logo
address
telephone
email
description
contactPoint
sameAs
vatID
iso6523Code
legalName
foundingDate
numberOfEmployees

Example

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Ltd",
  "legalName": "Example Trading Limited",
  "url": "https://example.co.uk",
  "logo": "https://example.co.uk/logo.png",
  "vatID": "GB123456789",
  "sameAs": ["https://www.linkedin.com/company/example"]
}

Common mistakes

A logo smaller than 112 by 112 pixels, or one that does not read on a white background.
Repeating the markup on every page instead of placing it once.
Using duns or leiCode where iso6523Code is now preferred.
Using Organization where a specific subtype such as OnlineStore or LocalBusiness fits better.

Check what your own pages are missing

Our free checker reads the markup already on a page and names the types it is missing for its page type. No account needed.

Run the schema checker →

Verified against Google’s structured data documentation and its changelog on 28/07/2026. Google changes what it supports without much notice — if you are reading this long afterwards, check the current documentation before acting on it. Background on why this markup matters beyond rich results is in the answer engine optimisation guide.

Related types

LocalBusiness

Article

ProfilePage