Skip to content
NewProduct Q&A: shoppers ask on your product page and get your answers.See how it works
IdukkiIdukki
AI search

Structured data and schema for product UGC

Customer photos, videos and reviews count for search and AI once machines can parse them. This schema turns a gallery into visibility.

Paste your best product page into Google’s Rich Results Test. Product and Offer come back clean. The customer photos and reviews below them do not appear at all. To a machine, your social proof is not there.

In this article

A product page can be stuffed with customer photos, videos and reviews. To a search engine or an AI shopping agent, it can still read as a blank. Machines parse markup. A nice layout tells them nothing. Structured data makes your UGC legible to them. Only legible UGC earns rich results and agent recommendations.

Why does UGC need schema?

Search engines render review stars and rich results from structured data. A pretty widget does not count. AI agents corroborate product claims against review and rating data they can actually read. UGC inside an unannotated gallery or a slow iframe works for the shopper on the page. It does nothing for your visibility. This is one of the highest-leverage moves in the answer-engine optimisation playbook. It sits beside the other markup shapes in the twelve JSON-LD shapes agents quote.

Which schema types actually matter?

  • Review: individual customer reviews, each with author, rating and date, attached to the product.
  • AggregateRating, the overall rating and review count, drawn honestly from real reviews.
  • ImageObject: customer photos, so visual UGC is described as well as displayed.
  • VideoObject, customer videos, with the metadata that lets them be indexed and understood.
Schema typeCarriesWhat it earns
ReviewAuthor, rating, body, date, tied to the productPer-review snippets; agent corroboration
AggregateRatingAverage score and review countStar rating in search and agent answers
ImageObjectCustomer photo URL, caption, dimensionsImage indexing; visual UGC described
VideoObjectVideo URL, thumbnail, duration, upload dateVideo rich results; clip indexing
The four UGC schema types, what each one carries, and where it surfaces.

How do you tie UGC to the right product?

Schema on its own is not enough. It has to bind the UGC to the specific product entity. It has to agree with what a human sees on the page. Picture a markup rating that differs from the rating on screen. Or reviews not tied to the product they describe. Both are worse than no schema at all. They read as a mismatch, and a mismatch gets discounted or penalised.

A checklist

Five steps to machine-readable UGC

  1. 01

    Reviews and rating

    Emit Review and AggregateRating on product pages, sourced only from genuine reviews.

  2. 02

    Customer media

    Add ImageObject and VideoObject, so visual UGC is described.

  3. 03

    Bind to the product

    Tie every piece of schema to the correct product entity.

  4. 04

    Match the page

    Confirm the markup matches the visible page exactly.

  5. 05

    Validate

    Run a structured-data testing tool. Re-check after template changes.

A nice gallery helps the shopper on the page and nobody else. Schema is what makes that UGC count for search and for AI agents.

Rohin Aggarwal · Co-founder & CTO, Idukki

Sources & notes

  1. 1Schema.org: Review, AggregateRating, ImageObject, VideoObject · The structured-data vocabulary for UGC.
  2. 2Google Search Central, review snippet & product structured data · Implementation and policy guidance.
  • 161%

    higher conversion among shoppers who interact with UGC

    Yotpo, 200k+ stores / 163M orders analyzed

  • +162%

    more revenue per visitor among shoppers who engage with UGC

    Bazaarvoice, Shopper Experience Index

  • 4.1x

    video reviews convert vs text-only

    PowerReviews, 2023 baseline

Core ecommerce + UGC metrics worth tracking.
#ai-search#structured-data#ugc#seo

Continue reading

4 pieces in this cluster

These long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.

More from Rohin Aggarwal