Showing evidence on product pages

Collecting evidence is the easy half. Most stores collect adequately and display badly, and displaying badly is the more expensive mistake — a review nobody sees is worth exactly nothing.

The one placement most stores miss

A star badge on product cards, in collection and search listings.

This is the highest-leverage placement available, and it is routinely skipped because it is not on the product page. Think about the actual sequence: a shopper sees twelve products in a grid and chooses which one to open. At that moment your product page has not happened yet. The rating on the card is the only evidence in play, and it decides which product gets the click.

<div data-evident-widget="star-badge" data-product-id="{{ product.id }}"></div>

Above the fold on the product page

A star badge immediately under the product title, with data-scroll-target pointing at your review section so clicking it goes somewhere:

<div
  data-evident-widget="star-badge"
  data-product-id="{{ product.id }}"
  data-scroll-target="#reviews"
></div>

Rating and count, in the first screenful, near the price. This is the “is this a real product that real people bought” check, and it happens in about two seconds.

Reviews inline, not in a tab

Put the review list in the page flow, below the description.

Reviews inside a collapsed tab are read by a fraction of the people who would read them inline. Tabs exist to make pages look tidy in a design review; they cost you the thing you spent months collecting.

<div id="reviews" data-evident-widget="review-list" data-product-id="{{ product.id }}"></div>

Leave the rating distribution on. A shopper who can see there are eleven one-star reviews out of four hundred trusts the average more than one who cannot. Leave sorting on — people deliberately seek out the critical reviews, and letting them find those quickly is a conversion event, not a risk. See Handling negative reviews.

Photos

Photo reviews outperform text by a wide margin, because they show the product in a real room, on a real person, at a real scale — and because they are hard to fake.

Two placements:

1. In the review list, inline with each review.
2. A gallery of approved customer photos, either on the product page or as a store-wide section pulling from photo reviews.

If you are choosing where to spend incentive budget, spend it here.

FAQs where the objection happens

An FAQ widget on the product page catches the question at the moment it occurs, rather than after the shopper has left to look for the answer.

<div
  data-evident-widget="faq"
  data-target-type="product"
  data-product-id="{{ product.id }}"
></div>

Write shipping, returns and sizing answers once as global FAQs and they cascade into every product’s widget automatically. Then add product-specific ones only where a product genuinely has its own questions.

The questions worth writing are the ones your support inbox already answers repeatedly. Anything else is marketing copy with a question mark on it.

The homepage and the cart

• Homepage — a review carousel or a customer photo gallery. Both are store-wide and need no product ID. For a first-time visitor this does more than another product grid.
• Cart or checkout — a small carousel near the checkout button, if your platform allows content there. It addresses the last moment of doubt.

Make it look like your store

Reviews that look bolted on get read as an advert. Theme the widgets from Storefront → Install & Theme, or override the CSS variables directly:

:root {
  --evident-font-family: inherit;
  --evident-primary: #111827;
  --evident-star-color: #f59e0b;
  --evident-radius: 6px;
}

--evident-font-family: inherit is usually the right answer — reviews take your storefront’s type without you naming a font, and survive a rebrand.

Set the variables rather than writing rules against internal class names, which are implementation detail.

Structured data

The FAQ widget emits FAQPage structured data automatically, and review data is exposed for rich results.

Treat search rich results as upside rather than the reason to do any of this. Google has narrowed eligibility considerably, and the conversion effect of visible on-page evidence is larger and entirely within your control.

An empty state is worse than nothing

A product with no reviews should not display an empty reviews section with a “0 reviews” heading. The blank space actively reads as “nobody bought this”.

Options, in order of preference: import history so it is not empty, show store-wide reviews on the page instead, or hide the section until the product has one.

A checklist

• Star badge on product cards in collection and search listings
• Star badge under the product title, linked to the reviews section
• Review list inline below the description, not in a tab
• Rating distribution and sorting visible
• Photo reviews rendering with their images
• FAQ widget with globals cascading in
• Widgets themed to your storefront
• No bare “0 reviews” empty states
• Homepage carousel or photo gallery