When and how to add images to structured data

Adding images to your structured data tells search engines and other consumers which visuals belong with a product, article, recipe or event, and those images can be used in rich results. Getting the property names and the image requirements right matters, because a missing or invalid image is a common reason a structured-data test flags an error.

Know the properties

• The image property. Most content-based schema types (Article, Product, Recipe, Event, WebPage) accept an image property. It can be a single URL string, an array of URLs, or an ImageObject with its own properties.
• Use ImageObject for control. An ImageObject lets you add a caption, upload date, author and licensing plus width and height. Use the simplest form that meets your needs, and prefer ImageObject when multiple images share metadata.
• Point at real, crawlable images. The URLs you list should be actual image files that resolve over HTTPS and return image content, not empty or placeholder paths, because the image must be fetchable to be useful.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example notebook",
  "image": [
    "https://www.example.com/images/notebook-front.jpg",
    "https://www.example.com/images/notebook-open.jpg"
  ],
  "offers": { "@type": "Offer", "price": "12.00", "priceCurrency": "GBP" }
}

Follow size guidance

• Meet the recommended dimensions. Google's rich-result documentation sets minimum width and height per rich-result type, so check the current guidance for the type you target rather than assuming one universal minimum.
• Use supported formats. WebP and JPEG are safe choices alongside the formats your site already serves. Avoid obscure formats for structured-data images.
• Keep the image relevant and in-scope. Rich-result policies can reject images that are cropped, mislabelled, or that do not correspond to the item (such as a logo standing in for a product).

Validate and review

• Test in the Rich Results Test. Paste the page or run a URL and check that the image property is populated and valid for the type you targeted.
• Reuse one canonical image style. If you maintain a single image per page, keeping the structured-data image consistent with the visible hero or main image avoids mismatches that a reviewer or consumer notices.
• Expect no guaranteed appearance. Structured data is input to rich results, not a contract that an image will show. Valid data increases the chance a result is eligible, but appearance depends on many ranking and policy factors. For related structured-data patterns, see the breadcrumb schema and general structured data guides.