Place the compact, product-specific star summary directly below the product title or between the title and price as your starting point. That keeps the rating average and review count early in the buying flow without separating them from the product they describe.
Test a position nearer the price or immediately before the buy controls only when the current layout creates a specific problem—for example, a large promotion block pushes the rating away from the purchase decision, or the mobile order makes the proof easy to miss.
Do not move the stars and redesign the rest of the buy box at the same time. A placement test should answer one question: does changing where shoppers encounter the rating summary improve the path from product evaluation to purchase without creating a usability or layout regression?
Separate the star summary from the full reviews widget
The compact star summary and the full reviews section solve different jobs.
The star summary is an orientation cue. It normally shows the product’s average rating and the number of reviews in a small footprint. It helps shoppers decide whether the product has enough relevant customer evidence to investigate further.
The full reviews widget is the evidence destination. It can contain the rating distribution, individual review text, customer photos or videos, filters, sorting, variants, and merchant replies. Its location and layout deserve a separate decision because moving that larger component into the buy box would fundamentally change the page.
Loox documents this separation in its default integration: the Star Rating Widget appears between the product title and pricing, while the Reviews Widget appears toward the bottom of the product page. Both can be moved independently. See Changing the Location of Loox Widgets.
This article owns only the compact summary. It does not decide where the full review gallery should sit, how its cards should be sorted, or whether a carousel, grid, or list is the right detailed-review format.
Map the buy box before moving the rating summary
“Above the fold” is too vague to make this decision. Product pages differ, and the same block order can create a different experience depending on the number of variants, subscription options, promotions, shipping messages, and sticky purchase controls.
Write down the current desktop and mobile order for each important product template:
- Product title
- Star summary
- Price and compare-at price
- Promotion or financing message
- Variant and selling-plan selectors
- Quantity control
- Shipping or availability message
- Add-to-cart or buy button
- Short product proof or reassurance
Then ask three questions.
Is the rating clearly attached to the correct product?
The shopper should not have to infer whether the stars describe the product, the entire store, or a promotional claim. Product-specific ratings are the cleanest default on a product page because the evidence and the item under consideration match.
Loox offers a Show all reviews option that can display a store-wide aggregated average instead of the current product’s rating. That is a real configuration choice, but it changes the meaning of the proof—not merely its position. Freeze that setting during a placement test. The current options are listed in Customizing the Star Rating Widget.
Can shoppers interpret the rating without extra work?
Stars alone are weak evidence. A 4.8 average based on six ratings and a 4.8 average based on six thousand ratings do not carry the same information.
Baymard’s product-rating research reports that shoppers look for both the rating average and the number of ratings behind it. Its research also found that reviews were used extensively when evaluating products. The practical implication is simple: keep the numerical context or review count visible instead of turning the summary into a decorative row of icons. See Baymard’s ecommerce CRO guidance.
Does interacting with the summary lead somewhere useful?
If the stars look interactive, confirm what happens when a shopper clicks or taps them. Loox can be configured so clicking the rating icons opens its Floating Reviews Widget. If that option is not enabled, test the actual behavior rather than assuming the summary scrolls to the full reviews section.
This matters because Baymard observed users expecting a visible rating summary to take them to reviews. A control that appears to promise review access but leads nowhere creates a navigation failure, regardless of its position. See Baymard’s product-page navigation research.
Compare the three useful placement zones
There is no reason to test every possible slot. Most Shopify product pages can narrow the decision to three zones.
| Placement zone | Strongest reason to use it | Main risk | What would justify a test |
|---|---|---|---|
| Directly below the product title | Establishes product-specific proof before pricing and controls compete for attention | Can feel distant from Add to cart on a long or promotional buy box | Use as the default control unless it is technically broken or visually detached |
| Beside or immediately below the price | Keeps proof close to value evaluation | Discounts, installment copy, tax notes, and dynamic pricing can make the area crowded | Test when price is the main hesitation and the summary remains clearly associated with the product |
| Immediately before variants or Add to cart | Places proof near the commitment point | Can interrupt required selections, create visual noise, or push the primary action lower on mobile | Test when shoppers reach the controls without encountering credible proof earlier |
Treat the table as a hypothesis map, not a ranking. The right treatment depends on the existing content order and the problem the merchant can observe.
Why under-title placement is the safest default
Loox currently recommends placing its Star Rating Widget under the product title. Its separate location guide says the initial integration places the widget between the title and pricing. Both describe the same general principle: introduce the compact proof early, while its relationship to the product is unambiguous. See the current Loox Star Rating Widget guide.
That default has four practical advantages.
- The proof has a clear subject. It immediately follows the product name.
- The rating appears before buy-box complexity. Promotions, variants, subscriptions, shipping messages, and payment terms have not yet competed for attention.
- The desktop and mobile story is easier to preserve. A simple title-rating-price order usually survives narrow screens more predictably than an inline price-and-rating composition.
- It provides a stable control. If the current placement works and no measurable problem exists, the merchant does not need to invent a treatment merely to run a test.
“Default” does not mean “proven winner.” Loox’s recommendation documents how its widget is intended to be placed; it is not independent evidence that every store will gain conversion by using that position.
When a position closer to price deserves a test
A near-price treatment can make sense when the price is the first major objection and customer proof helps shoppers interpret value. Examples include products with a clear premium, a visible compare-at price, or a short buy box where title, rating, and price remain one compact group.
Do not force the summary into the price row if the price changes with variants, selling plans, quantities, or markets and the rating block becomes unstable or visually ambiguous. Keep the implementation simple enough that the shopper can still distinguish rating, review count, current price, and promotion.
The treatment should normally preserve the same product-specific average, count, wording, icon, color, and click behavior as the control. Otherwise the test compares a different proof treatment, not merely a different location.
When a pre-add-to-cart position deserves a test
Moving ratings immediately before variants or Add to cart is the most aggressive placement. It can be useful when the current theme places several informational blocks between the early rating and the purchase controls, leaving proof visually disconnected from the moment of commitment.
It is a poor candidate when:
- required size, color, subscription, or bundle choices already make the control area dense;
- the rating block pushes Add to cart materially farther down the mobile page;
- a sticky purchase bar duplicates the rating or changes the content order;
- the product has too few credible reviews for the summary to reduce uncertainty;
- another proof block, such as a review snippet, already occupies the same decision moment.
Proximity is not value. A block near Add to cart helps only if it answers an unresolved question without competing with the action the shopper must complete.
Keep the star summary decision-useful
Loox’s current app block provides controls for size, text, text visibility, alignment, default or single-icon layout, text color, star color, store-wide versus product-specific scope, click behavior, and empty stars. Those controls make the widget flexible, but they also create confounding variables.
Before testing placement, record the current settings and freeze them.
| Setting | Why it must stay fixed during the placement test |
|---|---|
| Product-specific or store-wide rating | Changes what the proof represents |
| Rating average and review count text | Changes the amount and credibility of information |
| Default or single-icon layout | Changes visual weight and recognition |
| Size, color, and alignment | Changes prominence independently of position |
| Click destination | Changes the shopper journey after interaction |
| Empty-star behavior | Changes which products display a visible summary |
If the store needs to compare these settings, run that as a later experiment. Placement should first answer where a constant proof treatment performs its job most clearly.
Check theme and mobile feasibility before designing a test
Shopify allows app blocks to be added, previewed, and repositioned through the theme editor, but only compatible themes and sections expose the necessary block positions. Some sections do not accept app blocks, and incompatible moves can return the block to its prior location. Review Shopify’s app-block guidance and sections-and-blocks documentation before assuming all three zones are available.
Use a duplicate or unpublished theme for the feasibility pass. For each important product template, check:
- desktop and mobile order;
- long product titles and long review counts;
- zero-review, low-review, and high-review products;
- products with and without compare-at pricing;
- one-variant and many-variant products;
- subscription, bundle, preorder, or financing controls where applicable;
- sticky add-to-cart behavior;
- whether the rating interaction still opens the intended review destination;
- visible wrapping, overlap, duplication, or unexpected spacing.
This is not a full accessibility or performance audit. Those deserve their own specialists and test plans. Here, the purpose is to reject a placement that is visibly broken, unavailable, misleading, or impossible to compare cleanly.
Run the Buy-Box Proof Placement Test Plan
1. Define the placement problem
Write one falsifiable problem statement. For example: “On the primary mobile template, promotional and financing copy separates the under-title rating from the variant and purchase controls, so shoppers may reach Add to cart without using the available review evidence.”
Avoid statements such as “Ratings should be closer to the button.” That is a preferred solution, not an observed problem.
2. Choose the eligible templates and products
Identify which product templates receive meaningful traffic and whether their buy-box structures differ. Do not mix a simple one-variant product with a subscription product and assume one position represents both experiences.
Exclude products whose review meaning changes during the test—for example, a new launch moving rapidly from no reviews to many reviews—unless that change is explicitly part of the analysis.
3. Lock the control and one treatment
Use the current under-title or title-to-price placement as the control unless it is broken. Choose only one treatment:
- move the same block beside or immediately below price; or
- move the same block immediately before the buy controls.
Keep copy, average, count, icon, color, alignment, click behavior, review scope, offers, price presentation, variants, and primary CTA unchanged.
4. Prefer concurrent assignment
When the store’s testing stack supports it, expose comparable visitors to control and treatment during the same period. Concurrent assignment reduces the risk that campaigns, stock, weekday patterns, price changes, or seasonality explain the difference.
If only a before-and-after comparison is possible, keep the windows comparable and label the result directional. Do not turn a short sequential result into a permanent universal rule.
5. Measure the complete decision path
| Measure | What it diagnoses |
|---|---|
| Eligible product-page sessions | Defines the population that could experience the placement |
| Star-summary exposure | Checks whether the block was actually visible or rendered in the tested position |
| Star-summary interaction rate | Shows whether shoppers used the compact proof control |
| Full-review destination visits | Tests whether interaction led to deeper evidence |
| Add-to-cart rate | Detects movement at the first commercial commitment |
| Product-page purchase rate | Tracks the final page-level business outcome |
| Mobile layout-regression rate | Captures overlap, wrapping, duplication, or blocked controls found through QA or monitoring |
| Support or usability signals | Captures confusion that aggregate conversion data might hide |
Do not choose the winner from widget clicks alone. A placement can increase curiosity while distracting from product selection, or reduce clicks while making the summary easier to understand at a glance.
6. Predeclare the decision and rollback rules
Before launch, record what would cause the merchant to keep, reject, or continue testing the treatment. Useful rollback conditions include a broken mobile template, duplicated ratings, a failed review destination, interference with variants or Add to cart, or a commercial decline beyond the store’s accepted tolerance.
The tolerance should come from the store’s baseline, traffic, economics, and risk appetite. This article does not invent a universal lift, duration, or sample-size threshold.
Decide whether Loox fits the placement job
Loox is a practical fit when the merchant wants a configurable product star summary, uses a Shopify theme section that accepts the app block, and can keep the proof attached to the correct product. Its documented controls make it possible to preserve a compact baseline and change location through the theme editor.
Loox is not the answer to every placement problem. Hold the install or move when the product has no credible review evidence, another system already owns the rating summary, the theme cannot expose a valid block position, or the merchant needs to rewrite code without a safe preview and rollback path.
If you are still evaluating the broader collection, display, migration, and automation capabilities—not just placement—read the ShopSideK Loox review before changing the storefront.
For a merchant who passes the review-quality, theme-compatibility, and measurement checks, start with the simplest valid position and earn each additional customization through evidence.
Start Your 30-Day Free Trial with Loox
Frequently asked questions
Should Shopify product ratings go above or below the price?
Start above the price, directly below the product title or between title and pricing. Test a near-price position only when the current buy-box order creates a specific, measurable problem. Do not assume proximity to price automatically improves conversion.
Should star ratings be placed next to Add to cart?
Only as a treatment worth testing. A pre-add-to-cart position can reconnect proof with the purchase decision, but it can also interrupt variants, subscriptions, quantity controls, or mobile access to the button.
Should the star summary show the review count?
Yes, when the widget supports it. The count gives shoppers context for the average and helps distinguish a rating backed by a few reviews from one backed by a substantial body of evidence.
What should happen when a shopper clicks the stars?
The interaction should open a useful, tested path to relevant reviews. Loox can be configured to open its Floating Reviews Widget when the rating icons are clicked. Verify the actual configuration rather than assuming the behavior.
Can every Shopify theme move the Loox block anywhere?
No. Shopify app-block availability depends on theme and section compatibility. A block cannot be moved into an incompatible section through the editor, so validate the intended zones on every important product template before planning the experiment.
Should products with no reviews show empty stars?
That is a separate proof-policy decision. Loox provides an empty-star setting, but switching it during a placement test changes which products display the widget. Keep the current empty-state rule fixed and test it separately if needed.
How long should a placement test run?
There is no universal duration. It depends on eligible traffic, baseline conversion, business cycles, detectable effect, and risk tolerance. Prefer concurrent assignment and a predeclared analysis plan; label small or sequential comparisons directional.
Put proof where shoppers can use it—and prove the move
The under-title or title-to-price position is the strongest starting default because it introduces product-specific proof early and keeps the evidence clearly attached to the product. Move it closer to price or buy controls only when the current architecture creates an observable problem and the alternative remains clear on mobile.
The disciplined decision is not “stars always belong near Add to cart.” It is: map the buy box, preserve the meaning of the rating, test one placement change, measure the full purchase path, and roll back when the treatment creates more friction than confidence.
