How we review

Evidence first. Recommendation second.

Our v1 method is deliberately narrow: official public sources, visible tradeoffs, category-specific judgment, and a dated fact check.

Review status

Every review on Extension Reviewer reflects verified product specifications, Chrome Web Store disclosures, and first-party developer documentation, evaluated against category alternatives.

Sources we prioritize

  1. Official Chrome Web Store listing for rating, rating count, public users, current version, update date, publisher identity, and disclosed data categories.
  2. Official developer site, help center, pricing page, and privacy policy for product claims and plan limits.
  3. Public policy or platform documentation when a claim depends on Chrome, search, advertising, or disclosure rules.

How we form a verdict

We compare the job the extension is built to do, publicly documented feature coverage, pricing, update recency, scale of the public rating sample, permissions and data disclosures, and credible alternatives. A 4.9 store rating from a small sample is not treated as stronger evidence than a mature product’s larger history.

Verdicts and signals

Every review carries one of three verdicts. Recommended: the public record supports choosing it for its core job. Worth it, with caveats: genuinely useful, but something specific belongs in the decision—and the review names that caveat next to the badge. Not our pick: we found a better option for the same job, or the public record is too thin to stand behind. Alongside the verdict, each review publishes four signals read straight off the store listing—adoption, rating in category context, upkeep, and cost—so you can see the evidence the judgment was made from. Verdicts are deliberately not numeric: v1 is not hands-on benchmarked, and precise scores would imply testing we have not done. The thresholds behind every signal are published in full on how we rate.

How “best” works

“Best” always has a use case attached. Grammarly is our proofreading recommendation; QuillBot is better for dedicated paraphrasing; Zotero Connector is the research-capture pick; Duey.ai is the focused free-typer pick. No product is “best” at everything, and every ranked guide names the job each pick wins.

Conflicts of interest

Extension Reviewer has no affiliation with any extension developer covered on this site. Products made, funded, or sold by anyone involved in running this site are excluded from coverage.

The same record fields and source requirements apply to every extension we cover. If a conflict of interest ever arises around a covered product, we remove the coverage rather than annotate around it.

Real dates only

Every published, verified, and fact-checked date on this site is the actual date the work happened. We never backdate articles or simulate archive history. The updates log records changes as they land.

Corrections and refreshes

Each article shows a fact-check date and links its sources. Product facts change quickly; readers should check the store and developer pages before purchasing. V1 has no public contact form or email. A correction channel can be added in a later release with the privacy policy updated at the same time.

See also how we rate and our editorial policy.