How to read rankings and reviews without being misled

A ranking shows how a set of products compares against the criteria its publisher stated, at the time it was checked. It does not measure your needs, and a single overall number hides the trade-offs that usually decide the choice. Read the criteria, the publisher's disclosure and the dates first, then the order, then user reviews, which need their own reading habits. The video above covers the checks in about 80 seconds; this page explains each one, using the rankings on this site as examples.

What a ranking can and cannot tell you

A ranking is a comparison. Its editor picks the products, picks the criteria, judges each product against them and sorts the results. Every step involves judgment. A ranking can tell you which products deserve a closer look and which one scores higher on the criteria it states. It cannot tell you whether those criteria match your work.

The scores on this site are editorial judgments. They are not benchmarks, user ratings or survey results, as the methodology says in plain terms. A score asks how well a product serves a typical reader of its category, against the criteria the list states, so the question it answers may not be yours. For example, a list that weights free-plan limits heavily will favor products with generous free plans. A reader who needs a free plan gets a good answer from that list, and a reader who needs something else should look at the criteria before trusting the order.

Read the criteria and the best-for labels first

Start with the criteria, then the order. A list that states its criteria lets you check them against your needs. The password managers ranking names five: vault security and encryption model, platform and browser coverage, free plan limits, open-source code and transparency, and sharing and extra features. The e-signature ranking names different ones, including hosting choice and data control, and API and integrations. Someone sending a few contracts a month and a developer who embeds signing in an app should read those lists differently.

The list states its criteria but not how much each one counted, so you cannot recalculate its scores. Write down your own needs before you read the order, decide how much each criterion matters to you, and treat the order as one input. Then read the best-for label before the number. On the password managers list, the top two entries are labelled "Free open-source password manager for most people" and "Paid password manager for families and polished apps". Their scores are 93.5 and 92.0 on a judgment scale. The labels tell you more about the choice than a gap of one and a half points does.

Who publishes it and what they gain

Every ranking has a publisher, and the publisher's income and interests are the first thing to check. Look for sponsored or partner placements, affiliate links (links that pay the publisher when you buy), and products made by the publisher or by its employer. A disclosure should sit where the ranking is, not only in a footer.

The Federal Trade Commission's endorsement guides in the United States say that a material connection must be disclosed when a significant minority of the audience would not expect it, and that the disclosure must communicate the nature of the connection clearly enough for a reader to judge its weight (16 CFR 255.5).

listme.name's own disclosure is a useful example. Some listed products are made by the publisher, by the publisher's employer or by people the publisher works with. Those products carry an asterisk wherever they appear, and the disclosure page names them. They are scored on the same criteria as every other product, and they also receive a small, capped lift when a list is ordered, plus one placement floor per list. The displayed score is always the editorial score, and how we rank gives the exact rule. At the time of writing the site has no advertising, no sponsored placements and no affiliate links. The about page adds that research and drafting use AI tools, and that product facts come from vendors' own pages and public repositories.

Check the dates on the list and on each product

A ranking carries a date, and so does each product entry. Check both. The date on a list is the newest date any of its products was checked, so it does not mean every entry was checked that day. Each product page shows its own "Checked" date, and those are the dates to rely on for price, platforms and features.

Dates matter because software changes. A vendor can add a platform, retire a plan or change its free allowance after a list was checked. For example, if a free plan's limits changed after the last check, the vendor's own pricing page shows the current limits and the list does not. Treat the vendor's page as the final word on cost, and treat the list as a starting point.

Read user reviews for what they leave out

User reviews describe daily use better than a feature table, but they have predictable gaps. The people who write them are a self-selected group: someone who had a strong reaction is more likely to write than someone who was satisfied and carried on. Five-star and one-star reviews often describe a first week or a single bad incident. Middle ratings often explain a specific trade-off in detail, which makes them a good place to start reading.

Skip reviews that give no detail about how the product was used, because nothing in them can be checked. Check which version a review describes. A review of an old release can be accurate and still irrelevant, so compare the date and version against the vendor's changelog. Also check whether a review describes the product you would buy: a review of a mobile app says nothing about the desktop client.

Fake reviews are a separate problem. In the United States, the Federal Trade Commission's rule on consumer reviews makes it an unfair or deceptive practice for a business to write, create or sell a review or testimonial that misrepresents who wrote it or whether the writer used the product (16 CFR 465.2). The rule defines a consumer review as a consumer's evaluation or a purported consumer's evaluation. A review that complies with the rule can still be misleading, so the rule is a floor, not a test of accuracy.

Cross-check a claim against the vendor's documentation

A ranking or review may say that a product works offline, encrypts files or runs on Linux. Each of these is a claim you can check against the vendor's own documentation, which is more precise than a summary. Find the help article that describes the feature, note which platforms and plans it names, and compare the claim with what the vendor says.

For example, if a list says a product has an offline mode, open the offline help article and read the platforms it covers. If the article describes only the desktop app, the offline claim covers only the desktop app, whatever the summary says. How to compare products fairly covers setting up a fair side-by-side comparison, and how to run a trial shows how to test a claim yourself.

Sources

• 16 CFR Part 255: Guides Concerning Use of Endorsements and Testimonials in Advertising, Federal Trade Commission, current eCFR text. Section 255.5 covers disclosure of material connections.
• 16 CFR Part 465: Rule on the Use of Consumer Reviews and Testimonials, Federal Trade Commission, current eCFR text. Section 465.2 covers fake or false reviews.