How we rank
A rank is an argument. Here is ours, in the open, so you can disagree with the weights instead of guessing at an advertiser.
55% · Editorial score
Daily-driver fit, the jobs the product actually does, and the failure modes we will not sand off a spec sheet.
25% · Press consensus
Where serious desks landed this cycle (Wirecutter, CNET, RTINGS-class, DPReview, Car and Driver, SoundGuys). We synthesise; we do not scrape their sentences.
10% · Value
Street price versus what you get. A 9.5 that only exists at MSRP can lose to an 8.8 on sale if the job is the same.
10% · Freshness
RSS ingest every 30 minutes. A launch, a leak, or a safety notice can move notes the same day. It will not buy first place.
Independence. Brands cannot pay to appear on a list or to move a number. We do not buy search ads or paid traffic. They can buy display inventory on /advertise, marked as advertising, kept off the ranking templates.
Notes. One original article a week that is not a ranking lives on /notes. Each note answers a job (doorbell without a plan, light Windows laptop, coding seat if you already pay ChatGPT) and links hard into the matching Top 10. The newsroom is other desks' RSS — a citation tool, not a traffic play by itself.
Experience. Google's E-E-A-T bar wants first-hand photos. Each ranking has a photo well on #1. When a still exists it is a real desk/porch/wrist shot, never an AI product render. Until then we label the rank as editorial composite. Drop files at public/photos/[list-slug]/[product-slug].jpg and they appear on the next deploy.
Bots. Publisher RSS is pulled every 30 minutes on the newsroom. A daily cron counts mentions against ranked names and writes data/signals.json. Optional Keepa / Amazon PA-API keys plug in for price history when you have them. We do not scrape Amazon HTML. Creator videos are linked out — we do not host YouTube or TikTok files.
