A studio ships a catalog of product photos the careful way. Every file is compressed to WebP, every hero loads fast, every alt attribute is written by hand to describe what the picture shows. Months later the Search Console numbers tell a flat story: the pages rank, but almost nothing arrives from the Images tab. A competitor selling a near-identical item shows up there instead, its thumbnail carrying a small “Licensable” tag that links out to license terms. Same kind of photo, different result. The studio did the delivery work and the labeling work. Visibility in image search turned out to be a separate job.
Two posts on this site already cover the neighbors of that job. One is about shrinking the image file itself, format choice and lazy loading and responsive delivery. The other is about writing alt text. Both are necessary, and neither is about how a photo gets found and ranked inside Google Images, or about the image feature a site can most directly earn for itself. That is the gap this piece fills.
Image search is a different surface, and it borrows the page’s relevance #
Google Images is its own results surface, not a slice of the regular blue-link page, and an image earns a place there through cues that mostly sit outside the file. Google’s Search Central documentation is direct about where the meaning comes from: “The content and metadata of the pages where an image is embedded can have a great influence on how and where the image may appear in Google’s search results.” The image inherits the page.
Google names the specific inputs it reads. Alt text is one, used “along with computer vision algorithms and the contents of the page to understand the subject matter of the image.” The surrounding page is another, since Google “extracts information about the subject matter of the image from the content of the page, including captions and image titles.” The filename gives “very light clues.” Put together, these say something practical. A brilliant photo dropped onto a thin or off-topic page has little to rank on. The same photo on a focused, well-written page about that subject carries the page’s authority into the Images tab.
Before an image can rank, it has to be findable #
Ranking is the second gate. The first is whether Google can crawl the image at all, and a few technical conditions decide that. The image needs to be placed with a standard HTML element, because a picture loaded as a CSS background is not eligible for image search. The format has to be one Google supports, and the current list is BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF. The file needs a stable, crawlable URL rather than one that only appears after a click or a script Googlebot does not run.
Quality and delivery matter here too, for a reader-facing reason as much as a crawling one. Google notes plainly that “high-quality photos appeal to users more than blurry, unclear images,” and recommends serving responsive versions through a picture element or a srcset attribute with a plain fallback src so a real image is always present. If a file is buried on a page with few internal links, Google may never discover it, and an image sitemap is the documented way to hand it the URLs it might otherwise miss. Discovery first. Ranking after.
The Licensable badge is the image feature most directly in your hands #
Most of what shapes an image result is indirect, decided by the page and the query. The Licensable badge is an exception, an enhancement a site declares for itself rather than waiting for Google to infer it, and one of the few that applies to any photo regardless of what the page sells. It places a “Licensable” label on the image in Google Images and, per Google, “provides a link to the license and more detail on how someone can use the image.” For a photographer, a stock library, or any brand whose images get lifted and reused, that badge turns a passive picture into a labeled, monetizable asset with a route back to the owner.
There are two ways to declare licensing, and Google is clear that either one on its own is enough. The first is structured data: an ImageObject on the page. Its required fields are the contentUrl plus at least one of creator, creditText, copyrightNotice, or license, but to qualify for the badge specifically Google adds a condition, “you must include the license property for your image to be eligible to be shown with the Licensable badge.” A companion field, acquireLicensePage, points to where someone can buy a license. The second method is IPTC photo metadata written into the file itself, where the “Web Statement of Rights” field is the one required for badge eligibility and a “Licensor URL” is recommended for the purchase route.
One honest limit belongs next to all of this. Google states it “does not guarantee that structured data or IPTC photo metadata will show up in search results.” The markup opens the door. It does not walk anyone through it.
Structured data or IPTC: which route to declare licensing #
The two methods reach the same badge, and they differ in where the information lives and how far it travels. That difference is the whole decision.
| Question | ImageObject structured data | IPTC photo metadata |
|---|---|---|
| Where it lives | In the page’s HTML, near the image | Inside the image file itself |
| Travels with the file? | No, it stays with the page | Yes, it moves wherever the file is used |
| Field required for the badge | The license property | The Web Statement of Rights field |
| Purchase-route field | acquireLicensePage | Licensor URL |
| Best fit | A site publishing its own images on known pages | Photos that get syndicated, resold, or reused across sites |
The choice tends to split by scale. A single business publishing its own product shots on its own pages can add ImageObject markup once per template and be done. A stock library or a wire photographer whose files scatter across client sites gets more from IPTC, because the license claim rides inside the file and survives the copy. Both is fine. IPTC also carries a Digital Source Type field that flags AI-generated or AI-edited images, which is a separate concern from licensing but lives in the same metadata block and is worth setting honestly.
A pre-publish check, and what to watch after #
Image search rewards work done before the file goes live more than fixes bolted on later. Front-load it. A short pass before publishing catches most of what matters:
- Embed the file with a standard HTML element, never as a CSS background, if it should be found in image search.
- Give it a descriptive filename and alt text, and place it on a page whose text is genuinely about the subject.
- Start from a high-resolution source and serve responsive sizes with a plain fallback so a real, crawlable file always loads.
- Pick one licensing method, structured data or IPTC, and make sure the field the badge requires is filled with a live URL.
- List files in an image sitemap when they sit on thin or poorly linked pages Google may not reach on its own.
After publishing, the measurement lives in one place. The Search Console Performance report can be filtered by search type to Image, which separates image traffic from web traffic and shows whether those files draw clicks at all. Confirm eligibility with the Rich Results Test, then give Google time to recrawl before reading anything into an absent badge. The badge is an eligibility ticket, not a guarantee, and image search is one of the few places where a picture on an ordinary page can quietly out-earn a better one that no crawler ever found.