Organization schema
The publishing entity behind a site. The anchor every other node references by @id.
Where to use it
Every page, once, in the sitewide graph.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.seoforsolos.com/#organization",
"name": "Acme Reference",
"url": "https://www.seoforsolos.com/example",
"logo": "https://www.seoforsolos.com/icon.svg",
"sameAs": [
"https://www.seoforsolos.com"
],
"description": "A one sentence description that restates its own subject.",
"email": "hello@example.com",
"foundingDate": "2026"
}Properties
| Property | Status |
|---|---|
name | Required |
url | Required |
logo | Recommended |
sameAs | Recommended |
description | Recommended |
email | Recommended |
foundingDate | Recommended |
The three mistakes this type attracts
- 01Emitting a separate Organization node per page with no @id, so a crawler sees 2,000 organisations rather than one.
- 02Listing social profiles in sameAs that do not exist or do not link back.
- 03Using Organization where LocalBusiness is the correct, more specific type.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
Questions
What is the Organization schema type for?
The publishing entity behind a site. The anchor every other node references by @id. Use it on: every page, once, in the sitewide graph.
Which Organization properties are required?
Organization requires 2 properties: name, url. It also recommends 5: logo, sameAs, description, email, foundingDate.
Does Organization produce a rich result?
Organization does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common Organization mistake?
The most common Organization mistake is: Emitting a separate Organization node per page with no @id, so a crawler sees 2,000 organisations rather than one.