schema.org/BrandNo rich result
Brand schema
A brand, as distinct from the legal organisation that owns it and sells under it.
Where to use it
Nested inside Product.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
brand.json
{
"@context": "https://schema.org",
"@type": "Brand",
"name": "Acme Reference",
"logo": "https://www.seoforsolos.com/icon.svg",
"url": "https://www.seoforsolos.com/example"
}Properties
| Property | Status |
|---|---|
name | Required |
logo | Recommended |
url | Recommended |
The three mistakes this type attracts
- 01Duplicating Organization as Brand rather than referencing it.
- 02A logo URL that 404s.
- 03Using it where the brand and the organisation are the same and already declared.
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 Brand schema type for?
A brand, as distinct from the legal organisation that owns it and sells under it. Use it on: nested inside Product.
Which Brand properties are required?
Brand requires one property: name. It also recommends 2: logo, url.
Does Brand produce a rich result?
Brand 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 Brand mistake?
The most common Brand mistake is: Duplicating Organization as Brand rather than referencing it.