Insights

How to Add Organization Schema Markup

5 Min Read

Updated August 2026

Organization schema is a block of structured data (JSON-LD) that tells search engines and AI systems exactly who your business is: your name, your website, and how to verify you are who you say you are. It is the single most foundational piece of schema on any site, since almost every other type references it.

Quick Answer

Organization schema is a JSON-LD block added to your site that states your name, URL, description, and links to your verified profiles elsewhere on the web. Add it once, sitewide, usually through your header or footer template, and reference the same exact name and description in every other schema type on your site, since it is the foundation almost everything else builds on.

Key Takeaways

Add one Organization block sitewide rather than pasting it into individual posts, so every page loads the same consistent entity information.
Inconsistent spelling of your business name across pages is one of the most common reasons a model fails to connect the dots between mentions of you.
If you have a physical location customers visit, plain Organization schema is not enough on its own, add LocalBusiness schema instead, which extends it with an address, hours, and phone number.

What Organization Schema Actually Does

Without it, a model reading your homepage sees a business name somewhere in the header and has to guess whether that name is your legal entity, a product line, or a person mentioned in passing. Organization schema removes the guessing. It states your name, your URL, and a description in a format built for machines, and it gives you a place to list sameAs links pointing to your verified profiles elsewhere on the web, which helps a model confirm you are one real, consistent entity rather than piecing together a guess. See how this fits the bigger picture in Structured Data & Schema Markup: The Complete Guide.

The Code: A Working Example

Here is a minimal, valid Organization schema block for a small business. Paste this inside a <script type="application/ld+json"> tag, typically in your site header:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Riverside Bakery",
  "url": "https://riversidebakery.example",
  "description": "A neighborhood bakery in Portland, Oregon making sourdough bread and pastries daily.",
  "logo": "https://riversidebakery.example/logo.png",
  "sameAs": [
    "https://www.facebook.com/riversidebakery",
    "https://www.instagram.com/riversidebakery"
  ]
}

The Fields That Matter Most

name. Your exact legal or trading name, spelled the same way everywhere on your site. Inconsistent spelling across pages is one of the most common reasons a model fails to connect the dots.

url. Your canonical homepage address, not a page specific one.

description. One or two plain sentences describing what you do, written the same way it appears on your homepage.

logo. A direct link to your logo image, since some rich results pull it automatically.

sameAs. Links to your verified social and professional profiles. Add every profile that is genuinely yours and skip anything you do not control.

If you run a business with a physical location customers can visit, plain Organization schema is not quite enough. Add LocalBusiness schema instead, which extends Organization with an address, hours, and a phone number. See our LocalBusiness schema guide for the full example.

Where to Add It on Your Site

Add one Organization block sitewide, usually through your header or footer template so it loads on every page, rather than pasting it into individual posts. Google’s own Organization documentation recommends the homepage or About page as the anchor location; what matters most is that every instance states identical details. Every other schema type on your site (Article, Service, Product, and so on) should reference this exact same name and description. A model that sees three slightly different versions of who you are treats all three as less trustworthy than one it sees consistently everywhere.

How to Validate It

Paste your homepage URL into Google’s Rich Results Test, or the raw JSON-LD into Schema.org’s Validator, before you consider it done. Both will catch missing required fields and malformed JSON, and a single misplaced comma is enough to quietly break the whole block.

This is the first piece of schema we add to every site we build, before anything else. If you want your whole site’s entity signals checked at once, that is part of our AEO services.

FAQ

Do I need Organization schema if I already have a Google Business Profile?
They serve different systems. A Google Business Profile feeds Google Maps and local search directly. Organization schema is what AI crawlers and other search engines read from your own site. Most businesses need both.

What is the difference between Organization and LocalBusiness schema?
LocalBusiness extends Organization with fields a physical location needs: address, opening hours, and a phone number. If customers visit you in person, use LocalBusiness. If you operate entirely online, plain Organization is usually enough.

Can I have more than one Organization block on my site?
You can, but every instance should describe the exact same entity with the exact same name and description. Contradicting details across pages is worse than having schema on only one page.

Go deeper on structured data and entity clarity:

Want to Be the Brand AI Recommends?

Book a call and we’ll map what it takes to get there for your business.

Book a Call

Winsignia