Why we bother writing this down

Any site that compares products has an incentive to sound more certain than it is. Confident writing gets read, gets shared, and sends people to retailers. A code of ethics is our way of setting limits on that pull before it starts shaping what we publish, quietly, one small compromise at a time.

What follows isn't a list of aspirations we hope to grow into. Each principle describes how a comparison on this site is supposed to be written today, and each is specific enough that you can open an article and check whether we followed it. When we don't, the last section explains how to tell us.

A short note on scope: this code covers the comparisons, guides and supporting pages on ranking-hours.uz. It sits alongside our Independence and Funding pages, which deal with money and outside influence in more detail, and our Methodology page, which explains the research itself.

One more thing before the principles. You don't have to take this page on trust. The whole point of writing standards down is that they become testable. Pick any comparison on the site, read it against the ten principles below, and see whether it holds up. If it doesn't, that's useful information for us and for you.

1 Claims should match the evidence

A comparison earns trust by being exactly as confident as its sources allow, and no more. If the only evidence for a battery figure is the manufacturer's own claim, the article should sound like it's relaying a claim, not reporting a measurement.

This sounds obvious, but it's the principle most often broken in product writing, usually without anyone meaning to. A sentence starts as "the manufacturer says" and ends up, a few edits later, as a flat statement of fact.

  • Every statement about performance should trace back to a source we could name if asked: a spec sheet, a published test, or a pattern in owner reports.
  • When evidence is thin, as it is for a product released a few weeks ago, the article says so instead of writing around the gap.
  • Words like "dramatically" or "far better" are kept for differences that are actually large. A two percent gap in a performance score is described as a two percent gap.
  • Where we're inferring rather than reporting, the wording shows it: "likely", "we'd expect", "reports suggest".

2 Be honest about how we know things

Readers assume that a site comparing two laptops has held both. Often that isn't the case, and pretending otherwise would be the fastest way to lose the trust this whole site depends on.

So we draw a plain line between three kinds of knowledge: what a manufacturer publishes, what independent testers have measured, and what someone on our side has personally used. Only the third gets described as our own experience, and only when it's true.

  • We don't describe a product as tested, used or lived with unless someone here has actually done that.
  • Manufacturer specifications are attributed to the manufacturer. A copied spec table is never presented as original research.
  • Product images are there to help you recognise what's being discussed. A press photo isn't passed off as a picture of a unit we handled.
  • When we can't verify something, the limitation is stated in the article rather than covered with invented detail.

3 Keep facts and judgment apart

A specification can be checked against a datasheet. A recommendation can't, because it depends on what you care about. Mixing the two makes a comparison harder to trust, since a reader can't tell which sentences are verifiable and which are opinion.

In practice this means each article separates what the products are from what we think of them, and ties every opinion to a priority you can accept or reject.

  • Specifications and prices sit in their own sections, clearly separate from the conclusions drawn from them.
  • "Best" is never left hanging. It's always "best for" something: a small budget, long battery life, a crowded desk.
  • When two products suit different kinds of buyers, we say that instead of forcing a single winner onto everyone.
  • If the honest verdict is "these are close", the article says it's close.

4 Money doesn't get a vote

This site earns money through advertising and, on some pages, affiliate commissions. That's a real conflict of interest, and the only responsible response is to be open about it and to build the writing process so the money can't reach the conclusions.

The order of work matters most here. A comparison is researched and its conclusion is settled first. Only afterwards is a retailer link added, pointing to wherever the product we already chose can be bought. Our Affiliate Disclosure explains this in full.

  • A commission rate never decides which product wins, how high it's rated, or whether a flaw gets mentioned.
  • We don't take payment to change, soften or remove a conclusion.
  • We don't accept gifts or free products in exchange for coverage or a favourable verdict.
  • If a piece of content were ever sponsored, it would be labelled as such on the page itself, not tucked into a policy document.

5 Disclose conflicts of interest

Money isn't the only thing that can tilt a comparison. A writer who once worked for a phone maker, or who owns shares in a car company, will have a harder time being even-handed about it, however hard they try.

  • Anyone working on a comparison who has a personal or financial connection to one of the brands involved should say so.
  • Depending on how close the connection is, that person either steps away from the comparison or the connection is disclosed in the article.
  • Owning a product ourselves isn't a conflict, but it's mentioned when it's relevant, because it can colour how a product feels to us.

6 Treat brands and products fairly

Two products in a comparison should be judged against the same yardstick. It's easy to be strict about the one you're less fond of and generous about the other without noticing.

  • Both sides of a comparison are measured on the same criteria, in the same order, using the same kind of evidence where it exists.
  • We don't set a budget product against a flagship and then act surprised when the flagship wins.
  • Criticism has to rest on something specific. "Feels cheap" needs a reason; "the hinge flexes noticeably" is a reason.
  • If a company shows us that we got a fact wrong, we correct it, whether or not the correction helps them. A disagreement about the conclusion is a different matter and doesn't trigger a rewrite on its own.

7 Fix mistakes in the open

We'll get things wrong. Specifications get revised after launch, prices move, and sometimes we simply misread a source. What counts is what happens next.

