How Do I Add Licensing Information for My Product Photographs in Google Images?

Establish the rights record before writing metadata

Identify the exact photograph, its creator, the authorized rights holder and the applicable usage or licensing destination. Do not infer ownership merely because the image appears in the merchant's product catalog.

Google distinguishes a license-information page from a page where someone can learn how to obtain a license. The first explains the terms governing use. The second may provide an acquisition process or contact information. These destinations can differ.

Keep the rights record tied to the actual photograph, not just the product SKU. A hero image, detail photograph and supplier mockup may have different creators and permissions even when they depict the same item.

This procedure concerns metadata representation, not a legal determination about copyright or permission. If the merchant cannot establish an authorized licensing statement, hold the licensing markup rather than inventing one.

Choose structured data or embedded IPTC

Google supports two routes for image licensing information. ImageObject structured data associates image metadata with a page. Embedded IPTC metadata travels inside the image file when preserved.

For structured data, Google's documentation identifies contentUrl as the preferred precise image reference, with url supported as an alternative. The documented property set includes creator, creditText, copyrightNotice, license and acquireLicensePage.

For eligibility for Google's Licensable badge through structured data, the license property is required. The acquireLicensePage property is recommended when relevant.

For IPTC, Google documents fields including Web Statement of Rights and a Licensor URL attached to a Licensor object. The Web Statement of Rights field is required for the corresponding licensing-badge eligibility route.

If both metadata methods are present and conflict, Google states that it uses structured data. Therefore, publishing contradictory rights information is not a useful redundancy strategy.

Hypothetical case: a merchant-owned ceramic mug photograph

Hypothetical illustration; no rights agreement, metadata file or Google result was inspected. A fictional ceramics merchant commissions a product photograph. Assume the merchant has confirmed the applicable rights and an authorized public licensing-information page.

The public image URL is represented in the worksheet by a fictional example-domain address. The merchant proposes ImageObject metadata identifying that image, the approved creator credit and the appropriate license page.

A second proposed record points to the product's purchase page as acquireLicensePage even though that page only sells mugs and says nothing about licensing photographs. Under the stipulated facts, that destination does not explain how to license the image and should not be used for that purpose.

The worksheet distinguishes a verified rights destination from an unrelated commerce destination. It does not establish that the fictional merchant actually owns the image or that Google will display a badge.

Verify the published image and metadata together

Have the site maintainer implement the selected metadata route in the publishing system. If using structured data, inspect the actual public page and verify that the image URL identifies the correct photograph. Google says structured data must be supplied for each relevant page instance where the image appears.

If using IPTC, inspect the final image file and any CDN derivative to determine whether the intended fields survived processing. Do not assume that metadata embedded in a local original remains present after conversion.

Use Google's Rich Results Test and relevant public-page checks for implementation evidence, while recognizing that valid markup does not guarantee the Licensable badge will appear.

Keep alt text and product structured data accurate for their own purposes. Neither is a substitute for image-specific licensing metadata. Likewise, Content Credentials can describe provenance but are not interchangeable with the license fields documented here.

The existing public-export metadata guide governs removing inappropriate private fields and preserving required information. This article defines the specific Google Images licensing metadata route.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Google Search Central — Image metadata in Google Images: Primary documentation for ImageObject licensing fields, IPTC alternatives, eligibility requirements, metadata precedence and display limitations.
• Google Search Central — Image SEO best practices: Documents discoverable public image elements and the role of page context and image metadata.