Near the end of almost every press release sits a short sentence that does something the rest of the document carefully avoids: it asks the reader to act. Read the full report. Register for the event. Download the data. That sentence — the call to action, or CTA — is the point where a news document admits it was written for a reason beyond informing. Writers who go searching for guidance on the CTA press release usually find landing-page advice transplanted wholesale into a news format: urgency, scarcity, benefits stacked like sandbags. Some of that advice is harmless. Much of it misunderstands what kind of document a release is.

A call to action inside a release is a component of the document, like the headline, the dateline or the boilerplate: it has a proper place, a proper register and a job it can legitimately do. This article treats it that way. It looks at what a release CTA may honestly ask for, where it belongs, how it should be worded, how the right ask changes with the release’s purpose, and the mistakes that turn a useful signpost into a sales pitch wearing a news costume.

A News Document That Still Asks for Something

The tension is real, and it is better faced than wished away. A press release borrows the forms of journalism: third person, inverted pyramid, facts before interpretation. Its readers — journalists first, the public directly behind them — extend it a limited trust precisely because it observes those forms. A landing page operates under different rules: it exists to persuade, and nobody mistakes it for anything else. When a release starts behaving like a landing page, it spends the trust that made it worth reading, and it usually spends it on a sentence or two at the end.

Yet a release with no next step at all is also a failure of craft. Announcements point beyond themselves almost by nature: there is a report behind the summary, an event behind the announcement, a fuller account behind the statement. The CTA is simply the honest marking of that path — the sentence that tells a reader who wants more exactly where more is kept. The working test is simple: a legitimate release CTA completes the story for the reader. An illegitimate one interrupts the story to sell something adjacent to it.

What a Release CTA Can Legitimately Ask

The legitimate asks share a quality: each one gives the reader more of what the release itself is about. The commonest is the invitation to read the full document behind the announcement — the complete report, study, findings or decision of which the release is a summary. Close behind come the resource asks: download the data tables, the technical appendix, the image library or the full text of a speech. And the attendance ask: register for the event, the briefing, the webcast or the opening that the release announces. Each of these extends the reader’s access to the story rather than diverting the reader out of it.

Two further asks are legitimate when they are the announcement’s own substance. A recruitment release can ask the reader to read the full role description and apply; that is not a diversion, it is the point of the document. And any release can close with the standing invitation aimed at journalists: contact the named person for comment, for an interview, or for the underlying material. What the list does not include is pressure: no countdowns, no expiring discounts, no invitations to buy dressed up as news. The moment the ask stops serving the story, it stops belonging in the document.

Where the CTA Belongs

Position is a matter of manners as much as of effectiveness. The news comes first and must be complete before anything is asked of the reader, so the CTA’s natural home is the end of the body: after the final fact, before the boilerplate and the contact block round the document off. Placed there, it reads as a signpost at the end of a road the reader has already travelled. Moved into the headline or the opening paragraph, it reads as an ambush — the document asking for something before it has given anything — and experienced editors treat it accordingly. The document’s full anatomy, for reference, is set out in this blog’s complete guide to formatting a press release.

There is one respectable exception. When the resource is the story — a published report, an open dataset, a consultation document — a single link to it may sit early, immediately after the lead, because withholding it would make the release less useful to the journalist working from it. That is a service to the reader, not a second CTA: the closing ask should still be the document’s main one, and it should point the same way. One document, one destination, mentioned at most twice.

Wording the Ask

A release CTA is a sentence, not a slogan, and it should be written with the same care as the lead. Start with the verb, because the verb is the ask: read, register, download, apply, attend. Name the object specifically — “the full report, including the regional breakdowns” persuades where “learn more” merely waves. Keep the destination honest: a reader who follows the sentence should find exactly what it described, in the form described, without a further maze of gates. And keep the whole thing short enough to survive being read once, at speed, by someone deciding whether the story is worth their morning.

What to leave out matters more. No clickbait constructions, no curiosity gaps, no teasing of any kind: a release that withholds to provoke is a release that will not be trusted twice. No manufactured urgency — an event has a real date and a report does not expire, so neither needs a countdown. No superlatives about the thing being offered, and no benefit claims the linked page cannot cash. The register to aim for is the register of the rest of the document: the plain, verifiable tone of a news page, in which a calm invitation outperforms a shout precisely because everything around it is calm.

CTA Types by Release Purpose

The right ask follows from what the release is for. An event announcement asks for attendance, and its CTA is registration: a link to the booking page, with the practical facts — date, place, cost if any — already stated in the body, so the click is a confirmation rather than a fact-finding mission. A launch release asks the reader to look closer: to view the full specifications, the documentation, the availability details on the product page. The ask is inspection, not instant purchase, and wording it as inspection keeps it inside the news register — trade readers in particular expect to examine before they commit.

