Search & Discovery·Explain
Licensable badge vs. IPTC
Google Image Search can show a "Licensable" badge on an image result, with a link to licensing details. There are two different ways an image qualifies for it, and this platform deliberately does one of them and not the other. Most "image SEO" checklists don't distinguish the two at all, which is how photographers end up assuming alt text and file names are the whole story.
Two paths
Same job, different place the bytes live
JSON-LD on the page
An ImageObject in the HTML describing license, credit, copyright, and creator. Survives image transforms. Only found if Google crawls that page.
IPTC in the file
Web Statement of Rights and related fields baked into the image bytes. Travels with a download. Breaks if a CDN or resize pipeline strips it.
What we emit
Rights on every public photo page as ImageObject JSON-LD. Read from the page, not extracted from the file.
What we don't
No IPTC bytes written into image derivatives. Tools that only inspect a downloaded file will not find a rights field here.
Where the badge came from
Google's requirements for the Licensable badge have shifted more than once since it launched in 2020. Confirm current rules in Search Central or Search Console's licensable-image report before treating anything below as a permanent spec.
Google introduced the badge keyed to IPTC metadata embedded directly in the image file, specifically the IPTC Web Statement of Rights (Copyright Info URL) field, plus related credit and copyright fields baked into the file's own bytes. Google later added a second, alternative path: structured data on the page (a schema.org ImageObject, or equivalent) carrying the same kind of licensing information. Either path, satisfied on its own, can make an image eligible.
| Path | Lives where | Survives what |
|---|---|---|
| IPTC metadata | Embedded in the image file itself | Travels with the file if it's downloaded or copied; breaks if a CDN or resize pipeline strips or fails to preserve it |
| JSON-LD structured data | In the page's HTML, describing the image | Travels with the page; unaffected by image transforms, but only found if Google crawls that page |
What this platform does
Rights (license, credit, copyright, creator, and EXIF when present) are written into the page's ImageObject JSON-LD on every public photo page. That's the structured-data path. It's read from the page, not extracted from the file.
What it doesn't do
No IPTC bytes are written into image derivatives. The practical consequence: any tool that reads licensing by inspecting a downloaded file, rather than crawling the page around it, won't find it here. That includes some stock-licensing crawlers, some reverse-image and ORM tools, and anyone who saves your image locally and checks its file properties expecting a rights field.
Why that's a tradeoff, not an oversight
IPTC-in-file has a real structural weakness for a platform serving images through a CDN with on-the-fly transforms: metadata embedded in a master file doesn't reliably survive every resize, format conversion, or derivative generation step, and re-verifying it on every transformed variant is a much bigger commitment than it sounds. JSON-LD sidesteps that entirely. It describes the page, and the page is the thing Google's crawler is actually looking at when it decides whether to show the badge. The cost is the one above: anything reading the file directly, off-platform, sees nothing.
The practical takeaway
If your goal is Google Images eligibility for the Licensable badge, the structured-data path this platform uses is a legitimate, Google-documented route, not a lesser substitute for IPTC. If your goal is specifically to have licensing survive inside a downloaded copy of the file (for a workflow, an archive handoff, or a tool that only reads embedded metadata), that's not something to assume is covered.
The count of licensable images, if you want one, lives in Search Console's own report. See What Search Console is for.
Rights on the page, not in the derivative
Google can read ImageObject. A downloaded file won't carry IPTC we never wrote. Plan the workflow, not the myth.
Also in Guides: The structured data this platform emits · What Search Console is for · AI SEO myths for creatives