# A PDP review hub that converts: stars, summary, gallery and Q&A

Fix siloed widgets with one hub story: stars, summary, gallery, Q&A. Theme map and measurement included.

By Rohin Aggarwal · 2026-10-31

A shopper reaches the buy button and stops. Stars sit in one app. Photos sit in another. Questions open a third tab. She leaves to read Reddit instead. The proof was on your page the whole time. It was just never in one place.

**Quick answer**

- **One hub under the buy box.** Stars, summary, photos, reviews, then Q&A.
- **Siloed widgets break the story.** Shoppers stop scrolling between apps.
- **Mobile gets a short stack.** Desktop can show the photo strip beside the list.
- **Measure scroll depth and add-to-cart.** Not vanity open rates on the widget.
- **We make Idukki.** The product page hub is one layout for that stack.

We make Idukki. Our [reviews product](/reviews) and product page hub put the full proof stack in one embed. The layout ideas below still apply if you wire the same order with separate blocks.

_Figure: One product-page story: rating, what customers say, their photos, the reviews, then questions._

## What breaks when widgets are siloed

Separate apps each solve one job. Together they leave gaps a shopper falls through.

- **Stars without photos.** The average looks fine. Fit and colour stay unanswered.
- **Photos without the review.** A stranger in the dress, no size, no date, no verified mark.
- **Q&A in a buried tab.** The question that would have closed the sale never gets asked.
- **Three scripts on one template.** Extra weight, three moderation inboxes, three style systems.

Siloes also break measurement. Separate events hide which block moved add-to-cart.

> **Count the embeds on one PDP:** Open view-source or your tag manager. Three vendors for reviews, UGC and Q&A is a speed and ops problem.

## The hub story order

Shoppers read proof in a fixed order. Match the hub to that order.

1. **Rating summary.** Average, count, and a bar per star.
2. **What customers say.** A short labelled AI summary, only when enough reviews exist.
3. **Customer photos and videos.** A strip that opens into the full review.
4. **Reviews list.** Sortable, filterable, with verified marks that match how each review was collected.
5. **Questions and answers.** Peer help for the doubt the reviews did not settle.

Product Q&A as its own trust tool is covered in [product Q&A on the PDP](/blog/product-qa-the-underused-pdp-trust-tool). In a hub it sits last, after the shopper has skimmed stars and photos.

## Theme block map

**Where the hub sits on a product page**
- **Image gallery — Studio media first:** Keep the first slot a still. Customer video can sit later.
- **Buy box — Price, variants, add to cart:** A compact star row can sit here. The full hub starts below.
- **Review hub — Stars, summary, photos, list, Q&A:** One embed under the buy box. Sections can be switched off per collection.
- **Details and care — Specs the hub should not repeat:** Materials, shipping and returns stay in theme copy.
- **Complete the look — Optional shoppable UGC rail:** Tagged social posts, separate from the review hub if you need more media.

## Mobile vs desktop

**Same hub, two stacks**
Mobile:
- Compact stars under the price
- Summary collapsed to three lines
- Horizontal photo strip
- Reviews five at a time
- Q&A behind a clear chip
Desktop:
- Full rating bars beside the average
- Summary visible without a tap
- Photo strip above or beside the list
- Filters in a single row
- Q&A open in the same column
_Layout sketch only. Measure on your own theme._

On a phone, protect the add-to-cart button. Do not push it below a tall hub. Keep a short star row near the price. Put the hub under the fold.

> **Test one product with no reviews:** Open a new SKU. The hub should show an honest empty state or a labelled fallback. Idukki can show similar-product posts under a clear label when nothing is tagged yet.

## Measurement on the PDP

| Event | What it tells you | Watch out for |
| --- | --- | --- |
| Hub viewed | Shoppers reached proof | Fired too early if the embed loads above the fold |
| Photo opened | Media is working | Count unique shoppers, not every swipe |
| Filter used | List is too long without help | A high rate can also mean weak sorting defaults |
| Q&A opened / asked | Reviews left a doubt | Pair with the question text in your inbox |
| Add to cart after hub view | Proof near the decision | Use a short attribution window on the same page view |

_Events worth tracking on the hub. Keep names stable across theme changes._

Skip vanity scores such as "widget opens". Prefer add-to-cart and checkout steps for sessions that reached the hub.

## Idukki hub setup

**Put the product page hub live**
1. **Pick the collection** — Use the collection that holds reviews and tagged customer posts.
2. **Choose Product Page Hub** — Set that layout on the collection. Embed code stays the same.
3. **Filter to the product** — Set filter-pid on the product template so only that product's posts show.
4. **Switch sections** — Turn off any section you do not need. Set reviews per page.
5. **Check both states** — Open a product with reviews and one without.
_From the product page hub help article. Collection layout + product filter._

AI summaries need five or more approved reviews and stay off until you switch them on. Imported Google, Trustpilot and TripAdvisor reviews are not marked up for rich results. Full steps sit in [the product page hub help article](/help/product-page-hub).

**The rule to use:** Tell one proof story under the buy box: rating, summary, photos, reviews, Q&A. Measure add-to-cart for sessions that reached that story.

### Questions store owners ask

**Q: Can we keep our old reviews app and only hub the photos?**

A: You can, but siloed stars and photos recreate the bounce. Prefer one list shoppers can filter, with photos attached to each review.

**Q: Where should the compact star row sit?**

A: Near the price on mobile, with the full hub below the buy box. Do not duplicate a long list in both places.

**Q: Do we need Q&A on every product?**

A: Start on bestsellers and high-return SKUs. Turn the section off where nobody asks.

**Q: Will one hub slow the page?**

A: One script is usually cheaper than three. In Idukki, Q&A and AI summary pieces load on demand.

### Sources and related reading
- [Idukki: Reviews](/reviews)
- [Idukki help: product page hub](/help/product-page-hub)
- [Idukki: product Q&A as a PDP trust tool](/blog/product-qa-the-underused-pdp-trust-tool)
- [Idukki: photo review widget examples](/blog/photo-review-widget-examples)
- [Idukki help: turn on AI review summaries](/help/turn-on-ai-review-summaries)

---
Canonical: https://idukki.io/blog/pdp-review-hub-stars-summary-gallery-qa
Tags: reviews, pdp, product-page, fashion, product-qa, cro, widgets