Idukki
AI search

Structured data and schema for product UGC

Customer photos, videos and reviews only count for search and AI agents if a machine can parse them. This is the schema that turns a gallery into visibility.

The PDP had flawless Product schema, flawless Offer schema, and not one line of UGC-shaped markup. The audit caught it, the fix took eleven minutes, and the AI-citation rate for that page doubled over the next four weeks. The schema patterns that did the work are below.

In this article

A product page can be stuffed with customer photos, videos and reviews and still read, to a search engine or an AI shopping agent, as a blank. Machines do not infer from a nice layout; they parse markup. Structured data is how your UGC becomes legible to them, and legible UGC is the only UGC that earns rich results and agent recommendations.

Why does UGC need schema?

Search engines render review stars and rich results from structured data, not from a pretty widget. AI agents corroborate product claims against review and rating data they can actually read. UGC that lives only inside an unannotated gallery or a slow iframe is doing work for the shopper on the page and none at all for your visibility. This is one of the highest-leverage moves in the answer-engine optimisation playbook, and it sits alongside the other markup shapes covered 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, not just 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
AggregateRatingOverall 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, and it has to agree with what a human sees on the page. A rating in the markup that does not match the rating on screen, or reviews not tied to the product they describe, is worse than shipping no schema at all: it reads as a mismatch, and a mismatch gets discounted or penalised.

A checklist

  1. 1Emit Review + AggregateRating on product pages, sourced only from genuine reviews.
  2. 2Add ImageObject / VideoObject for customer media so visual UGC is described.
  3. 3Tie every piece of schema to the correct product entity.
  4. 4Confirm the markup matches the visible page exactly.
  5. 5Validate with a structured-data testing tool, and 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, 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.
  • +0%

    Median PDP CVR lift from UGC

    Idukki page-level

  • +0%

    Median AOV lift

    Same cohort

  • +0%

    Compound RPV lift

    CVR x AOV

  • +0%

    Median dwell-time lift

    Idukki dataset

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

Continue reading

3 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

We use cookies

We use essential cookies to run this site and optional analytics cookies to understand how it’s used. You can change your choice anytime in our privacy policy.