Organization schema markup: example, recommended fields and WordPress setup
Organization schema identifies who is behind a website: the company or group's name, logo, URL, contact details and its profiles elsewhere on the web. It belongs on the homepage or an About page, once per site, not on every post.
Google lists no required properties, only recommended ones. The most useful are logo, url, sameAs and the identifiers that disambiguate you from similarly named organizations. Clear Organization markup is also how AI assistants connect your site to the entity people are asking about.
JSON-LD example
Copy this into a <script type="application/ld+json"> tag and replace the values with your own.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Northfold Outdoor",
"legalName": "Northfold Outdoor Supply, Inc.",
"url": "https://example.com/",
"logo": "https://example.com/images/northfold-logo-512.png",
"description": "Northfold designs and sells hiking packs and trail gear.",
"foundingDate": "2014",
"address": {
"@type": "PostalAddress",
"streetAddress": "400 Mill Street",
"addressLocality": "Boulder",
"addressRegion": "CO",
"postalCode": "80302",
"addressCountry": "US"
},
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer support",
"telephone": "+1-303-555-0199",
"email": "help@example.com"
},
"sameAs": [
"https://www.linkedin.com/company/northfold",
"https://www.instagram.com/northfold",
"https://www.youtube.com/@northfold"
]
}
Properties
| Property | Status | What it is |
|---|---|---|
name | Recommended | The organization's common name. |
alternateName | Recommended | Other names or acronyms you are known by. |
legalName | Recommended | The registered legal name, if different. |
url | Recommended | The organization's website URL. |
logo | Recommended | A crawlable logo image at least 112x112 pixels that looks right on a white background. |
sameAs | Recommended | URLs of your official profiles elsewhere: social accounts, Wikipedia, Wikidata. |
contactPoint | Recommended | ContactPoint entries with telephone or email and a contactType such as "customer support". |
address | Recommended | The PostalAddress of your headquarters or main office. |
description | Recommended | A short, factual description of what the organization does. |
vatID / taxID / duns / leiCode / iso6523Code | Recommended | Official identifiers that help distinguish your organization from others. |
foundingDate / numberOfEmployees | Recommended | Basic facts about the organization. |
When to use it
Every site run by a company, nonprofit, school or other group should have one Organization block, typically on the homepage. Use a more specific subtype when it fits: OnlineStore for an ecommerce business, NGO, EducationalOrganization, Corporation. A business customers visit in person should add LocalBusiness for each location and link it to the Organization.
If the site is about one individual, such as a personal brand or portfolio, use Person instead.
Give the block an @id (for example https://example.com/#organization). Other markup on the site, like an Article's publisher, can then point to that same entity instead of repeating it.
Add it in WordPress
By hand. Print the JSON-LD on the front page only, from wp_head wrapped in an is_front_page() check.
With Hydrogen SEO. Organization is configured on the Schema screen: name, logo, URL and contact details. Its sameAs list is built from the Organization sameAs URLs you enter there plus the social profiles and X account on the Social screen, merged with duplicates removed. The setup wizard's Business Profile fills empty settings when you first install. The JSON-LD renders server-side on every matching page.
One-off markup. The free schema generator in the Hydrogen SEO app at /seo/schema-generator builds Organization JSON-LD with a logo, phone and social profiles.
Common mistakes
- A logo that is too small or not crawlable. Use an image at least 112x112 pixels, served from a URL Googlebot can fetch.
- sameAs pointing to unofficial pages. List only profiles you control or that are about you, like your Wikipedia entry.
- Organization markup on every post with different values. One consistent entity, referenced by
@id, is cleaner than dozens of slightly different copies. - Conflicting names. Your name in schema, on the site and in your profiles should match.
- Two plugins printing Organization. A theme, an SEO plugin and a page builder can each add one. Keep one source. See invalid structured data.
Test it
Two passes work best for Organization: syntax and required fields in our validator, then the live URL in the Rich Results Test and validator.schema.org. The Rich Results Test reports Organization as its own item when it detects a logo or other supported properties. Search Console does not guarantee a logo or knowledge panel change; those depend on Google's own understanding of your entity.
Common questions
Where should Organization schema go?
On the homepage, or on a single page describing the organization such as About. It does not need to be repeated on every page.
Will Organization schema give me a knowledge panel?
Not by itself. It helps Google understand details like your logo and contact information, but knowledge panels depend on Google recognizing your organization as an entity from many sources.
What is the difference between Organization and LocalBusiness?
LocalBusiness is a subtype of Organization for a place customers visit or a local service. Online-only companies use Organization; physical locations add LocalBusiness.
Should I include Wikidata in sameAs?
If your organization has a Wikidata or Wikipedia entry, yes. These are strong signals for connecting your site to the right entity.