Unit 1: Foundations · Lesson 4 of 15

Organization

Organization is the "who we are" block. Write it once, carefully, and every other piece of schema on your site can point back to it.

7 min readBeginnerOrganization, ImageObject, ContactPoint, PostalAddress

When to use it

Every business, nonprofit, school, or club with a website is an Organization. This block tells search engines and AI tools the basic facts: your name, your logo, your address, how to contact you, and which social profiles are really yours.

Google uses Organization markup to understand who's behind a site. It can feed details like your logo and name into knowledge panels and other visual elements in search. Google lists no required properties for it. It just recommends adding the ones that apply to you.

The bigger payoff is the entity idea from Lesson 1. Your Organization block gets an @id, and every other block on the site (your WebSite, your blog posts, your services) points back to it. One source of truth.

Where it goes

Google says to put Organization markup on your homepage or on a single page that describes the organization, like an About page. You don't need the full block on every page.

We'll put the full version on the homepage. Everywhere else, a page just references it by @id, like this: "publisher": { "@id": "https://fernandink.example/#organization" }. That's a pointer, not a copy. You'll see it again in Lesson 5.

The code

Here's the Organization block for our running example, Fern & Ink, a small Minneapolis design and letterpress studio. This sits on the homepage, inside the <script type="application/ld+json"> tag you learned in Lesson 3.

JSON-LD · Organization
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://fernandink.example/#organization",
  "name": "Fern & Ink",
  "legalName": "Fern & Ink Studio LLC",
  "url": "https://fernandink.example/",
  "logo": {
    "@type": "ImageObject",
    "url": "https://fernandink.example/images/fern-and-ink-logo.png",
    "width": 512,
    "height": 512
  },
  "description": "A small Minneapolis studio for brand identity design, letterpress printing, and wedding invitations.",
  "foundingDate": "2017",
  "founder": {
    "@type": "Person",
    "@id": "https://fernandink.example/about/#maya",
    "name": "Maya Lund"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "412 Main St SE",
    "addressLocality": "Minneapolis",
    "addressRegion": "MN",
    "postalCode": "55414",
    "addressCountry": "US"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "telephone": "+1-612-555-0142",
    "email": "hello@fernandink.example",
    "availableLanguage": "en"
  },
  "sameAs": [
    "https://www.instagram.com/fernandink.example/",
    "https://www.linkedin.com/company/fernandink-example/"
  ]
}

Line by line

Google has no required properties for Organization, so the tags below follow Google's recommended list. founder isn't on that list, so we've marked it optional.

PropertyStatusWhat it means
@idOptionalNot on Google's list, but we always add it. It's a permanent name tag for this entity. Use your homepage URL plus #organization. It doesn't have to load anything. It just has to stay the same.
nameRecommendedThe name people know you by, exactly as it appears on the site.
legalNameRecommendedThe registered name, if it's different ("LLC" and all).
urlRecommendedYour homepage.
logoRecommendedA plain image URL or an ImageObject. Google wants it at least 112×112 pixels, crawlable, and legible on a white background.
descriptionRecommendedOne or two plain sentences. Reuse the wording from your homepage or About page.
foundingDateRecommendedAn ISO 8601 date. A year ("2017") is fine, or a full date like "2017-04-01".
founderOptionalA Person. Give it an @id so Maya's full Person block (Lesson 11) can live on the About page.
addressRecommendedA PostalAddress. Use the two-letter country code (US).
contactPointRecommendedHow customers reach you. Include the phone in international format (+1-612-…) and/or an email.
sameAsRecommendedA list of your official profiles elsewhere. This is how you say "that Instagram account is us."

A note on logo: the simple form, "logo": "https://fernandink.example/images/fern-and-ink-logo.png", is perfectly valid too. The ImageObject version just lets you add width and height. Pick one and move on.

Organization or LocalBusiness?

LocalBusiness is a more specific kind of Organization, for businesses with a physical place customers visit or a set area they serve. It adds things like opening hours, map coordinates, and price range.

  • Use Organization for online-only businesses, publishers, brands, and parent companies.
  • Use LocalBusiness (or a subtype) when there's a storefront, office, or service area that matters to customers.

Fern & Ink has a studio people can walk into, so in Lesson 7 we'll upgrade this exact block to a LocalBusiness. Nothing you write here is wasted. Because LocalBusiness is an Organization, every property above still works.

Common mistakes

Don't copy the whole block onto every pageFive slightly different Organization blocks across your site look like five different companies. Write the full block once, then reference it by @id everywhere else.

  • Changing the @id. Once you pick https://fernandink.example/#organization, keep it forever. Other pages depend on it.
  • Listing profiles you don't control. sameAs is for your official accounts, not a directory listing someone else wrote or a competitor's page.
  • A logo that disappears. A white logo on a transparent background vanishes on white. Use a version with contrast.
  • Mismatched details. If the footer says one phone number and the schema says another, you've made the machine's job harder, not easier.

Try it

Write an Organization block for your own business or a client's. Start with just five properties: @id, name, url, logo, and sameAs. Paste it into the Schema Markup Validator and confirm it reads back the way you expect. Then add address and contactPoint, and check again.

Check yourself

  • I know Organization has no required properties in Google's docs, just recommended ones.
  • I put the full block on the homepage (or About page), not on every page.
  • My Organization has a stable @id that other pages can point to.
  • My sameAs list only includes profiles we actually own.
  • I know LocalBusiness is a more specific kind of Organization.
Go deeper on Double Atari

How these foundation types fit together on a real site: Schema Markup Explained, Part 1: Organization, WebSite, WebPage, and BreadcrumbList.