Google Licensable Image Badge: XMP and Schema.org Setup

In Google Images search results, images that carry valid licensing metadata can receive an interactive "Licensable" badge. Clicking this badge opens an informational panel displaying licensing terms, creator attribution, and an actionable link for users to acquire a license or purchase the asset.

Implementing this badge requires adhering strictly to Google's technical specifications across embedded metadata and structured markup.

1. The Two Channels for Licensing Information

Google supports two distinct methods for providing licensing metadata:

1. Embedded IPTC/XMP Metadata: Injected directly into the binary file container (JPEG or WebP).
2. Structured Data Markup: Declared on the hosting webpage using Schema.org ImageObject in JSON-LD format.

While Google's crawler recognizes either approach, implementing both channels is the professional standard. Structured data on the host page assists Googlebot during initial crawling, while embedded XMP ensures rights attribution survives when files are syndicated, saved, or republished elsewhere.

2. Technical Specification for Embedded XMP

Embedded metadata resides in an XMP packet inside the image container. To qualify for the Licensable badge, the following properties must be present:

• xmpRights:WebStatement: A secure, absolute URL pointing to a publicly accessible web page detailing the license terms governing the image (e.g., a Creative Commons deed or commercial usage license).
• plus:LicensorURL: A secure, absolute URL pointing to a page where a visitor can purchase, request, or acquire a license to use the image.
• dc:creator & dc:rights: Standard Dublin Core fields recording the creator's name and copyright notice.

URL Validation Standards

• Must use the https:// protocol.
• Must not contain embedded credentials (such as user:password@host).
• Must resolve to a valid, live web page that returns an HTTP 200 OK status to automated crawlers.

3. Schema.org JSON-LD Structured Data

When publishing the asset in HTML, pair the image with a corresponding Schema.org ImageObject block in the document <head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ImageObject",
  "contentUrl": "https://example.com/images/high-resolution-photograph.webp",
  "license": "https://example.com/licensing/editorial-terms/",
  "acquireLicensePage": "https://example.com/licensing/purchase/",
  "creator": {
    "@type": "Person",
    "name": "Alex Morgan"
  },
  "creditText": "Alex Morgan Photography",
  "copyrightNotice": "© 2026 Alex Morgan. All rights reserved."
}
</script>

The license property corresponds to xmpRights:WebStatement, while acquireLicensePage corresponds to plus:LicensorURL.

4. Engineering Realities & Anti-Hallucination Guardrails

To prevent misunderstandings about what licensing metadata accomplishes:

• No Ranking Guarantee: Embedding licensing metadata does NOT guarantee that Google Images will display the badge. The asset must be crawled and indexed, pass safe-search filters, and the host domain must be recognized as authoritative and in good standing.
• Not Cryptographic DRM: XMP metadata is plaintext metadata inside the file. It does not encrypt, water-mark, or mechanically restrict downloading or screen captures.
• URL Integrity is Mandatory: Submitting placeholder links or broken URLs disqualifies the asset from the badge. Google's automated systems test the target URLs.

5. Automated Licensing in Image Studio

Image Studio streamlines this dual-layer setup directly in your browser:

1. In the studio workstation, provide your License Terms URL (licenseUrl) and Acquire License URL (acquireLicenseUrl).
2. Image Studio validates that both entries use secure HTTPS schemes and well-formed syntax.
3. Upon export, the client-side engine embeds compliant XMP blocks into your WebP or JPEG binary, and generates corresponding Schema.org ImageObject JSON-LD code ready for copy-pasting into your page.