A research or report release asks for the document itself: read or download the full findings, because the release can only carry the headlines of the evidence. A recruitment release asks for applications, and points to the full description and the application route. The delicate case is the crisis-adjacent release — a service failure, a safety notice, a disruption. There the CTA narrows to pure service: check the dedicated updates page, use the dedicated contact route, follow the specific instruction. Its wording must be plainer than plain, stripped of anything that smells of marketing, because the reader on the other end may be worried, inconvenienced or worse, and the document’s job is to help, not to harvest.

Worked Examples, Labelled as Illustrations

The examples below are invented for illustration. The companies are generic, the releases imaginary; what is real is the shape of the sentences and where each sits in its document.

A regional logistics company publishes its annual review of delivery times. The release carries the headline findings, and closes: “The full review, including the regional data tables and methodology, is available to download from the company’s reports page.” The ask names the object, the contents and the destination, and asks for nothing else.

A city arts festival announces its programme. After the dates, the venues and the headline events are stated in the body, the closing line reads: “Tickets for all events can be booked through the festival box office, in person and online.” No urgency, no exhortation — the facts were the persuasion.

A water utility issues a notice about planned overnight works that will interrupt supply in two districts. The CTA is the plainest sentence in the document: “A street-by-street schedule of the interruptions, and the arrangements for households that need support, are on the works update page.” In a document of this kind, clarity is the whole of the craft.

A software company launches a records-management tool for clinics. The release describes what the tool does and when it ships; the closing ask is: “Full specifications, pricing bands and implementation notes are on the product page.” The reader is invited to inspect, not ambushed into a trial.

Writing for Two Audiences at Once

Every release CTA is read by two audiences with different intentions. The journalist reads it as a tool: is there more material here, and can I get it quickly? The end reader — who now commonly meets the release directly, on the issuer’s own newsroom page or republished — reads it as the way onward: what do I do with this information? A well-built CTA serves both without modification, because both want the same thing: the fuller version of the story, honestly labelled.

The complication is mechanical. When outlets republish or adapt a release, its links are kept, stripped or rewritten unpredictably: one newsroom preserves the registration link, another publishes the text bare, a third links a phrase of its own choosing. The writer controls none of that, and the only sound response is structural — the CTA must never be the sole carrier of information the release needs. If the event’s date, the report’s existence or the deadline for applications matters, it belongs in the body, in words. A release stripped of every link should still be a complete and usable document.

Measuring a CTA Honestly

Measurement is where this subject attracts its most confident nonsense, so it deserves plain speaking. What can honestly be counted is activity on properties the issuer controls: visits to the release’s page in its own newsroom, downloads of the resource the CTA names, registrations that arrive through the release’s own link. Those numbers describe what readers of that copy did. They say nothing directly about the far larger audience that met the story through coverage, where the link may or may not have survived — and any figure claiming to capture that audience’s behaviour should be treated as a guess wearing a lab coat.

It follows that there is no honest universal benchmark for what a release CTA should achieve, and writers should distrust anyone quoting standard conversion percentages for press releases: the figure cannot survive contact with the variety of releases, audiences and republication paths involved. The meaningful comparison is internal — this release against the same organisation’s previous releases of the same kind. One clarification belongs here too: a CTA is a service to the reader, not a device for search engines or link schemes, and wording it for any purpose other than the reader’s next step corrupts it.

Common CTA Mistakes

The commonest mistake is competition: a release that asks the reader to download the report, register for the event, follow the organisation, subscribe to the newsletter and contact the office has asked for nothing, because a reader offered five doors tends to choose none of them. Choose the one action the announcement actually exists to enable, and let the rest go. The second mistake is smuggled sales copy — the closing paragraph that suddenly switches into brochure register, all benefits and exclamation. It does not merely fail; it retrospectively contaminates the news above it, teaching the reader to discount the whole document.

The third mistake is the promise the destination cannot keep: the CTA that offers full data and links to a summary, or announces registration and links to a page that demands an email address before revealing the date. Each such disappointment is charged to the issuer’s account, not the page’s. The fourth is burial — the ask tucked inside the boilerplate or appended after the contact block, where it reads as an afterthought and functions as one. And the fifth is repetition: the same ask in the subheading, the body and the close, which converts a signpost into a nag and a news document into a leaflet.

The One-Sentence Test

Before any release goes out, its CTA deserves the same ten seconds of scrutiny as its headline. Read the closing sentence on its own and ask three things. Is there exactly one action here? Is it the natural next step of the story the document has just told — the step a reader who believed every word would want to take? And does the page it names deliver precisely what the sentence promises? A CTA press release that passes that test has done the component’s whole job: it has asked, once, politely, and in the service of the news.