ImageObject Schema: Complete Reference

By Amit Patel

ImageObject schema describes an image with metadata — its URL, creator, copyright, credit, and licensing terms — which Google can use to show a licensable badge in Google Images and to attribute the image correctly. It is a niche but genuine rich result: for photographers, stock providers, and publishers of original imagery, ImageObject with license fields can drive attribution and licensing inquiries. This reference covers the useful properties and where the type actually pays off.

What ImageObject Does

It attaches structured metadata to an image so search engines understand its source, creator, and usage terms — and, with license fields, can mark it as licensable in Google Images.

ImageObject also appears as a value inside other types (as the image of an Article, Product, or Organization logo), but as a standalone rich-result play it is about image licensing and attribution. It is one of the safe, additive types you can implement for original imagery.

The Licensable Badge

Adding license (a URL to your license terms) and acquireLicensePage (where to get a license) makes an image eligible for the “Licensable” badge in Google Images, linking searchers to your licensing page.

This is the main visible benefit. It only helps if you actually license images — for a typical blog using its own photos without a licensing program, the badge is irrelevant. When you do license, these two properties are what unlock the feature.

Key Properties

Useful properties include contentUrl, creator, creditText, copyrightNotice, license, and acquireLicensePage; these feed both attribution and the licensable badge.

creator (often a Person or Organization) and creditText control attribution display, while the two license URLs drive the badge. Keep them accurate and pointing at real pages. Validate with the Rich Results Test.

When It Is Worth Adding

Add ImageObject with license fields if you sell or license images or want formal attribution; skip the license fields if you simply use your own images decoratively.

For most content sites, images are already referenced inside Article or Product markup, and standalone ImageObject licensing is unnecessary. Match the effort to whether image licensing is part of your business, the same status-and-fit judgment the whole cluster applies.

Example Markup

An ImageObject with license fields (shown as code):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ImageObject",
  "contentUrl": "https://example.com/photo.jpg",
  "creator": { "@type": "Person", "name": "A. Photographer" },
  "creditText": "A. Photographer",
  "license": "https://example.com/license",
  "acquireLicensePage": "https://example.com/buy-license"
}
</script>

See JSON-LD vs Microdata for the format.

Frequently Asked Questions

The Bottom Line

ImageObject is a specialist type: for image licensors and publishers of original photography, its license fields earn a badge and clean attribution; for everyone else, images are already covered inside other markup. Add it where licensing matters, keep the URLs real, and skip it where it does not — the fit-to-purpose approach the schema cluster takes to every type.