Why Some Press Releases Get Picked Up and Others Don't

Some press releases get picked up because they give a journalist or an editor something clear to publish: a real change, for a defined audience, explained in the first few lines, with proof and a person to contact. Releases that get ignored usually fail on one of those basics, not on every part at once, which is why a careful check of the hook, the audience, the lead, the assets, and the timing will usually reveal the problem.

This guide works through the five most common reasons a release is passed over, with a practical fix for each one. It is written for a small business owner or marketer who has already sent a release that went quiet, and for anyone who wants the next one to stand a better chance. The aim is not to promise coverage, which no honest distributor can guarantee, but to remove the avoidable reasons a good story never gets seen.

Key takeaways

• Pickup is not luck: it follows a real news hook, the right audience, a clear lead, useful assets, and sensible timing.
• If your release has no change a reader can point to, no amount of distribution will create news value.
• Send to people who cover your topic, not to the largest list you can find.
• Put the news in the headline and first paragraph, and prove it with a quote, a fact, and a way to follow up.
• Diagnose a quiet release before you rewrite it: check the hook, the list, the lead, the assets, and the timing in that order.

What does picked up actually mean?

Picked up can mean several different things, and confusing them leads to the wrong diagnosis. A release can appear on news sites through distribution, it can be rewritten or quoted by a journalist, or it can prompt a journalist to request an interview or more detail. Those are different outcomes, they need different strengths, and a release can succeed at the first without achieving the second or third.

Distribution places your release where editors and readers can find it, and that visibility has value on its own: it creates a public record, supports search visibility, and gives anyone checking your announcement a consistent version to quote. Editorial pickup is a separate step, taken by a person who judges whether the story serves their readers. When you review a quiet release, be clear about which result you expected, because the fix for low visibility is different from the fix for low editorial interest.

It also helps to judge pickup over a sensible window. Some stories are used the same day, others are filed for a feature, a roundup, or a slower news week. A release that seems ignored after a few hours may simply be waiting for the right slot. Give it time, check where it appeared, and only then work through the five reasons below in order, starting with the news value itself.

Reason 1: There was no real news hook

The most common reason a release is ignored is also the simplest: nothing in it is actually new. A new slogan, a redesigned website, a minor internal promotion, or a routine service update may matter inside the business, but none of them changes anything for a reader. Journalists are looking for a change they can explain to an audience, and if they cannot find one in the first paragraph, they move on to the next email in a crowded inbox.

The fix is to be ruthless about the hook before you write. Ask what a reader would learn that they did not know yesterday, and who would act differently because of it. If the honest answer is nobody outside your team, the release is premature. Wait for a genuine milestone, bundle several small updates into one meaningful change, or turn the material into a pitch or a blog post instead of a release. A smaller number of strong releases will serve your reputation far better than a steady stream of weak ones.

When you do have a hook, protect it. State it plainly in the headline and the first sentence, without burying it under background, mission statements, or praise for your own team. A launch date, a result, a new service that solves a named problem, or a decision that affects customers are all hooks. The reader should be able to repeat the news to a colleague after reading only the first paragraph, and if they cannot, the hook is still hidden.

The hook test

• Something has changed: a launch, a result, a decision, an opening, or a finding.
• The change affects people beyond your own team, and you can say who and how.
• There is a reason it matters now, not at any convenient moment.
• You can state the news in one sentence without adjectives or company history.

Reason 2: The release went to the wrong audience

Even a strong story fails when it reaches people who do not cover that topic. A local hiring announcement sent to national finance writers, a specialist product update sent to general news desks, or a consumer story sent only to trade press will all be ignored, not because the story is bad, but because it arrived in the wrong place. Relevance is the first filter a journalist applies, and it is applied in seconds.

The fix is to build the audience from the story outward. Start with the readers who would care, then find the journalists and outlets that serve those readers, and check recent coverage to confirm the fit. A short, well-matched list will outperform a huge generic list every time, because every recipient can see why the story was sent to them. If you are distributing widely as well, keep the core story clear enough that an editor scanning a feed can still recognise the audience and the angle at a glance.

Geography matters in the same way. A story with a strong local angle should make that place obvious early, with the town, region, or community named rather than implied. A story aimed at a specialist audience should use the terms that audience uses, without assuming a general reader will follow. Matching the story to the audience is not a distribution trick; it is basic respect for the reader, and it is what makes the rest of the release worth reading.

Reason 3: The lead was buried

Many releases contain a good story somewhere in the middle, after three paragraphs of company background, market context, and self-praise. By the time the news appears, the reader has already decided the release has nothing to say. Journalists read the way busy readers read: headline first, first paragraph second, and only then the rest, if the opening earns it. A buried lead is therefore not a small style problem; it is a structural failure.

The fix is the inverted pyramid: most important information first, supporting detail after. Write the headline as a plain statement of the news, not as a slogan or a teaser. Open with what happened, who it affects, and when, in language a stranger could understand. Then add the reason it matters, a supporting fact, and a quote from someone who can speak to the change. Background about the company belongs near the end, where an interested reader can find it without it blocking the news.

Read your opening aloud as a test. If a colleague hearing only the headline and first paragraph could not explain the news back to you, rewrite the opening until they can. Cut adjectives that claim importance instead of proving it, such as groundbreaking, revolutionary, or leading, and let the fact carry the weight. A clear lead also helps anyone who republishes or summarises the release, because the summary they write will be built from the lines you put first.

