ImageObject schema
An image, with its dimensions and caption.
Where to use it
Nested wherever an image is referenced by a node.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "ImageObject",
"url": "https://www.seoforsolos.com/example",
"width": 1200,
"height": 630,
"caption": "Acme Reference logo",
"contentUrl": "https://www.seoforsolos.com/opengraph-image"
}Generate a ImageObject node with your own values in the schema generator, and lint what your page actually ships with the schema validator.
Properties
| Property | Status |
|---|---|
url | Required |
width | Recommended |
height | Recommended |
caption | Recommended |
contentUrl | Recommended |
The three mistakes this type attracts
- 01Omitting width and height, which some consumers require.
- 02Pointing at an image behind authentication.
- 03Using a URL under 1200px wide where a rich result requires more.
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
- Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.
Questions
What is the ImageObject schema type for?
An image, with its dimensions and caption. Use it on: nested wherever an image is referenced by a node.
Which ImageObject properties are required?
ImageObject requires one property: url. It also recommends 4: width, height, caption, contentUrl.
Does ImageObject produce a rich result?
ImageObject 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 ImageObject mistake?
The most common ImageObject mistake is: Omitting width and height, which some consumers require.