Star Ratings on the Product Page: Above the Fold or Buried?

Where on the product page should the star rating go?

Directly under the title, in the price block, above the fold. The area around the product name and price is among the most-looked-at parts of a product page, so the star summary belongs there and nowhere lower. A shopper deciding whether to keep reading wants the verdict before the specs, and the rating is the verdict.

This is not a place for the full review list. It is a place for a compact summary: average, count, and a link. The detail lives further down. The summary lives where the decision is made.

• Under the product title, in or beside the price block.
• Average score, the star glyphs, and the rating count together.
• The count as a clickable link that jumps to the full review section.
• Above the fold on both desktop and the first mobile viewport.

What should the star summary actually contain?

Three things, in this order: the average score, the stars themselves, and the count of ratings. The number matters as much as the stars. A 4.6 from 800 reviews reads very differently from a 4.6 from 4, and shoppers calibrate trust on the count as fast as on the average.

Make the count a link, not decoration. "412 reviews" should scroll the page to the full review section. That single anchor does double duty: it helps a shopper who wants proof, and it ties the summary to the corroborating detail a crawler will read next.

Should the summary link down to the full reviews?

Yes, and this is the part most stores skip. The star summary near the title should link down to the full, crawlable review section. For the shopper, that anchor removes friction: tap the count, land on the evidence. For the page itself, the link makes the relationship explicit between the headline number and the reviews that justify it.

The full section is where the substance sits: individual reviews, dates, and verified-buyer signals. The summary is a promise; the section is the proof. Keep them connected with a real in-page anchor rather than leaving the shopper to scroll and hope.

Why does the rating need to be in the server HTML?

Because rendering the rating in the server HTML makes it eligible for search snippets and AI citation. When the average and count are present in the page source before any script runs, a crawler reads them on the first pass, and that is what feeds the star-rating rich result in Google and the numbers an answer engine can quote.

Most review apps inject the summary through a JavaScript widget after load. A shopper still sees stars. A crawler often sees an empty container, so the rating that is plainly visible to a person is missing from the document a machine reads. The format on screen can be perfect and still earn nothing in search if the number is not in the HTML.

How should I format the rating so it stays readable?

Keep it legible, keep it honest, and keep the layout stable. Show the numeric average to one decimal next to the stars rather than relying on glyphs alone, since partial stars are hard to read at a glance. Reserve the vertical space the summary will occupy so it does not shove the price or button down when it loads, which protects both the buyer experience and your layout-shift score.

• Numeric average to one decimal, paired with the star glyphs.
• Rating count in plain text next to the average, not hidden on hover.
• A reserved block so the summary does not push the price on load.
• Adequate contrast on the stars and the count, not a faint grey.

Does the placement also affect schema and rich results?

It does, because placement and markup are the same problem seen from two sides. The visible summary and the structured data should describe the same average and count, drawn from the same source, so a person and a crawler see one consistent rating. When the on-page number and the AggregateRating markup disagree, you risk the rich result being dropped.

This is where CRO and schema meet. The placement decision (under the title, in the server HTML) is also the decision that makes your structured data trustworthy and your rating quotable. Get the summary into the page source correctly and you serve the shopper above the fold and the snippet at the same time.

What this adds up to

Put the summary where the eye lands, format it so the average and count are both legible, link it to the full review section, and render the whole thing in the server HTML. Do that and one element serves the shopper, the Google rich result, and the AI answer at once. Most review apps were built for the on-page shopper and stop at the widget, which is the gap BetterReviews is built to close: getting the reviews you already have readable, corroborated, and cited, in search and in AI.