Organization schema
Organization schema describes your company in JSON-LD: its name, URL, logo, contact details, address, identifiers and official profiles. Google says adding it to your home page can help it understand your organization’s administrative details and disambiguate it in search results. There are no required properties; add the ones that apply.
What does Google use Organization markup for?
Google says Organization structured data on your home page “can help Google better understand your organization’s administrative details and disambiguate your organization in search results.” Some properties are used behind the scenes to tell organizations apart (such as iso6523Code and naics); others can influence visual elements such as the logo in results and the knowledge panel.[1] Officially documented
Which properties should you include?
Google lists no required properties and recommends focusing on name or alternateName, real-world presence (address, telephone) and online presence (url, logo).[1] Schema.org defines many more Organization properties.[2]
| Property | Notes |
|---|---|
name, alternateName, legalName | Consistent with how you are known offline |
url, logo | Your entity home and a crawlable logo image |
address, telephone, email | Match your contact page and Business Profile |
sameAs | Official profiles and databases (guide to sameAs) |
foundingDate, founder | Link founders by @id to Person nodes |
iso6523Code, naics, vatID, leiCode | Identifiers that help disambiguation[1] |
What does a good example look like?
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#organization",
"name": "Example Co",
"url": "https://www.example.com/",
"logo": "https://www.example.com/logo.png",
"foundingDate": "2009",
"founder": {"@id": "https://www.example.com/about/jane-doe#person"},
"address": {"@type": "PostalAddress", "addressLocality": "San Diego",
"addressRegion": "CA", "addressCountry": "US"},
"sameAs": ["https://www.linkedin.com/company/example-co",
"https://www.wikidata.org/wiki/Q00000000"]
}
Generate your own with the schema generator.
What mistakes should you avoid?
- Different names or addresses in markup, site text and Business Profile. Practitioner practice
- A new
@idon every page instead of one stable identifier (@id guide). - sameAs links to profiles you do not control or that describe someone else.
- Using Organization for a local storefront when a LocalBusiness subtype fits better.
Google’s Organization properties in detail
Google’s Organization documentation sets out where to place the markup and what each property is for.[1]
- Placement. Google recommends the home page, or a single page that describes the organization such as an about page; “you don’t need to include it on every page of your site”.
- Type. Use “the most specific schema.org subtype of Organization” that fits; for a local business, use the most specific
LocalBusinesssubtype and follow the local business fields too (see LocalBusiness schema). - Name. Use the same
nameandalternateNamethat you use for your site name (see below). - Legal and registry identifiers.
legalNameis the registered name “if applicable and different from the name property”. Google encouragesiso6523Codein the formICD:identifier; common ICD prefixes it lists are0060(Dun & Bradstreet DUNS),0088(GS1 Global Location Number) and0199(Legal Entity Identifier). For LEI and DUNS numbers it encouragesiso6523Codewith the0199:and0060:prefixes instead ofleiCodeandduns. It also listsnaics,taxIDandnumberOfEmployees. - Logo. At least 112×112 px, crawlable and indexable, in a format Google Images supports, and legible on a plain white background.
- Scope. There are no required properties. Google suggests focusing on name, real-world presence (address, telephone) and online presence (url, logo).
Google adds that some of these properties (it names iso6523 and naics) are used “behind the scenes” to disambiguate organizations, while others can influence visual elements such as the logo shown in results and in the knowledge panel.[1] How heavily either is weighted is not published.
Keeping the organization name consistent with the site name
Google’s site name feature shows “the name of the site the page comes from”, distinct from the page title.[3] You indicate a preference with WebSite structured data on the home page; Google also considers og:site_name, the title, headings and other home page text, and references to the site elsewhere.[3] Its guidance:
- Choose a concise, commonly recognised name, and avoid generic names.
- Use the name consistently across the home page.
- Provide an
alternateName(for example an acronym) so Google has another option if the preferred name cannot be used. - Only one site name per site is supported, and the markup must be on the domain-level or subdomain-level home page, which Google must be able to crawl.
Because the Organization guidance says to reuse the same name and alternate name, the two should match (Google’s guidance, applied here).[1][3]
Frequently asked questions
Where should Organization schema go?
Google recommends the home page. Other pages can reference the same node by its @id.
Are there required properties?
No. Google recommends adding the properties that apply, focusing on name, address or telephone, url and logo.
Should I use Organization or LocalBusiness?
Use a LocalBusiness subtype for a business customers visit or that serves a defined area; use Organization for a company without a local presence.
See also
References
Pages accessed September 29, 2026 unless a date is given. See all sources and our editorial policy.
- ^ "Organization structured data". Google Search Central.
- ^ "Organization type". Schema.org.
- ^ "Provide a site name to Google Search". Google Search Central. Last updated December 10, 2025. Accessed October 29, 2026.