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.
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.
In this article
We make Idukki. Our reviews product 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.
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.
The hub story order
Shoppers read proof in a fixed order. Match the hub to that order.
- 1Rating summary. Average, count, and a bar per star.
- 2What customers say. A short labelled AI summary, only when enough reviews exist.
- 3Customer photos and videos. A strip that opens into the full review.
- 4Reviews list. Sortable, filterable, with verified marks that match how each review was collected.
- 5Questions 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. 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
- 1Studio media firstBrand-owned
Keep the first slot a still. Customer video can sit later.
- 2Price, variants, add to cartConversion
A compact star row can sit here. The full hub starts below.
- 3Stars, summary, photos, list, Q&AVerified reviews
One embed under the buy box. Sections can be switched off per collection.
- 4Specs the hub should not repeatBrand-owned
Materials, shipping and returns stay in theme copy.
- 5Optional shoppable UGC railCustomer UGC
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
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.
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 |
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
- 01
Pick the collection
Use the collection that holds reviews and tagged customer posts.
- 02
Choose Product Page Hub
Set that layout on the collection. Embed code stays the same.
- 03
Filter to the product
Set filter-pid on the product template so only that product's posts show.
- 04
Switch sections
Turn off any section you do not need. Set reviews per page.
- 05
Check both states
Open a product with reviews and one without.
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.
Questions store owners ask
Can we keep our old reviews app and only hub the photos?
You can, but siloed stars and photos recreate the bounce. Prefer one list shoppers can filter, with photos attached to each review.
Where should the compact star row sit?
Near the price on mobile, with the full hub below the buy box. Do not duplicate a long list in both places.
Do we need Q&A on every product?
Start on bestsellers and high-return SKUs. Turn the section off where nobody asks.
Will one hub slow the page?
One script is usually cheaper than three. In Idukki, Q&A and AI summary pieces load on demand.
Sources and related reading
More from Rohin Aggarwal
- Strategy
Repurposing customer support videos and unboxings as marketing assets
Support teams and customers already make the videos a product page is missing: assembly walkthroughs, fit checks, what is in the box. Who owns each kind, what consent you need, how to clean a clip for the PDP, and a monthly workflow that moves the good ones from the help desk to the storefront.
- Strategy
Live shopping tech stack for a Shopify brand
What a Shopify brand actually needs to run a live shopping stream: streaming, cart sync, chat moderation, and the pieces that get forgotten until the stream is already live.
- Strategy
Measuring live shopping ROI beyond concurrent viewers
Peak concurrent viewers is the easiest live shopping number to report and one of the least useful for deciding whether to run another stream. The metric stack to use instead, how to track it with UTMs and Shopify reports, a worked ROI example, and a report template.