You sent a press release, waited, and received nothing. That silence does not establish that anyone rejected it, read it, or found it in spam. It leaves several possibilities unresolved.
The useful question is not “Why did journalists ignore us?” but “Which parts of this outreach can we verify, and what should we change?” Work through the checks below in order. Record evidence, distinguish observations from guesses, and stop when further outreach would add no value.
1. Establish what happened to the email
Start with delivery, not the headline. Check your sending platform’s bounce records, error messages, and suppression list. Verify the address against the publication’s current staff page or submission instructions. A reporter may have changed roles; an address copied from an old database may no longer be appropriate.
A hard bounce supports an address or delivery problem. No bounce does not prove inbox placement, and server acceptance does not prove human attention. Keep those conclusions separate.
Ask your email provider to check authentication and sending configuration. Google’s sender guidelines require SPF or DKIM for all senders to personal Gmail accounts, with SPF, DKIM, and DMARC required for bulk senders. These are requirements within that stated scope, not a universal promise of inbox placement or readership.
- Test: Review logs, verify addresses, and have your provider test authentication.
- Remedy: Resolve documented failures before further outreach.
- Stop: Do not resend the entire list to test whether the first message arrived.
A controlled test to an account you manage can expose formatting problems. It cannot reproduce every recipient’s filtering. Do not demand read receipts or treat an open-tracking pixel as certainty about reading.
2. Separate possible attention problems from known facts
Once obvious delivery faults are excluded, inspect what a recipient could see before opening: sender name, subject line, and preview text. Do they identify a concrete development, or merely announce that your organization has “exciting news”?
Ask a colleague unfamiliar with the project to describe the story from those elements alone. This tests clarity, not whether the journalist actually noticed the email.
Compare the release with your own website and earlier announcements. If the supposed development is already public and unchanged, the issue may be the absence of news rather than poor wording. The Purdue OWL press-release guide emphasizes new, useful, relevant information. Polished language cannot substitute for that substance.
Decision: Rewrite an unclear subject line for future outreach. If there is no meaningful development, stop pitching this announcement. A customer update or website notice may serve it better; this guide to what a press release is and when to send one can help frame that choice.
3. Test relevance against actual coverage
Review the recipient’s recent work and current beat. Identify specific coverage showing a connection to your subject. Then write one sentence explaining what their readers would learn, gain, question, or need to decide because of your announcement.
“They cover technology” is weak evidence. “They cover municipal procurement, and this contract changes how three local councils purchase software” is a testable connection. Even a strong connection does not establish interest in this particular story.
The Conversation’s pitching guidance is useful for thinking about existing coverage, readers, and concrete story ideas. Its academic-contributor publishing model is not a general business-pitching route, however, and its instructions should not be presented as universal newsroom rules.
- Evidence: Relevant articles, a current beat description, and a reader-specific explanation.
- Remedy: Narrow the recipient list or develop a genuinely different angle.
- Stop: Remove recipients when you cannot establish a credible connection.
4. Check whether the claims can support reporting
Underline every significant claim: cheaper, faster, first, larger, safer. For each, identify the source, comparison, timeframe, and limitations. If the release reports a percentage change, supply the underlying values and define what was measured.
Separate an organization’s assertion from independently established evidence. A company-funded survey, for example, needs clear information about its sample, questions, fieldwork dates, and methodology. A testimonial does not establish a general outcome.
Next, test access. Open supporting links while signed out. Confirm that documents do not require unexpected permissions, images have usable captions and rights information, and the named contact can arrange the promised interview. Tell recipients about confidentiality or access restrictions upfront.
Decision: Replace unsupported claims with accurate, bounded statements. Make essential evidence accessible without forcing a reporter through a sales process. If the central claim cannot be substantiated, pause outreach rather than disguising the gap with stronger adjectives.
5. Examine timing without inventing an explanation
Record the actual news date, the send date, and any deadline affecting readers. Was the announcement sent after the event? Did it arrive too late for a relevant planning cycle? Is an embargo clearly stated and agreed where necessary?
Check the publication’s coverage around that period. A major competing story may provide context, but it does not prove why your email received no response. Avoid turning a plausible explanation into a finding.
Editorial choice and resources remain separate considerations. A relevant, timely, well-supported story may still not be commissioned because of priorities, available reporting capacity, or overlap with planned coverage. Unless an editor tells you, those explanations remain unknown.
Decision: Correct a demonstrable timing mismatch for future outreach. Do not manufacture urgency or reannounce unchanged information simply to create another sending opportunity.
6. Decide whether one follow-up adds value
A single useful follow-up is a reasonable recommendation, not a rule for every journalist or publication. Follow explicit submission preferences, and allow time appropriate to the story’s deadline. There is no universally correct waiting interval.
Keep the message short. Identify the original story and add something useful: a newly available dataset, a confirmed interview window, or a concise clarification of reader relevance. Avoid “Did you read my email?” and requests for an explanation of silence.
If nothing has changed, consider stopping. Repeated reminders do not repair weak news value. If you discover a material error, send a clearly labeled correction separately; accuracy should not depend on your follow-up schedule.
Track outcomes honestly. Replies, interview requests, and published coverage are different results. Website visits are another measure: GA4 and UTM tracking can help attribute link traffic, but a visit does not identify an individual journalist’s reasoning or establish that the release was read.
A worked diagnosis: a fictional delivery-service launch
The following company, figures, and circumstances are illustrative, not reported facts. Suppose Alder Delivery announced a booking service and received no replies.
Weak headline and lead
Alder Delivery Revolutionizes Local Logistics
Alder Delivery today announced an exciting new platform that will transform deliveries for businesses everywhere.
The draft supplies neither a defined audience nor a verifiable change. An audit finds no recorded bounces, but that does not establish inbox placement. The list mixes national technology writers with local business reporters. Supporting information is behind a login.
Stronger headline and lead
Alder Delivery Opens Same-Day Booking to 120 Shops in Northbridge
Alder Delivery opened same-day parcel booking on 6 May for 120 independent shops in Northbridge. The service accepts weekday bookings until noon for delivery within the district by 6 p.m.; published prices start at £6 per parcel.
The remedy is not “send again to everyone.” First verify those figures, publish accessible service terms and coverage boundaries, and identify reporters covering local retail or transport. Offer an operations contact and disclose capacity limits. A targeted follow-up may then be justified, without implying that coverage will follow.
Use this audit worksheet before acting
Complete each line with an observation, supporting evidence, remaining uncertainty, and an action owner. Do not assign a numerical score: one unresolved factual problem can matter more than several polished details.
- Delivery: What do logs, address checks, and provider tests establish?
- Attention: Is the visible message clear? What remains unknown about exposure?
- Relevance: Which coverage and reader need support this recipient choice?
- Evidence: Can each central claim withstand scrutiny?
- Timeliness: What changed, when, and why does it matter now?
- Access: Can recipients obtain documents, images, and knowledgeable contacts?
- Editorial choice: What feedback exists, and which explanations are only hypotheses?
- Next step: Repair, narrow, follow up once if useful, or stop?
The goal is a defensible next action—not a confident story about someone else’s silence.
