Organization Schema Generator

Organization schema: required vs recommended properties

Google lists no required properties for Organization markup. Instead it asks you to add as many as apply. The table groups them by how much they matter for identifying your organization.

Property	Status	Format	Notes
Name	Recommended	Text	The name people know you by, matching your site name.
Website URL	Recommended	URL	The URL that identifies your organization.
Logo URL	Recommended	URL	At least 112×112 pixels, crawlable, and legible on a white background.
Address	Recommended	Group
Organization type	Optional	One of a fixed set
Legal name	Optional	Text	Only if different from the name.
Description	Optional	Text
Founding date	Optional	Date, YYYY-MM-DD
Email	Optional	Email address
Telephone	Optional	Phone number
Address › Street address	Optional	Text
Address › City	Optional	Text
Address › State or region	Optional	Text
Address › Postal code	Optional	Text
Address › Country code	Optional	ISO 3166-1 alpha-2 code
Contact points	Optional	Repeated group
Contact points › Type	Optional	One of a fixed set
Contact points › Telephone	Optional	Phone number
Contact points › Email	Optional	Email address
Contact points › Area served	Optional	Text
Contact points › Language	Optional	Text
Profile URLs (sameAs)	Optional	List	Social profiles, Wikipedia or Wikidata pages and other pages about you, one per line.

Is Organization markup eligible for a Google rich result?

Organization markup helps Google understand your organization and can influence details such as the logo and name in results and the knowledge panel. Google lists no required properties and recommends adding as many relevant ones as you can.

Status verified on 24 September 2026. Google’s documentation: https://developers.google.com/search/docs/appearance/structured-data/organization

About Organization structured data

Organization markup is about identity: it tells Google that a name, a logo, a set of profiles and some contact details all belong to the same organization. That helps it connect your site to the entity behind it, and can influence the name and logo it shows.

Google has removed some features that used to be associated with organization markup. Its structured data gallery no longer lists a sitelinks search box, so do not add markup for one. Focus on the identity properties: name, url, logo, sameAs and contact details.

Common Organization schema mistakes

A logo that is too small or that cannot be crawled. Google asks for at least 112×112 pixels, a supported image format and a crawlable, indexable URL.
A logo that looks wrong on a white background, such as white artwork with a transparent background. Check it on white.
Putting a name that differs from the one you use everywhere else. The name should match your site name and other profiles.
Adding Organization markup on every page. It is enough on the home page, or on an about or contact page, as long as it identifies the organization.
A sameAs list of pages that are not about you. It should link only to profiles that represent the same organization.
Inconsistent contact details between the markup, the page and your other listings.

Organization schema example

A company with a logo, address, customer-service contact point and two social profiles, as generated on this page, is shown below.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Ltd",
  "legalName": "Example Limited",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "description": "Example Ltd makes accessible project-management software for small teams.",
  "foundingDate": "2015-04-01",
  "email": "hello@example.com",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Market Street",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78701",
    "addressCountry": "US"
  },
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "contactType": "customer service",
      "telephone": "+1 555 010 2030",
      "email": "support@example.com",
      "areaServed": "US",
      "availableLanguage": "English"
    }
  ],
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://x.com/example"
  ]
}

How to use it

Fill in the organization details — the form marks each field Required, Recommended or Optional.
Watch the JSON-LD and the validation list update as you type.
Copy the JSON-LD, the HTML script tag or the Next.js snippet, or download the .json file.
Paste it into your page, then check it with Google’s Rich Results Test.

Frequently asked questions

Which properties are required for Organization schema?

Google lists none as required, and recommends including as many relevant ones as you can, such as name, url, logo, address, contact details and sameAs.

What size should the logo be?

At least 112×112 pixels, in a format Google Images supports, at a crawlable and indexable URL, and it should look right on a white background.

Where should I put Organization markup?

On your home page, and optionally on an about or contact page. It does not need to be on every page.

What is sameAs for?

It lists URLs of other pages that represent the same organization, such as social profiles and directory or encyclopedia entries, helping Google connect them.

Can I use it for a local shop?

For a business with a physical location, use LocalBusiness instead. It is a subtype of Organization and adds opening hours and coordinates.

Valid markup makes a page eligible for a rich result; it does not guarantee one. Google decides what to show. Test your page with Google’s Rich Results Test before relying on it.