Skip to content

Methodology

How we pick

The whole ranking method, in enough detail that you could rerun it with the same spec sheets and get our numbers back. That is the point of publishing it.

Last reviewed

The short version

Every product is scored 0 to 10 on five metrics with fixed weights — fit 30%, capacity 20%, documentation 20%, build 20%, value 10% — and the overall figure is the weighted mean, computed in code rather than entered by hand. Products without a complete published dimensional specification are not eligible at all.

The disqualifier, before anything is scored

A product with no published dimensional specification cannot be a pick on this site. Not a low score — not eligible. The entire value here is dimensional accuracy, and recommending something we cannot measure would contradict the premise of every other page.

That rule does real work: it is why the 30 products in our registry are the ones they are, and why several popular models that publish only a headline width do not appear anywhere.

The five metrics

The rubric, with weights
MetricWeightWhat it measures
Fit30%Usable storage per inch of floor depth and wall width, and how tight a space it still works in.
Capacity20%Published pair count and compartment sizes, checked against real shoe lengths rather than taken at face value.
Documentation20%How completely the manufacturer publishes its own figures — internal depths and load ratings, not just the outside box.
Build20%Published materials and stated load ratings. What the maker commits to in writing, not how it feels.
Value10%Capacity and published build relative to what this category normally asks for the same footprint.
The overall score is the weighted mean of these five, rounded to one decimal place. It is computed by lib/score.ts, not typed in per product, so it cannot drift from the metrics it claims to summarize.

Fit carries the largest weight because it is the constraint this reader actually has. In a hallway at the 36-inch code minimum, every inch of furniture depth comes off the walkway permanently — which is why an 11-inch steel bench can finish above a handsomer 18-inch one.

Documentation is in the rubric because it is the one quality difference a reader can verify without owning anything. One maker publishes each cubby's internal size to a quarter inch; another publishes no weight capacity at all for a product it sells as a bench. That is a real difference in what you can plan around, and it deserves to move the score.

What we refuse to score

Durability, comfort, how a bench feels to sit on, how a drawer runs after a year. We have not handled these products, so scoring any of it would be an invention dressed as a measurement.

That is a genuine limitation and we would rather state it than paper over it. If what you need is a first-hand account of how a cushion wears, this site does not have one and does not claim to.

Why the score is never marked up as review schema

The number you see on a product card is ordinary page content and never appears in this site's structured data. Marking an editorial score up as a review rating would tell Google we performed a first-hand evaluation, which is the opposite of what the page tells you.

For the same reason the score is shown as pips rather than stars. Stars are the visual grammar of a customer review, and this is not one.

How constrained roundups are ranked

A page like narrow shoe cabinets filters the pool to a stated, checkable constraint — 10 inches of depth or less — and then ranks by the same rubric with no special cases. A ranking rule that changes per page is a ranking rule nobody can reproduce.

That occasionally means the winner of a hub roundup also tops its constrained page. When it does we say so on the page rather than reshuffling to make two pages look different. If the best cabinet overall is also the best narrow one, that is the answer.

Where prices come from

The live price layer, or nowhere. No price is ever typed into copy, and where the layer has no current figure the page says check price on Amazon rather than showing a number we cannot stand behind at the moment you read it.

Prices carry a visible as-of date when they render, and anything older than 48 hours disappears on its own rather than sitting there looking current.

How often this is reviewed

  • Prices: refreshed automatically, with the verification date shown.
  • Top-pick availability: checked monthly, and discontinued picks are replaced rather than left.
  • Full specification re-verification: quarterly across every roundup.
  • Dates: updated only where the content actually changed. A refreshed price is not a content change.

Read next

Where to go from here