The lead, in order

• Headline: the news itself, in plain words, without hype or wordplay.
• First paragraph: what happened, who it affects, where, and when.
• Second paragraph: why it matters, with one fact or quote.
• Everything else: background, detail, and context, in order of importance.

Reason 4: There were no useful assets

A release can have a good hook and still be passed over because the journalist cannot use it without extra work. No quote from a named person, no image, no fact that can be checked, and no contact who will reply quickly all create friction. On deadline, friction is fatal: the journalist will choose the story that can be published with the material already in hand, even if your story is slightly stronger on paper.

The fix is to make the release self-contained. Include at least one quote that adds information or a clear point of view, rather than repeating the announcement in nicer words. Add the concrete facts a journalist needs: dates, places, numbers with context, and what happens next. Provide a named contact with a direct way to reach them, and make sure that person is actually available in the days after distribution. If images are relevant, provide them in a usable form with a plain caption, and say who may use them.

Assets also include proof. If you claim a result, show the basis for it: how many customers were involved, over what period, and what changed compared with before. If you announce a partnership, explain what each side actually does. If you cite a survey or a study, name who carried it out and when. Proof does not need to be long, but it does need to be present. A release that asks the reader to trust every claim, without offering anything to check, reads as promotion rather than news.

Reason 5: The timing worked against the story

Timing can quietly sink a release that is otherwise sound. Sending a story about a weekend event on the Monday after it, distributing during a major breaking news story that dominates every newsroom, or choosing a date with no connection to the news all reduce the chance of attention. Timing is not about a magic hour that guarantees coverage; it is about giving the story a fair chance to be noticed in the first place.

The fix starts with the story's own calendar. If there is an event, a launch date, or a deadline, work backwards and allow journalists time to read, ask questions, and plan. If the story is tied to a season, a report, or a public moment, say so early, so the relevance is obvious. Avoid sending a release and then disappearing: the days after distribution are when questions arrive, and a slow reply can lose a story that was about to be used.

Also consider what else is happening that day. A major election, a large industry announcement, or a national emergency will crowd out ordinary business news, and no headline can compete fairly with it. Where you have a choice, pick a quieter day. Where you do not, acknowledge the context in your planning and do not judge the release as a failure simply because the news cycle was unusually full. Timing is one factor among five, and it should be weighed alongside the others, not blamed for everything.

What other quiet killers should you check?

Beyond the five main reasons, a handful of smaller faults can tip a borderline release into the ignored pile. Errors are the most damaging: a wrong date, a misspelled name, or a figure that does not add up makes a journalist doubt every other claim in the document. Proofread with fresh eyes, check every proper name and number against its source, and have someone who was not involved in writing the release read it once before it goes out.

Length and tone matter too. A release that runs to several pages for a simple announcement suggests the writer could not decide what mattered. A release that is only a few lines suggests there is nothing behind the headline. Aim for the length the news needs, usually a focused page or two, with each paragraph earning its place. Keep the tone factual and calm, and let quotes carry opinion and enthusiasm. If every sentence claims to be exciting, none of them will be believed.

Finally, check the next step. A reader who is interested should know immediately what to do: visit a page, contact a named person, attend an event, or wait for a launch date. If the release ends without that guidance, interest has nowhere to go. A simple, specific closing line, with a working link and a responsive contact, turns attention into action and makes the release useful even for a reader who only skims.

Quick checks after the big five

• Errors in names, dates, or figures, which undermine trust in the whole release.
• Hype and superlatives that promise more than the facts support.
• A release so long that the news is lost, or so short that it raises more questions than it answers.
• No clear next step: no link, no contact, and no statement of what happens next.

How do you run a pickup autopsy on your own release?

Start with the document itself, not with the distribution. Print it or open it fresh, read only the headline and first paragraph, and write down the news in your own words. Then read the whole release and ask whether the rest of it supports that summary or contradicts it. If you struggled to summarise the opening, the lead needs work. If the body drifts into unrelated claims, the release is trying to do too much and should be split or trimmed to one clear topic.

Next, check the audience and the timing with the same honesty. List the outlets and journalists who received it, and for each one, note a recent story that shows they cover this topic. If you cannot point to one, the list was too broad or too hopeful. Check the date it went out against the story's own calendar and the wider news of that day. If the timing was poor, note it for next time rather than treating the story as dead: a good story with better timing and a sharper lead can often be reworked rather than abandoned.

Finish by checking assets and accuracy. Is there a usable quote, a checkable fact, an image where one would help, and a contact who replied promptly? Were all names, dates, and figures correct? Record what you find in a few honest lines, fix the weakest one or two items first, and use that note as the brief for the next release. The goal of an autopsy is not blame; it is to make the next announcement harder to ignore, one fix at a time.

Ready to get your news published?

A release that is picked up is usually a release that made the journalist's job easy: a real change, sent to the right people, with the news first, the proof included, and the timing thought through. If your last release went quiet, work through the five reasons above before you send the next one, and fix the weakest link first. Small, honest improvements to the hook, the lead, or the assets often make more difference than a larger distribution list.

When your story is ready, PressFudge can help you distribute it to news sites and reach the audiences that matter for your business. You can see the current plans and prices at pressfudge.com/pricing, from Basic at $149 to Enterprise at $2,749, with professional writing available as a $99 add-on on every order if you would like help shaping the release itself. Choose the plan that fits the story, send a release that earns attention, and give it the fair chance it deserves.