SwiftSchemaGenerate

Free Image License Schema Generator

Fill in the facts visible on your page, copy the Image License JSON-LD, and validate it before you publish. The guide, examples, and FAQs are below the tool. Generate this schema with AI

Type to filter 121 supported schema types.

Schema workflow

Use only facts a visitor can verify on the page, then validate the JSON-LD before publishing.

Required

  • Visible Image License content
  • Canonical page URL
  • Clear page owner/publisher
  • Fields that match the visible page

Recommended

  • A representative image when the schema supports it
  • SameAs or related links when visible
  • Validation before publishing

Avoid

  • Adding properties that are not visible
  • Copying example URLs into production
  • Skipping Google and Schema.org validation
Next step

Validate, repair, and publish clean structured data.

Check the generated JSON-LD against the visible page, then run both SwiftSchema and external validators before publishing.

Validate your Image License markupTest Image License rich results

Image License Metadata — Make rights clear for Google Images

Generate ImageObject JSON-LD with license, acquire page, credit, and creator so your images earn the licensable badge and proper attribution.

Generate Image License JSON-LD

Why image license data gets ignored

  • License URLs point to 404s or generic home pages.
  • CDN links block crawlers with signed or expiring URLs.
  • Credit text differs from on-page captions, lowering trust.
  • Acquire/license pages aren’t linked, so users can’t request rights.

How SwiftSchema helps

The generator gathers the ImageObject fields Google reads for licensable images: contentUrl, license, acquireLicensePage, creditText, copyrightNotice, and creator.

It keeps credit and caption fields aligned with on-page copy to avoid mismatches.

You get copy-ready JSON-LD you can drop on asset or article pages without hunting for field names.

How it works

  1. 01

    Add the image file URL (contentUrl). Google reads url as the image URL too, so never put the page URL there.

  2. 02

    Provide the license URL and the acquireLicensePage (can be the same if terms and request are combined).

  3. 03

    Add creditText, creator, and publish date to match visible attribution.

  4. 04

    Generate JSON-LD and embed it once on the page; keep it updated if URLs or rights change.

  5. 05

    Validate in Rich Results Test; ensure the image file is crawlable (no 403/expired URLs).

Ready to build the markup?

Add license, credit, and creator in minutes.

Generate Image License JSON-LD

Image License Metadata: Make usage rights unambiguous

Google uses ImageObject metadata to show the licensable badge and clarify how images can be used. This markup pairs your asset URLs with the license, acquisition page, and credit so creators get proper attribution and users know how to obtain rights.

Required properties

  • contentUrl — Direct file URL (WebP/JPG/PNG). Crawlable, no blocked headers.
  • license — URL to the license terms (CC, custom license page, or marketplace license).
  • Google needs contentUrl plus at least one of creator, creditText, copyrightNotice, or license. For the Licensable badge, license is the one you need.

High-impact properties

  • acquireLicensePage — The page to request or purchase rights (often a licensing or contact form).
  • creditText — Visible attribution string users see near the image.
  • caption — On-page caption describing the image; keep it consistent.
  • datePublished — When the image was first published.

Implementation checklist

  1. Confirm your file URLs are crawlable (no 403/robots blocking).
  2. Put the image file URL in contentUrl, not the page URL in url.
  3. Add license and acquireLicensePage (can be the same if terms and request form are on one page).
  4. Provide creator and credit strings that match on-page attribution.
  5. Generate JSON-LD with the form below and embed it once per image or per page.
  6. Validate in Rich Results Test and spot-check in live HTML to avoid duplicate or conflicting ImageObject blocks.

Common pitfalls

  • Pointing license to a 404 or generic home page.
  • Using CDN links that block crawlers (signed URLs that expire).
  • Missing or mismatched creditText vs. visible caption.
  • Marking up stock images where you do not own licensing rights.

Required properties

  • contentUrl
  • license (needed for the Licensable badge)

Recommended properties

  • acquireLicensePage
  • creator
  • creditText
  • copyrightNotice
Licensed product image
Validate
{
  "@context": "https://schema.org",
  "@type": "ImageObject",
  "contentUrl": "https://example.com/images/product-1234.webp",
  "license": "https://example.com/licensing/standard-commercial",
  "acquireLicensePage": "https://example.com/licensing/request?asset=product-1234",
  "creditText": "Photo: Jane Doe / Example Studio",
  "caption": "Front view of the Daypack 24L in Charcoal",
  "creator": {
    "@type": "Organization",
    "name": "Example Studio",
    "url": "https://examplestudio.com"
  },
  "datePublished": "2024-10-01"
}

FAQs

Do I need both license and acquireLicensePage?Show

license is what makes an image eligible for the Licensable badge. Google recommends acquireLicensePage as well: a page that explains how to license the image. If your terms and your request form are on one page, use the same URL.

What counts as creditText?Show

Use the visible attribution string you expect users to see (e.g., “Photo: Jane Doe / Example Studio”). Keep it consistent with on-page captions.

Does caption need to match on-page text?Show

Yes. Keep captions consistent with what’s rendered near the image. Mismatches can reduce trust or lead to ignored markup.

Related types

Image Object

Open schema

Web Page

Open schema

Article

Open schema
Browse all schema types

References