How to write a press release in 2026: a journalist-first template built for AI search

First decide whether you actually have a press release

The easiest way to write a weak release is to start drafting before deciding whether the event is news. A new feature, partnership, hire or report may matter internally without giving an external audience a reason to care.

Write the news in one sentence before you write the headline. If that sentence depends on phrases such as “excited to announce,” “industry-leading,” “innovative solution” or “game-changing,” remove them and see what remains. The remaining fact is what a reporter has to evaluate.

• What happened?
• Why does it matter now?
• Who is affected?
• What is genuinely new or different?
• What evidence can an independent reader verify?

The press release format journalists expect

A familiar structure reduces cognitive load. Reporters should not have to search a branded microsite or a five-paragraph introduction to discover the announcement. Put the strongest information where a newsroom reader expects it.

The exact style varies by market and organization, but the following sequence works across most business releases.

• Headline: state the news in plain language.
• Optional subheadline: add the most important context or number.
• Dateline: location and date when relevant.
• Lead paragraph: answer who, what, when, where and why in roughly two sentences.
• Context: explain the problem, market change or evidence that makes the news significant.
• Quote: add interpretation from a named person, not a repetition of the headline.
• Supporting facts: numbers, methodology, availability, milestones or implementation details.
• Boilerplate: a stable, factual description of the organization.
• Media contact: a real person or monitored press contact with a clear response path.

A press release template you can adapt

Use the template as a structure, not as a fill-in-the-blanks excuse for generic writing. Every line should either state the news, prove it, explain why it matters or help a journalist follow up.

HEADLINE: [Company / organization] [does what] [for whom / with what consequence]. SUBHEAD: [One concrete number, date or differentiator]. DATELINE — [City, date] — [Lead sentence stating the news]. [Second sentence explains why it matters now]. CONTEXT: [One short paragraph with market, customer or research context]. QUOTE: “[Interpretation or consequence that adds information],” said [name, role]. SUPPORTING FACTS: [Two or three concise facts, including methodology where relevant]. AVAILABILITY / NEXT STEP: [What happens next, when and where]. ABOUT: [Factual boilerplate]. MEDIA CONTACT: [Name, email, phone or approved contact channel].

Write a headline a reporter can understand in one scan

A release headline is not an ad headline. Cleverness can reduce clarity, especially when the reader is triaging an inbox. Use concrete nouns and active verbs. If there is a strong number, date, location or outcome, consider including it.

Compare “Company X Reinvents the Future of Work” with “Company X Opens 120-Seat Manchester Engineering Hub.” The second headline gives the reader an event, scale and location before the release is opened.

Make the first paragraph do the heavy lifting

Assume the journalist will read only the headline and first paragraph. That opening should therefore contain the core announcement and enough context to decide whether the story is relevant to the beat.

Do not begin with company history, a market cliché or a quote from the CEO. Those details can follow once the news has been established.

Use quotes to add interpretation, not applause

Weak release quotes usually sound like marketing copy because they repeat the announcement with emotional adjectives. A useful quote explains a decision, consequence, trade-off or point of view that a reporter could not obtain from the factual paragraphs alone.

If a quote can be deleted without losing any information, rewrite it. Strong quotes can also signal spokesperson availability and give a reporter a starting point for follow-up questions.

Build for verification and AI-search clarity

The same habits that make a release easier for a journalist to use also make it easier for machines to interpret: explicit names, dates, numbers, definitions and sources. Avoid vague pronouns, unexplained acronyms and unsupported superlatives.

If the release is based on research, describe the sample, geography, fieldwork dates and methodology. If the announcement uses a category term that could be ambiguous, define it once in plain language. If an important number comes from an external source, attribute it. These details reduce the chance that a downstream summary strips the claim from its context.

• Use descriptive headings where the publishing format allows them.
• Keep one primary topic per release.
• State entity names consistently across the headline, body and boilerplate.
• Include dates and version context for facts that can become stale.
• Link to primary research, product documentation or supporting data when useful.
• Use Article or NewsArticle structured data on the owned newsroom page when technically appropriate; structured data helps describe the page but does not guarantee AI inclusion.

Distribution is not the same as media targeting

Publishing a release creates a public record. Sending it through a distribution service can extend that record. Neither step guarantees editorial coverage because a journalist still needs a reason to care about the story and confidence that it fits the beat.

Pair the release with a targeted pitch that explains why this specific reporter may care. Use recent editorial evidence, not synthetic compliments. The pitch can be short because the release carries the detailed facts; its job is to make relevance clear.

The 2026 pre-send checklist

Before publishing or pitching, review the release from three perspectives: newsroom usefulness, factual risk and discoverability. The checklist below catches most avoidable problems without turning the document into an SEO exercise.

• Can someone identify the news from the headline and first paragraph alone?
• Does every number have a source or clear owner?
• Are names, roles, dates, locations and product names correct?
• Does the quote add information rather than praise?
• Is the release concise enough to scan quickly?
• Are links pointed to primary supporting material where possible?
• Does the owned page have a unique title, meta description, canonical URL and crawlable text?
• Is structured data valid if the newsroom uses it?
• Has the target media list been built from editorial relevance rather than category labels alone?
• Has a human approved the final version before external distribution?

Sources & further reading

• Public Relations Society of America — How to write a press release that gets published — PRSA guidance on structure, brevity and journalist relevance.
• Google Search Central — Optimizing for generative AI in Google Search — Google guidance that useful original content and established search practices remain foundational.

Related PR guides

• AI for PR agencies: practical use cases and best practices
• AI media monitoring for PR agencies: what to track in 2026
• PR workflow automation: what to automate and what to keep human