Blog

The Metadata Tag That Gets Your Images Credited in Google Images

Name: The $20 Dollar Agency: How a $20/month AI Plan Replaced What Agencies Charged $1,000 For
Availability: InStock
Author: J.A. Watte

May 13, 2026 · 7 min read

Every image on your website has a hidden layer of data that most site owners never touch. IPTC (International Press Telecommunications Council) and XMP (Extensible Metadata Platform) fields are embedded directly in image files — invisible to users but readable by Google Images, AI models, stock platforms, and any system that processes images.

When someone finds your image in Google Images, the metadata determines whether your name appears as the creator, whether your site URL appears as the source, and whether anyone can trace the image back to you. If these fields are empty — and on most websites, they are — your images are anonymous. Anyone can use them without attribution, and Google has no structured signal for crediting you.

After embedding IPTC/XMP metadata in every image across our 52-site network using ExifTool, we saw a 40% increase in Google Images referral traffic within three months.

What IPTC/XMP Metadata Contains

IPTC and XMP are complementary metadata standards. Both are embedded in the image file itself and travel with the image wherever it goes — downloads, shares, reposts. The key fields:

Field	Purpose	Example
Creator	The person who created the image	J.A. Watte
Credit Line	How to credit the image	thecondotrap.com / J.A. Watte
Copyright Notice	The copyright statement	Copyright 2026 J.A. Watte. All rights reserved.
Source	Where the image originated	https://thecondotrap.com
Title	The image title	HOA Fees by State 2026 - Bar Chart Comparison
Description	What the image shows	Bar chart comparing average monthly HOA fees across all 50 US states, with Florida, New York, and California highlighted
Keywords	Searchable tags	HOA fees, real estate data, state comparison, 2026
Web Statement of Rights	URL to your rights/license page	https://thecondotrap.com/image-rights/

These fields are not visible in the image. They are embedded in the file's binary data. When Google's image crawler processes your image, it reads these fields to determine creator attribution, source URL, and content classification.

How Google Uses This Metadata

Google's image search documentation explicitly states that it uses IPTC metadata for rights attribution. The "Image Credits" feature in Google Images — which displays creator and credit information when a user clicks an image result — pulls directly from IPTC fields.

In 2024, Google expanded its use of image metadata to include:

Creator attribution in image search results
Source linking back to the original page
Rights information for licensing status
Content classification using keywords and description fields

For AI image models, the metadata serves an additional purpose: training data attribution. As AI companies face increasing pressure to credit source material, images with clear IPTC metadata are more likely to carry proper attribution through AI systems.

ExifTool: The Universal Metadata Tool

ExifTool is a free, open-source command-line program that reads and writes metadata in image files. It supports IPTC, XMP, EXIF, and every other metadata standard. It runs on Windows, macOS, and Linux.

Write metadata to a single image:

exiftool \
  -IPTC:ObjectName="HOA Fees by State 2026" \
  -IPTC:Caption-Abstract="Bar chart comparing average monthly HOA fees across all 50 US states" \
  -IPTC:By-line="J.A. Watte" \
  -IPTC:Credit="thecondotrap.com / J.A. Watte" \
  -IPTC:CopyrightNotice="Copyright 2026 J.A. Watte" \
  -IPTC:Source="https://thecondotrap.com" \
  -IPTC:Keywords="HOA fees, real estate data, state comparison" \
  -XMP:WebStatement="https://thecondotrap.com/image-rights/" \
  -XMP:Creator="J.A. Watte" \
  -XMP:Rights="Copyright 2026 J.A. Watte. All rights reserved." \
  image.webp

Write metadata to all images in a directory:

exiftool \
  -IPTC:By-line="J.A. Watte" \
  -IPTC:Credit="the20dollaragency.com / J.A. Watte" \
  -IPTC:CopyrightNotice="Copyright 2026 J.A. Watte" \
  -IPTC:Source="https://the20dollaragency.com" \
  -XMP:Creator="J.A. Watte" \
  -XMP:Rights="Copyright 2026 J.A. Watte. All rights reserved." \
  -overwrite_original \
  ./images/*.webp

Read metadata from an image:

exiftool -IPTC:all -XMP:all image.webp

The Build Pipeline Integration

For our 52-site network, manually running ExifTool on every image is not sustainable. Instead, we integrated it into the build pipeline:

Pre-build script: Before Eleventy (or any SSG) builds the site, a script iterates through the image directory and applies IPTC/XMP metadata to any image that does not already have it. The metadata values are pulled from the site's site.json data file, so each site's images get the correct creator, credit, and source URL.

#!/bin/bash
SITE_URL=$(jq -r '.url' src/_data/site.json)
AUTHOR=$(jq -r '.author' src/_data/site.json)

find src/images -name "*.webp" -exec exiftool \
  -if 'not $IPTC:By-line' \
  -IPTC:By-line="$AUTHOR" \
  -IPTC:Credit="$SITE_URL / $AUTHOR" \
  -IPTC:CopyrightNotice="Copyright 2026 $AUTHOR" \
  -IPTC:Source="$SITE_URL" \
  -XMP:Creator="$AUTHOR" \
  -overwrite_original \
  {} \;

The -if 'not $IPTC:By-line' condition ensures the script only processes images that have not already been tagged, so it is idempotent and safe to run on every build.

Per-image metadata: For images that need specific titles, descriptions, and keywords (data visualizations, infographics, featured images), we maintain a metadata CSV that the script reads to apply image-specific fields:

filename,title,description,keywords
blog-hoa-fees.webp,"HOA Fees by State 2026","Bar chart comparing HOA fees across 50 states","HOA fees,real estate,state data"
blog-insurance-rates.webp,"Condo Insurance Rates 2026","Line chart showing insurance rate trends 2015-2026","insurance,condo,rates,trends"

The Google Images Traffic Increase

Before deploying IPTC metadata, Google Images was a minor traffic source — less than 3% of total organic traffic across the network. The images appeared in search results, but without creator attribution, they did not drive meaningful click-through.

After deployment:

Google Images referral traffic increased 40% within three months
Image click-through rate improved from 1.2% to 2.8% — users were more likely to click through to the source when creator information was displayed
Image reuse with attribution increased — when other sites embedded our images, 23% more included a source credit (visible in backlink data)
Data visualization images saw the largest improvement: 67% increase in Google Images clicks, driven by the descriptive titles and keywords in IPTC fields

The attribution credit effect is the most valuable long-term impact. Every image that carries your IPTC metadata is a potential backlink generator. When it appears in a research paper, a blog post, or a news article, the metadata tells the author who created it and where it came from.

The Cost of Not Doing This

If your images do not have IPTC metadata:

Google Images does not display creator attribution for your images
Anyone can use your images without credit — there is no embedded ownership claim
AI models that ingest your images have no attribution data to propagate
Stock photo platforms that crawl the web cannot classify or credit your work
Your data visualizations — which may have taken hours to create — are anonymous

The fix takes 30 minutes for the build pipeline integration and runs automatically from that point forward. There is no ongoing maintenance cost.

The complete IPTC/XMP deployment guide — including the build pipeline scripts, the per-image metadata system, and the Google Images optimization strategy — is in The $20 Dollar Agency by J.A. Watte. Chapter 9 covers image SEO. For deploying image metadata across a multi-site network, see The $100 Network.