“We do not take payment for product reviews. Ever.”
That sentence sits in TechRadar’s own published explanation of how it tests and rates, alongside a commitment to tell readers what its reviewers think rather than what advertisers want them to hear. It is worth quoting exactly, because a surprising number of approaches to the site are built on the assumption that it is negotiable. It is not, and sending that kind of approach marks you permanently in a newsroom that remembers.
Which leaves the harder and more interesting question of how to get featured on TechRadar on merit. The answer is unusually mechanical for a media relations question, because the publication has written down most of its process, and reading what it wrote tells you exactly what it needs from you.
Read the Testing Policy as a Requirements Document
TechRadar’s review framework describes a five-star scale with half-star increments, assessment across design, features, usability, performance and value, a stated minimum period of testing before publication, a preference for real-world use over laboratory conditions, and a firm distinction between a hands-on impression and a full review of a finished retail product.
Each of those is a requirement you can either satisfy or not, and most pitches fail on one specific clause: the finished retail product. A full, rated review requires a unit that represents what a buyer will receive. Pre-production hardware, engineering samples and review units with known differences from retail can produce a hands-on piece, which is genuinely valuable at launch, but they cannot produce the rated review that most companies are actually asking for.
So the first decision is which of the two you are pitching. Asking for a review when you can only support a hands-on wastes the exchange. Offering a hands-on at launch and a retail unit later for the full review is a coherent plan that a writer can say yes to twice.
The minimum testing period has a consequence too. A unit that lands three days before your launch cannot be reviewed on launch day, and pushing for that produces either a refusal or a thinner piece than you wanted. Count backwards from your date and add margin.
The Five Rules for a Review Unit
Here are the rules that separate a unit which gets reviewed from one that sits in a cupboard.
The first is that it has to be retail-representative, and if it is not, you say so unprompted. A reviewer who discovers a discrepancy mid-test will write about the discrepancy, and that paragraph will outlive your launch.
The second is that it has to be complete. Everything in the retail box, in the retail box. Accessories, cables, documentation, the actual packaging. Reviewers assess unboxing and setup because readers experience them, and a unit arriving in a padded envelope with a loose cable has already lost points on an attribute you did not realise was being scored.
The third is that it has to work out of the box without privileged setup. No pre-configured accounts, no engineer on a call walking them through it, no firmware you flash for them. The review tests what a customer gets, and any assistance you provide is either declined or disclosed, both of which work against you.
The fourth is that it has to arrive with the information a reviewer needs and nothing that wastes their time. Price by market, availability date, full specifications, firmware version, and a named contact for technical questions. Not a brochure, not a brand deck, not a video of your founder.
The fifth is that you let it go. Once a unit ships, you do not ask what the rating will be, you do not ask to see the piece before publication, and you do not offer to clarify unfavourable findings. Each of those requests is a flag, and reviewers discuss senders who make them.
Match the Edition to Your Availability
TechRadar runs multiple regional editions, which is the detail most pitchers miss and the one that quietly determines whether coverage is possible at all.
A product available only in one market cannot be usefully reviewed by an edition serving a market where readers cannot buy it, and a reviewer who likes your product but cannot give readers a price and a link has a problem you created. So establish availability and local pricing before pitching, and pitch the editions where both exist.
This also opens a path people overlook. A smaller regional edition is frequently easier to reach than the largest one, has a genuinely engaged readership, and produces a review you can quote everywhere afterwards. Starting with the market where your availability is strongest and your competition for attention is weakest is a better sequence than aiming at the biggest audience first and getting nothing.
On finding the right person: verify current writers and editors on the site rather than trusting any list. Mastheads at large portfolios move frequently, and reporting around the publication has noted senior editorial appointments in recent years, so a contact from two years ago may no longer hold the beat. Find the last ten reviews in your product category, note who wrote them, and read enough of their work to know what they consistently complain about.
Write the Pitch Like a Spec Sheet With a Reason
The email is short and front-loads the facts a reviewer triages on: what the product is, what is new about it stated as a mechanism rather than a benefit, the price by market, the availability date, and the offer of a retail-representative unit with a date it can ship.
Then one sentence on why a reader would care, which is the only part where you get to argue. Then a link to a press page holding specifications, high-resolution photography and a short unedited video of the product working. Attach nothing.
What to cut: superlatives, award mentions, funding news, comparisons to companies in a different category, and any claim without a measurement behind it. A reviewer’s job is to find out whether claims hold, so a claim you cannot support is an invitation to be tested in public and fail.
One addition that performs better than it should: a short, honest paragraph on what your product is not for. Naming the use case where a competitor is the better choice tells a reviewer that your other claims have been filtered through the same honesty, and it costs you almost nothing because the reviewer will reach that conclusion anyway.
Buying Guides Are the Other Door
There is a second route to how to get featured on TechRadar. Most companies pitch for a review and ignore the format that sends more sustained traffic over a product’s life, which is the buying guide.
A publication like this maintains ranked guides for most consumer categories, updated as new products arrive, and those pages rank persistently in search long after a launch review has stopped earning attention. A product that holds a slot in the relevant guide is being recommended to someone with purchase intent every day, which is a different and usually more valuable thing than a single rated review on launch week.
The route in is the same product, pitched differently. Guides get refreshed on a cycle, and the person maintaining one is deciding whether to swap an incumbent out. What they need is a reason: a category your product wins that the current list handles badly, a price point nothing on the list occupies, or a specific use case the guide’s own framing admits it has not covered. Read the guide carefully, find the gap it concedes, and pitch into that gap rather than asking to be added.
Timing matters differently here too. Launch windows are irrelevant; guide refresh cycles are not. The practical approach is to ask, once, when the guide for your category is next being reviewed, and to offer a unit in advance of that date. That question is easy for a writer to answer and it signals that you understand how the page works.
One caution. Guides are built on tested products, so a slot usually requires a review to have happened first, which means this is a second step rather than a shortcut. Companies that treat the launch review as the goal and then stop are leaving the durable half of the opportunity on the table. The review is the audition. The guide is the job.
What the Relationship Looks Like Over Years
The companies that get covered repeatedly by publications like this one behave consistently in ways that have nothing to do with pitching.
They ship units promptly when asked, including for comparison pieces about competitors where their product may lose. They answer technical questions directly and say when they do not know. They disclose problems before a reviewer finds them, including recalls, firmware issues and specification changes. They never involve the commercial side of a publisher in an editorial conversation, which is the single fastest way to end a relationship at a title that publishes a no-payment policy.
And they are useful in the gaps. A reviewer writing a category explainer needs someone who will explain the engineering honestly, and the company that does that becomes the one quoted, which is coverage that costs nothing and arrives without a pitch. Over a few product cycles this compounds into something no media relations budget buys: a sender whose email gets opened, and a product that gets considered on arrival rather than ignored by default.
When the Review Is Mediocre
Plan for this, because it is the most likely outcome and the point where companies damage relationships that took months to build.
A three-star review is not a failure of the pitch; it is the system working, and the system’s credibility is the reason the review was worth having. The correct response is a short thank-you, a factual correction only if something is actually factually wrong, and nothing else. No complaint to the editor, no escalation to the commercial side of the business, no suggestion that the reviewer misunderstood the product.
If something genuinely is wrong, such as a specification misstated or a unit that turned out to be faulty, raise it once, politely, with evidence, and accept the outcome. Publications correct real errors. They do not revise judgements, and asking them to is how a sender becomes a problem rather than a source.
Then use what you learned. A critical review from a publication that takes no payment is the most honest product feedback you will get at no cost, and the specific complaints are a roadmap. Companies that fix the thing a reviewer criticised and say so in the next cycle get noticeably warmer receptions, because the reviewer can see that someone read it.
Learning how to get featured on TechRadar is mostly learning to meet a documented standard rather than to persuade anyone. The policy is published. The testing requirements are published. The one thing not published is whether your product is good enough, and no amount of pitching changes that answer.