On this page
Most merchants install a size recommendation widget and never touch its placement again. That's a mistake: where the widget sits on the product page determines whether shoppers actually click it, and a widget nobody clicks can't reduce returns, no matter how accurate its algorithm is.
Why Placement Matters More Than Merchants Think
A size recommendation widget only creates value at the moment of interaction. If it's buried below a long description or hidden inside an accordion, most shoppers never see it before they've already guessed a size and moved on. Placement is not a cosmetic decision — it's the primary lever for adoption rate, and adoption rate is the primary lever for return-rate reduction.
Teams that treat the widget as "just another PDP element" tend to drop it wherever there's leftover space. Teams that treat it as a conversion tool test its position the same way they'd test a call-to-action button.
The Three Common Placement Options
Option 1: Hero Placement (Above the Fold, Near the Product Image)
Placing the widget prominently near the top of the page, close to the hero image or title, maximizes visibility. Shoppers see it before they've formed an opinion about sizing, which is exactly when a recommendation is most useful.
The tradeoff: hero placement competes for attention with the product photography and price, and on image-heavy PDPs it can feel intrusive if not designed carefully.
Option 2: Near the Size Selector
This is the most common placement, and for good reason — it meets the shopper at the exact moment they're making the sizing decision. When someone opens the size dropdown, a "Find My Size" prompt right next to it has obvious relevance and low friction.
The risk here is timing: some shoppers select a size out of habit before noticing the widget, so it can be seen but not used.
Option 3: Sticky Bar (Persistent Across Scroll)
A sticky bar keeps the size recommendation prompt visible as the shopper scrolls through images, description, and reviews. It never disappears, so it catches shoppers regardless of when they decide to check their size — early skimmers and late deliberators alike.
Sticky bars require careful mobile design since screen real estate is limited, but on mobile-heavy storefronts they often outperform static placements simply because they're always reachable.
How Each Placement Changes Adoption Rate
| Placement | Visibility | Typical Adoption Behavior | Best For |
|---|---|---|---|
| Hero (above the fold) | Highest initial visibility | Strong first impression, some tune-out on repeat visits | New-visitor-heavy traffic, brand-led stores |
| Near size selector | Contextually relevant | High intent-to-click when seen, but easy to miss | Stores where sizing is the #1 pre-purchase question |
| Sticky bar | Persistent across the session | Highest cumulative click rate over a session | Mobile-first storefronts, long PDPs |
Research on product-page CRO consistently shows that above-the-fold interactive elements convert attention into action far more reliably than elements requiring scroll — some UX benchmark studies put the engagement lift from above-the-fold placement at roughly 30% compared to below-the-fold equivalents, which tracks with what merchants running a size recommendation widget typically report after moving the prompt higher on the page. For a broader look at how visibility research is conducted, see NRF and general conversion research from Shopify's enterprise blog.
A Practical Testing Framework
Start With Near-Size-Selector, Then Test Sticky
If you're deploying a widget for the first time, start with placement near the size selector — it has the clearest intent match and the lowest design risk. Once you have a baseline adoption rate, run a two-week A/B test comparing it against a sticky bar variant. Track click-through rate on the widget itself, not just downstream conversion, since that's the metric placement directly controls.
Segment by Device
Desktop and mobile shoppers behave differently. On desktop, hero and near-selector placements perform comparably because the whole page is often visible without scrolling. On mobile, sticky bars tend to win by a wide margin because scrolling past a static prompt is so easy. If your traffic is mobile-majority, weight your test accordingly.
Don't Confuse the Widget Type With the Placement Decision
Placement decisions are independent of whether you're running a full size recommendation engine or a simpler size chart. If you're still deciding between the two, it's worth reading size chart vs. size recommendation before you invest time optimizing placement for the wrong tool.
Common Placement Mistakes
- Hiding the widget inside a tab or accordion that requires an extra click just to see it exists.
- Placing it below reviews or shipping information, where shoppers have already left the sizing decision behind.
- Using generic microcopy ("Size Guide") that doesn't signal a personalized recommendation, which suppresses click-through even in a good position.
- Running the widget only on desktop layouts and forgetting mobile placement entirely, despite mobile often representing the majority of PDP traffic.
If you're still evaluating vendors rather than optimizing an existing install, placement flexibility itself should be a selection criterion — see how to choose a size recommendation solution for the fuller checklist.
Frequently Asked Questions
Does widget placement really affect return rates?
Indirectly, yes. Placement affects how many shoppers click the widget, and adoption rate is the strongest predictor of whether the recommendation influences the final purchase. A highly accurate widget that nobody clicks has zero effect on returns, so placement is effectively a multiplier on the widget's underlying accuracy.
Should the widget replace the size chart or sit alongside it?
Most merchants see better results running the widget alongside a traditional size chart rather than replacing it outright. Some shoppers still prefer to self-select using measurements, so keeping both available and placing the recommendation prompt closer to the primary decision point tends to lift overall engagement without removing a familiar option.
How long should I test a new placement before deciding?
Two to four weeks is typically enough to get a statistically meaningful read, assuming your PDP gets steady traffic. Shorter tests are vulnerable to day-of-week and promotional noise, and testing across at least one full pricing or marketing cycle helps confirm the result isn't an artifact of a specific campaign.
