Image Metadata Structured Data: Complete Implementation Guide
ImageObject structured data allows you to provide Google with detailed information about images on your site, including licensing details, creator attribution, and copyright status. When implemented correctly, Google Images can display licence badges and creator information alongside your images, making it easier for users to find and properly attribute visual content. This is particularly valuable for photographers, stock image providers, news organisations, and any website that publishes original imagery.
Why Use ImageObject Schema?
- Display licence badges directly in Google Images search results, increasing click-through rates for licensable content.
- Ensure proper creator attribution is shown alongside your images across Google surfaces.
- Help users identify whether an image is free to use or requires a licence, reducing unauthorised usage.
- Improve discoverability of your visual content in image search by providing richer metadata signals.
- Protect your intellectual property by clearly communicating copyright and usage terms to search engines.
Required Properties
These properties are required by Google for ImageObject structured data to be eligible for rich results.
| Property | Description |
|---|---|
| contentUrl | The URL of the actual image file. This must be a crawlable and indexable URL that points directly to the image resource. |
| license | A URL to the licence agreement or terms under which the image may be used. This can be a Creative Commons URL or a page on your own site detailing the licence. |
| acquireLicensePage | A URL to a page where users can find information about how to licence the image. This is required when the image is available for licensing. |
Recommended Properties
Adding these properties improves your chances of appearing in rich results and provides more context to search engines.
| Property | Description |
|---|---|
| creator | The person or organisation that created the image. Use a nested Person or Organization object with a name property. |
| copyrightNotice | A text string describing the copyright holder and year, e.g. 'Copyright 2025 Jane Smith'. Displayed as attribution in search results. |
| creditText | The credit line that should accompany the image when it is published, such as the photographer or agency name. |
| name | A descriptive title for the image. Helps search engines understand the subject matter of the visual content. |
| description | A textual description of what the image depicts. Supports accessibility and improves relevance in image search queries. |
JSON-LD Example
Here is a complete ImageObject structured data example you can use as a starting point. Or use our ImageObject generator to create one automatically.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ImageObject",
"contentUrl": "https://example.com/images/london-skyline.jpg",
"license": "https://creativecommons.org/licenses/by/4.0/",
"acquireLicensePage": "https://example.com/licensing/london-skyline",
"creator": {
"@type": "Person",
"name": "Sarah Thompson"
},
"copyrightNotice": "Copyright 2025 Sarah Thompson",
"creditText": "Sarah Thompson / Example Photography",
"name": "London Skyline at Sunset",
"description": "A panoramic photograph of the London skyline taken from the South Bank at golden hour, featuring the Shard, Tower Bridge, and the City of London financial district.",
"datePublished": "2025-06-15",
"width": 4000,
"height": 2667
}
</script>How to Implement ImageObject Schema
- 1Identify which images on your site would benefit from structured data — prioritise original photography, illustrations, and any licensable content.
- 2Add a JSON-LD script block to each page containing the ImageObject markup. Place it in the <head> or at the end of the <body>.
- 3Set the contentUrl to the full, canonical URL of the image file. Ensure this URL is not blocked by robots.txt.
- 4Include the license property pointing to the applicable licence page. Use standard Creative Commons URLs where appropriate.
- 5Add creator, copyrightNotice, and creditText properties to ensure proper attribution is displayed in Google Images.
- 6Validate your markup using Google's Rich Results Test and monitor performance in the Google Search Console Images report.
Common Mistakes to Avoid
- Using a relative URL for contentUrl instead of an absolute URL — all URLs in structured data must be fully qualified.
- Pointing the license property to a generic terms-of-service page rather than the specific licence that applies to the image.
- Omitting acquireLicensePage when the image is available for licensing, which prevents the licence badge from appearing.
- Adding ImageObject markup to images you do not own or hold the rights to, which can lead to policy violations.
- Failing to keep structured data in sync when images are updated, moved, or relicensed on the site.
Testing & Validation
Before deploying your ImageObject structured data, validate it using these tools:
- 1Google Rich Results Test — Paste your page URL or code snippet to check if your structured data is eligible for rich results.
- 2Schema Markup Validator — Validates your JSON-LD syntax against the schema.org specification.
- 3Google Search Console — After deployment, monitor the Enhancements report for any errors or warnings.
Frequently Asked Questions
Does ImageObject structured data guarantee a licence badge in Google Images?
No. Adding structured data makes your images eligible for licence badges, but Google determines whether to display them based on its own quality and relevance criteria. Correct implementation significantly increases the likelihood of badges appearing.
Can I use ImageObject structured data for stock photos I have purchased?
You should only add licensing structured data to images for which you hold the rights or are the original licensor. If you purchased a stock photo, the licence information should come from the original provider, not your site.
How does ImageObject structured data differ from IPTC metadata embedded in image files?
ImageObject structured data is read from the HTML page by search engine crawlers, while IPTC metadata is embedded directly in the image file. Google supports both, but structured data in JSON-LD is generally easier to manage at scale and does not require re-encoding image files.
Should I add ImageObject markup to every image on my site?
Focus on images where licensing and attribution matter — original photographs, illustrations, infographics, and other creative works. Decorative images, icons, and UI elements do not benefit from this markup.
Can I specify multiple creators for a single image?
Yes. The creator property accepts an array of Person or Organization objects, allowing you to credit multiple contributors such as the photographer and the retoucher.
Ready to Generate Your ImageObject Schema?
Use our free generator to create valid ImageObject structured data in seconds.
Open ImageObject Generator