ImageObject Schema
ImageObject schema describes an image to machines: dimensions, caption, licence, and creator. Learn when it matters and how it differs from alt text.
TL;DR
ImageObject schema is the structured data type that describes an image as a thing in its own right: its URL, dimensions, caption, creator and licence terms. Most sites encounter it as a nested property inside Article or Product markup rather than as a standalone block. It answers a narrower question than most schema types: not what the page is about, but what this specific image is and who owns it.
Why ImageObject schema matters
Images carry meaning that HTML alone does not express, and licensing information in particular has no other machine-readable home.
- Rich result eligibility: Several result formats require an image with declared dimensions, which ImageObject supplies.
- Licence clarity: Explicit licence and acquireLicensePage properties let engines show licensable badges and tell users how to obtain rights.
- Attribution: Naming a creator keeps credit attached to the image when it travels.
- Selection quality: Dimensions and caption help engines choose the right image rather than the first one they find.
How to implement ImageObject schema
Use it nested first
The image property inside Article, Product or Recipe markup is where most value sits. Standalone blocks are for image-centric pages.
Give an absolute URL
Relative paths fail. The contentUrl must be a full, crawlable address.
Declare width and height
Some rich results have minimum size requirements, and stating dimensions avoids engines having to fetch the file to find out.
Add a caption
A short description of what the image shows, distinct from alt text and aimed at machines rather than screen readers.
Include licence properties where relevant
license and acquireLicensePage matter for original photography and anything you want credited or licensed.
Name the creator
A Person or Organization, which supports attribution when the image is reused.
ImageObject schema vs. alt text
ImageObject schema: Machine-readable metadata about the image file: size, licence, creator, caption. Aimed at engines deciding how to use the image.
Alt text: A text alternative in the HTML for people who cannot see the image, read aloud by screen readers and used by engines as a description of content.
They serve different audiences and neither substitutes for the other. Alt text is an accessibility requirement with SEO benefits; ImageObject is metadata with licensing and eligibility benefits.
Image markup is a small part of a larger question: whether engines can fetch, parse and cite your pages at all. Findrix runs a 31-point technical check covering structured data and crawler access, then tracks citations across seven AI engines weekly. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
ImageObject properties worth setting
- contentUrl: The absolute URL of the image file.
- width and height: Pixel dimensions, needed for some result formats.
- caption: A brief description of the image content.
- creator: The photographer, illustrator or organisation responsible.
- license: A URL pointing at the licence terms.
- acquireLicensePage: Where someone can obtain rights to use it.
Where this sits on the priority list
Low, for most sites. ImageObject is worth implementing properly if you publish original photography, licence images commercially, or run an image-heavy publication where visual results drive real traffic.
For a typical B2B site, the nested image property inside Article and Product markup is sufficient, and the standalone type adds effort without a matching return.
The image work that pays off broadly is unglamorous: descriptive filenames, genuine alt text, compressed files, and images that actually illustrate the claim beside them.
Frequently asked questions
Do I need ImageObject schema for every image?
No. Use it for the primary image in Article or Product markup and for images you licence or want credited. Marking up every decorative image adds weight to your markup with no corresponding benefit.
Does ImageObject schema replace alt text?
No. Alt text is an accessibility requirement that screen readers depend on, and it remains a description engines read. ImageObject is metadata about the file. Both belong on an image that matters.
Can ImageObject schema help images appear in AI answers?
It helps engines understand what an image is and whether it can be used, which matters for licensing and selection. Whether an image appears in a generated answer depends far more on the surrounding content answering the question well.