Does Google need image metadata for every occurrence of an image?

Definition: Image metadata is information that describes an image, such as its licence, creator or credit. For structured data, Google documents a page-level association for every instance where an image is used. If the same image appears on several pages, the association is repeated on each page.

Key facts

• Google's image metadata documentation says to add structured data or IPTC photo metadata to each image, including each page appearance of an image reused across pages.
• Google describes structured data as an association between an image and the page where it appears, and says to add it for every image instance, even when the file is the same.
• IPTC photo metadata is embedded in the image file. Google says it can travel with the file between pages and needs to be embedded only once per image.
• When IPTC metadata and structured data conflict, Google's documented precedence gives the structured data information priority.
• Schema.org defines ImageObject as an image file and defines contentUrl as the URL for the actual bytes of the media object.

What does every occurrence mean for structured data?

Google's documentation, updated 10 December 2025, treats structured data as a relationship between an image and the page containing it. Its rule is expressed at the instance level: every use of the image receives structured data, including a reuse of the same file. The page also states explicitly that a repeated image on multiple pages receives structured data on each page where it appears.

This makes ImageObject page-level metadata. A file-level record embedded in the image does not replace the page association required for structured data. The public guidance gives a single-image example and does not show a separate snippet for two identical image elements on one page. Its wording about every instance is the relevant rule for that case.

What should the ImageObject describe?

Schema.org's ImageObject type represents an image file. Its contentUrl property identifies the actual media bytes. For licensing information, Google's example uses license for the page describing the licence, acquireLicensePage for the page explaining how to obtain a licence, plus creditText, creator and copyrightNotice.

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "ImageObject",
  "contentUrl": "https://example.com/photos/1x1/black-labrador-puppy.jpg",
  "license": "https://example.com/license",
  "acquireLicensePage": "https://example.com/how-to-use-my-images",
  "creditText": "Labrador PhotoLab",
  "creator": {
    "@type": "Person",
    "name": "Brixton Brownstone"
  },
  "copyrightNotice": "Clara Kent"
}
</script>

The structured data belongs to the page containing the image instance. The values can describe the same underlying file on different pages, provided they continue to describe that file and the page association remains present.

How does IPTC metadata differ?

IPTC metadata is stored inside the image itself, so it remains with the file as the file moves between pages. Google says one embedded IPTC record per image is sufficient for this purpose. The structured-data rule is different because the markup connects the image to a page. Google says either structured data or IPTC metadata is sufficient for enhancements such as the Licensable badge.

Google Images can show details such as the creator, permitted use and credit information when image metadata is supplied. The image SEO documentation also recommends using the same image URL when an image is referenced on multiple pages, so Google can cache and reuse it without requesting it repeatedly.

How can the placement be checked?

Google recommends validating structured data with the Rich Results Test. It also recommends testing deployed pages with the URL Inspection tool, checking that Google can access the page and that robots.txt, noindex or login requirements do not block it. A check should inspect every page template where the image occurs, because the documented requirement follows the page appearance.

Related terms

• Which image metadata wins when IPTC and structured data conflict?
• How can embedded image metadata identify an AI-created image?

FAQ

Does the same ImageObject need to appear on every page where the image is reused?

Yes. Google says structured data must be added for each image instance and for each page on which the same image appears.

Is IPTC metadata a substitute for page-level structured data?

Google documents either structured data or IPTC photo metadata as sufficient for enhancements such as the Licensable badge. IPTC is embedded once in the image, while structured data is associated with each page appearance.

What happens when IPTC and structured data disagree?

Google says it uses the structured data information when the two forms conflict.

Sources

1. Google Search Central, "Google Images SEO: Image Metadata", 10 December 2025
2. Schema.org, "ImageObject - Schema.org Type", 16 September 2026
3. Google Search Central, "Image SEO Best Practices", 2 March 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer