Ars Technica PREarn The Story
Engineers Trust.

What Ars Technica is

Ars Technica was launched in 1998 by Ken Fisher and Jon Stokes. The name is Latin — roughly, the art of technology — and the editorial position has stayed close to that idea for more than twenty-five years: explain how the thing works, not merely that it exists. Condé Nast acquired Ars Technica in 2008, and it has operated inside that group since, alongside titles such as WIRED.

Two things about the readership matter more than the traffic figure. The first is composition: Ars Technica is read by software engineers, systems administrators, security researchers, scientists, hardware designers and technically literate policy people. The second is tolerance for length. This is a publication with a tradition of extremely long reviews and explainers — an 18,000-word iPad review is part of its folklore — and its audience reads them. A reader who finishes a 6,000-word analysis of your architecture is a different kind of reader from one who skims a launch item.

A UK edition launched in 2015 and built a substantial British readership within its first year. Paid subscriptions, branded Ars Pro, have existed since 2001 and strip advertising out entirely for those subscribers — which tells you something about how the publication views the relationship between commercial pressure and editorial trust.

What Ars Technica actually covers

Pitching well starts with knowing which desk a story belongs to. Ars Technica is not a general technology-news site with one inbox; it has distinct areas with distinct standards.

If your story does not sit clearly inside one of those, the honest conclusion is usually that Ars Technica is the wrong title — not that the pitch needs rewriting.

Why you cannot buy Ars Technica coverage

This is the part most pages on this subject avoid, so let us be direct. Editorial coverage in Ars Technica is not purchasable. There is no rate for a news item, no paid contributor route into the newsroom, and no agency — this one included — that can guarantee a piece will run. Anyone who tells you otherwise is either describing an advertising product and calling it editorial, or selling something that will not be delivered.

Condé Nast does sell advertising and does run clearly marked commercial formats. Those are legitimate products, but they are advertising: labelled as such, treated as such by readers, and treated as such by search engines. They are not the thing people mean when they say they want to be in Ars Technica.

What earns Ars Technica coverage

Across the desks, the pattern is consistent: the writer needs material they cannot obtain from anyone else, in a form they can verify.

Original data at meaningful scale

Not a survey of 500 people commissioned to produce a headline. Data that exists because of what your company does — anonymised telemetry, incident statistics, latency measurements across a real network, adoption figures with methodology attached. Offer the dataset, not the conclusion.

Security research

A genuine vulnerability, responsibly disclosed, with a technical write-up, proof of concept where appropriate, a disclosure timeline and vendor response. This is one of the few areas where a smaller company can reach this readership on merit alone.

Technical firsts, honestly framed

Something that has not been done before, with an explanation of how it works and what its limits are. Stating the limitations improves the odds rather than harming them, because it signals you are not overselling.

Documents

Court filings, regulatory submissions, standards drafts, contracts, internal policy. Primary sources are the raw material of the policy desk.

Access and expertise

An engineer who can explain a hard problem clearly and answer follow-up questions without a communications minder rewriting the answers. Real expertise, made genuinely available, is a durable asset.

What gets ignored

How to pitch Ars Technica: the Ars Technica PR method

The mechanics are simple; the discipline is not. Ars Technica lists a press address, and its contact page is public. Getting the address is the easy part.

1. Identify the desk and the writer. Read the last twenty pieces in your area. Note who wrote them and what they seem to find interesting. A pitch to the wrong desk is a deleted pitch.
2. Lead with the finding. First sentence states what is new and verifiable. Not your company name, not your funding, not an adjective.
3. Attach the evidence. The dataset, the technical paper, the disclosure timeline, the document. Not a link to a landing page.
4. Name the limits. Say what the finding does not show. Writers at this level will find the caveats anyway; supplying them earns trust.
5. Offer the engineer, not the executive. Direct access to the person who did the work, with authority to answer technical questions.
6. Keep it under 200 words. If it needs more, the story is not clear enough yet.
7. Accept silence. One follow-up after several working days. No more.

Are you ready? An honest test

Before spending anything on this, answer these. If you cannot answer at least two with a firm yes, Ars Technica is not currently reachable and we will tell you so.

• Do you hold data about how something works at scale that nobody outside your company has?
• Have your engineers found something — a vulnerability, a limitation, a surprising behaviour — that other practitioners would want to know?
• Can you name a specific technical claim that a sceptical reader could test?
• Would you let a journalist speak to your engineers without a script?
• Are you willing to have the weaknesses covered alongside the strengths?

That last question is the one that ends most conversations. Independent coverage is independent. A piece may conclude that your approach has real trade-offs. If that outcome is unacceptable internally, earned media at this level is the wrong instrument.

The UK angle

For British companies there is a practical advantage worth using. Ars Technica has run a UK edition since 2015 and covers European technology policy closely — online safety regulation, competition enforcement, data protection, telecoms and semiconductor policy all sit squarely in its territory. A UK or EU regulatory angle on a technical story is frequently the difference between a pitch that lands and one that does not, because it gives the policy desk a hook that United States coverage will not already have exhausted.

The same is true of British academic and research institutions. A UK university spin-out with published research, a national laboratory result, or a company operating inside a specific British regulatory regime has something structurally distinctive to offer. That is a stronger position than a company competing for attention on generic product news.

Ars Technica and AI search visibility

One development makes technology-press coverage worth more than it was a few years ago. Condé Nast, Ars Technica’s owner, entered a content partnership with OpenAI in 2024, licensing its titles for use in AI systems. Alongside that, assistants such as ChatGPT, Google’s AI overviews, Perplexity and Claude lean heavily on established technology publications when answering questions about products, companies and technical claims.

The practical consequence: a piece in Ars Technica is not only read by its own audience. It becomes part of the material AI assistants draw on when somebody asks what your company does, whether your technology works, or who the credible providers in your category are. That is a longer-lived asset than a traffic spike, and it is a reason to care about accuracy in the coverage rather than volume of it.

It also raises the cost of the alternative. Low-quality placements on sites that assistants do not trust contribute nothing to this, and coverage that misstates what you do can propagate into AI answers and stay there.

If Ars Technica is not the right title

Being told a target is unrealistic is more useful than being sold a campaign against it. Where a story does not meet the bar, these routes are frequently better matched, and we would rather place you well somewhere appropriate than badly nowhere.

Our wider media list sets out the categories we work across, and our consumer technology and business-to-business pages cover adjacent programmes in more detail.

Where our work stops

Setting this out plainly is part of the service. We build the story, identify the right desks, prepare the technical material so it survives scrutiny, and manage the approach. We agree every named title with you before anything is sent.

What we do not do: guarantee that Ars Technica or any independent newsroom will publish; pay a journalist or a publication for editorial coverage; write copy that overstates a technical claim; or present advertising as though it were earned coverage. If the honest assessment is that your story will not clear the bar, we say so before you commit, rather than after.

Questions people ask about Ars Technica PR