Corrections are made in the article itself, not by publishing a new page and leaving the wrong one findable elsewhere on the site. Our Corrections page describes the process from the reader's side.

  • A reported error is checked against the original source before anything is changed.
  • Genuine errors are fixed, whoever reported them and whichever way the fix cuts.
  • We aim to acknowledge correction reports within a few business days, even when the full fix takes longer.
  • Where we can, we tell the person who reported it once the change is made.

8 Write plainly, without hype

Shopping pages are full of pressure: countdown timers, "only three left", "you'll regret waiting". None of that helps you choose well, and none of it belongs here.

  • No manufactured urgency. If a price is worth acting on, it's worth acting on without a fake deadline.
  • Headlines describe what the article actually contains, and don't promise a verdict the page doesn't deliver.
  • We don't invent reader reviews, testimonials or comments, and we don't quote anyone we can't point to.
  • Jargon gets explained the first time it appears, so a comparison doesn't require you to already know the answer.

9 Keep content current, or say when it isn't

A comparison of two phones is only useful while both are still on sale. Products get replaced, discounted and discontinued faster than any small team can rewrite every page.

  • When a product in a comparison is discontinued or superseded, we update the article or add a clear note near the top.
  • Prices in an article are pointers to the general price range. They aren't quotes, and you should confirm the current figure with the retailer.
  • Older pages are revisited periodically, not only when someone complains.
  • Readers are encouraged to check the model details in an article against the product they're actually looking at, since a near-identical trim can differ in an important way.
  • An article that can no longer be brought up to standard, because the product is long gone and nobody is comparing it any more, is retired instead of being left to mislead.

10 Respect the people who read and write to us

You came here to compare products, not to become a data point. What we collect is limited, and what you send us on purpose is used for the purpose you sent it.

  • A message sent through the Contact page is used to answer that message and to investigate it if it's a correction. It isn't added to a marketing list.
  • We explain what data is collected, and by whom, on the Privacy Policy page, in language meant to be read.
  • Readers who disagree with a conclusion are treated as useful, not as a nuisance. The best corrections often begin as complaints.
  • Personal details you share, such as a name or an email address, are never published alongside a correction or quoted on the site without asking you first.
  • If you ask us to delete a message you sent, we'll do that unless there's a real reason to keep it, and we'll tell you what that reason is.

Things we won't do, even though many sites do

Some practices are so common in product writing that leaving them out is a decision in itself. These are the ones we've deliberately ruled out.

  • Ranking products by commission and presenting the list as a neutral "top ten".
  • Republishing a manufacturer's marketing copy as if it were our own assessment.
  • Writing a glowing review of a product no one on the team has any real basis to judge.
  • Leaving an outdated comparison live with an old price and no note, because it still gets traffic.
  • Deleting a comment or a message because it points out an error we'd rather not admit to.
  • Changing a conclusion after publication for any reason other than new evidence.

The last item deserves a word. Updating a comparison because a product changed, or because someone showed us a better source, is exactly what should happen. Updating it because a brand asked nicely, or because a different retailer now pays more, is not, and it's the reason the wording around corrections in this code is so specific.

Where ethics and business rub against each other

It would be dishonest to pretend this is easy. Running a comparison site costs money: research takes time, hosting isn't free, and good writing isn't a hobby that pays for itself indefinitely. Advertising and affiliate income keep the site free to read. Both create pressure, and pretending that pressure doesn't exist would make this code worthless.

The way through isn't to refuse income. It's to separate the people and steps that decide what's true from the steps that earn money. The conclusion comes first. The link comes second. The ads are chosen by an ad network and not by us, and an ad appearing beside a comparison says nothing about what the comparison concludes.

There are still real grey areas here, and we'd rather name them openly than pretend they don't exist. A retailer that stocks fewer of the products we recommend will get fewer of our links, simply because there's less to link to. A category with weak affiliate programs, like cars, might earn us little, which could in theory make it less attractive to cover. We try not to let that decide what gets written, and the range of categories on the Categories page, including several that earn almost nothing, is the honest evidence of how that plays out.

If we've fallen short of this code

Tell us. Point to the page and the sentence, say which principle you think it breaks, and include a source if you have one. A specific report takes only minutes to check properly; a vague general one takes much, much longer.

We read every report. We can't promise a personal reply to each one, but correction reports are always checked, and a confirmed error is always fixed.

Related pages

This code is one piece of a set. If your question is about money, outside influence or how the research is done, one of these pages is probably the better place to look.

A living document

This code will change as the site itself changes and grows over time. If we take on a new kind of content, or discover that one of these principles is vague enough to be bent, the wording here will be tightened up instead of being quietly ignored or forgotten. We'd rather revise the code than break it.

If you think something is missing, and there's a standard you'd expect a comparison site to meet that isn't listed above, tell us through the Contact page. Some of the sharper points in this document exist because a reader pointed out a gap. We'd also welcome hearing from people who work in the industries we cover, such as engineers, retailers and repair technicians, since they often notice things a spec sheet never shows and a general reader would never think to ask about.