The Licensable badge tells a searcher that a picture has an owner and a way to license it. Earning it takes one URL in the right place. Keeping it takes a little care about how your site serves images.
To be eligible for the Licensable badge in Google Images, an image needs one thing: a URL, readable by Google, that points to the licence governing its use. You can supply it in structured data on the page or in IPTC metadata inside the file. Everything else in this guide is about doing that reliably across a whole site.
This article is general information, not legal advice. Checked on 18 November 2026 against Google Search Central's documentation, which was last updated on 10 December 2025. Google can change its requirements, so read the current page before a large implementation.
What is the Licensable badge?
Google introduced the badge on 31 August 2020, together with a usage rights filter in Google Images. When a result qualifies, a small "Licensable" label appears on its thumbnail. Opening the image shows a link to the licence details and, if you supplied one, a link to where a licence can be obtained. A searcher can also filter results to show only images with licensing information.
For photographers, agencies and archives the value is plain. It marks a picture as owned and available on terms, at the moment someone is deciding whether to use it, and it sends that person to your site instead of leaving them to guess.
What does Google require?
There are two routes. Google's documentation says you need only one.
| Structured data | IPTC photo metadata | |
|---|---|---|
| Where it lives | In the HTML of each page showing the image | Inside the image file |
| How often you add it | On every page where the image appears | Once per file |
| Required for the badge | license | Web Statement of Rights |
| Recommended | acquireLicensePage | Licensor URL |
| Also read by Google | creator, creditText, copyrightNotice | Creator, Credit Line, Copyright Notice, Digital Source Type |
| If the two conflict | Structured data wins |
For structured data, an ImageObject must include contentUrl, the address of the image file, and at least one of creator, creditText, copyrightNotice or license. To be eligible for the badge specifically, license must be present.
Google's general conditions apply as well. The page has to be reachable without a login, and neither the page nor the image may be blocked by robots.txt or a robots meta tag. The feature is available on mobile and desktop wherever Google Search operates. And Google states that it does not guarantee the metadata will appear.
How do I add image licence structured data?
The usual form is JSON-LD in the page. A minimal, complete example:
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "ImageObject",
"contentUrl": "https://example.com/images/bottle-1200.jpg",
"license": "https://example.com/licence-terms/",
"acquireLicensePage": "https://example.com/request-a-licence/",
"creditText": "Example Picture Library",
"creator": {
"@type": "Person",
"name": "Jane Example"
},
"copyrightNotice": "© Jane Example"
}
</script>
Points that catch people out:
- contentUrl must match the file actually displayed. If your site serves several sizes, describe the one in the page.
- license is a page of terms, not a statement. It should resolve to a real page explaining how the image may be used.
- acquireLicensePage is where the transaction or enquiry happens. A contact form is acceptable.
- Repeat it everywhere. A picture that appears on a gallery page, a category page and an article needs the markup on all three.
- A page with many images needs an entry for each.
Test the result with Google's Rich Results Test, and use URL Inspection in Search Console to confirm that Google can fetch both the page and the image.
How do I use IPTC metadata instead?
Embed two fields in the file:
- Web Statement of Rights, which holds the licence URL. This is the field Google requires for the badge. In XMP it is xmpRights:WebStatement.
- Licensor URL, which says where to obtain a licence. Google notes that it belongs inside a Licensor structure, not directly on the image.
Add Creator, Credit Line and Copyright Notice at the same time, since Google reads those for the credit shown beside the image.
The free copyright metadata tool writes the Web Statement of Rights, along with creator, copyright notice, credit line and usage terms, into a JPEG's XMP in the browser, without uploading or recompressing the file. Check what a file contains with the metadata viewer. How these fields relate to each other is set out in IPTC, XMP and EXIF compared.
The embedded route has one clear advantage: the information goes with the file, including onto other people's sites, if they leave it in place. It has one clear risk, which is that something between you and Google removes it.
Why is the badge not appearing?
Work through these in order.
- Is the image indexed? New images can take time. Search for the page with the site: operator in Google Images.
- Is anything blocked? A robots.txt rule aimed at AI crawlers can catch Googlebot-Image if written carelessly. Blocking the Google-Extended token does not affect Search; blocking Googlebot-Image removes the picture from Google Images altogether. The distinction is explained in the guide to robots.txt for AI crawlers.
- Does the licence URL work? It must load without a login.
- Is the markup on every page? One unmarked instance will not carry the badge.
- Has the metadata survived? Content management systems, image optimisers and content delivery networks often strip metadata when they resize. Download the image as your site serves it and inspect that copy. The wider problem is described in what happens to metadata when you upload a photo.
- Do the two methods disagree? If structured data and IPTC give different URLs, Google uses the structured data.
- Is it simply not shown? Eligibility is not a guarantee.
What the badge does not do
It is worth being exact about this, because the name invites over-reading.
- It is not protection. The image can still be saved, copied and misused.
- It is not a licence. It points to your terms; it grants nothing.
- It is not an AI opt-out. A licence URL says nothing to a training crawler about text and data mining. That preference is expressed by other signals, such as the IPTC Data Mining property, which the AI training opt-out metadata tool can write, and by robots.txt.
- It is not a ranking promise. Google's documentation describes the badge as a display feature and makes no claim about position in results.
- It does not settle any legal question. What is decided is only what Google's documentation says it will read. Whether signals of this kind carry legal weight as rights reservations is a separate matter, still pending in several jurisdictions, and outside what the badge is for.
A checklist for a picture library
- Publish a licence terms page and a page for licence requests.
- Add ImageObject markup with contentUrl, license and acquireLicensePage to every image on every page.
- Add creator, creditText and copyrightNotice.
- Embed Web Statement of Rights, Licensor URL, Creator, Credit Line and Copyright Notice in the files.
- Make sure both methods give the same URLs.
- Confirm that your image pipeline keeps metadata, or rely on the structured data.
- Keep Googlebot and Googlebot-Image allowed in robots.txt.
- Test a sample of pages, then recheck after any site redesign.
How Archive.London marks its images
The published photographs on Archive.London are described in ImageObject structured data on each collection page, with the creator, credit text and copyright notice, a license URL pointing to the rights and stewardship statement and an acquireLicensePage pointing to professional access. Whether Google displays a badge for any given image is Google's decision.
Only a small, watermarked selection of the Robert Harper Photograph Library is online, in collections such as watches and jewellery; more than half of the archive is still on film and has yet to be scanned. The archive is owned by 825 Ventures Ltd, the owner and rights holder. Picture researchers, publishers and agencies who find an image through search and want to use it can make a request through the picture agencies page.
Frequently asked questions
How do I get the Licensable badge on Google Images?
Give Google a URL for the licence that governs each image. Either add ImageObject structured data to the page with a license property, or embed the IPTC Web Statement of Rights field in the image file. Adding a second URL showing where to obtain a licence is recommended. The page has to be publicly accessible and crawlable.
Do I need both structured data and IPTC metadata for the Licensable badge?
No. Google says one method is enough. Structured data must be added on every page where the image appears. IPTC metadata is embedded once and travels with the file. Using both is sensible because some systems strip embedded metadata, but if the two disagree Google uses the structured data.
What is the difference between license and acquireLicensePage?
The license property is a URL for a page that describes the terms under which the image can be used. The acquireLicensePage property is a URL for a page where someone can obtain a licence, such as an enquiry form or a checkout. They can be different pages on your site. Only license is needed for badge eligibility.
Why is my Licensable badge not showing?
Common causes are that the image is not yet indexed, the page or image is blocked by robots.txt, the licence URL is missing or broken, the structured data is on some pages but not others, or a content delivery network has stripped the embedded metadata. Google also states that it does not guarantee the information will be shown.
Does the Licensable badge protect my images from being copied or used for AI training?
No. The badge tells people that licensing information is available and links to it. It does not prevent downloading, and it is not a rights reservation for text and data mining. Preferences about AI training are expressed separately, for example with robots.txt rules and the IPTC Data Mining property.
Sources
- Google Search Central: Image metadata in Google Images (last updated 10 December 2025)
- Google Search Central blog: Make the licensing information for your images visible on Google Images (August 2020)
- PetaPixel: Google Images launches 'Licensable' badge and search filter (31 August 2020)
- Google Search Central: Google's common crawlers
- IPTC Photo Metadata Standard specification
- IPTC: Social media sites photo metadata test results 2019
Published by Archive.London. Corrections are welcome under our editorial policy.

