Blog Tech

Push notifications for news publishers: what to send, how often and how permission works

What deserves a news push alert, how often to send, and how permission, channels and timing work on Android, iOS and the web.

Illustration of a smartphone with a ringing bell and three notification cards rising from the screen, next to a folded newspaper and a toggle switch

Short answer: a news push alert should be rare, verified, complete enough to understand without tapping, and sent only to readers who asked for that kind of story. Publishers that treat the lock screen as a front page lose readers fast, because one irritated swipe turns alerts off for good. The ones that keep their audience send fewer alerts, segment them by topic, and make the first permission request at a moment when the reader already sees the value.

Phones also changed the rules under publishers’ feet. Since Android 13, a new app can’t send a single notification until the reader taps “Allow,” and Android has let readers mute an app’s alert categories one by one since version 8.0. For a newsroom that builds its own reader app, these are product decisions as much as editorial ones, and they are usually settled by an Android app development team long before the first alert goes out.

This guide covers both sides: the editorial rules for what deserves a push, and the mechanics of how permission, channels and timing work on Android, iOS and the web. If you are still deciding whether you need an app at all, start with our guide on whether an independent newsletter needs its own app.

What is a news push notification, and why does it matter?

A news push notification is a short message a publisher sends to a reader’s lock screen or browser, usually with a headline and a link to the full story. It is the only channel that reaches a reader without the reader opening anything first.

That reach is why newsrooms lean on alerts to bring readers back. It’s also why they carry more risk. An email that misses gets archived. A push that misses can get the whole app silenced, and turning alerts back on means a trip to the phone’s settings that a reader has no reason to make.

Publishers use three kinds of push:

  • App push. Sent through Apple Push Notification service on iOS and Firebase Cloud Messaging on Android to readers who installed your app.
  • Web push. Sent from your website to readers who allowed notifications in their browser. No app required.
  • Email and SMS alerts. Not push in the technical sense, but readers experience them the same way, and they compete for the same attention.

App push, web push or email: which channel fits a small publication?

Web push is the cheapest way to start, app push gives the most control, and email reaches the most people. Most small publications should begin with web push and email and add app push only when they already have a reader app for other reasons.

ChannelWhat the reader must doTopic control for readersBest for
App push (Android)Install the app and tap “Allow” (Android 13 and later)Strong: separate notification channels per topicPublications with a loyal daily audience
App push (iOS)Install the app and accept the system promptSet inside your app; iOS adds Focus modes and summariesSame, plus readers who live on iPhone
Web pushAllow notifications in the browser; on iPhone, first add the site to the Home ScreenWhatever your website offersSmall sites testing whether alerts work at all
Email alertSubscribe with an email addressSeparate lists or preferencesDaily briefings and less urgent news

The iPhone row matters for US publishers. Apple added web push to iOS and iPadOS 16.4 in 2023, but only for sites that a reader has saved to the Home Screen as a web app. That is an extra step many readers never take, so web push on its own misses part of your iPhone audience.

How do readers grant permission on Android and iOS?

On both platforms, the reader decides once, and changing that decision later takes a trip to the phone’s settings. That makes the first request the most valuable moment in the whole relationship.

Android: runtime permission and notification channels

Android 13 (API level 33) introduced the POST_NOTIFICATIONS runtime permission. An app that targets Android 13 or later can’t post notifications until the reader grants it, and Google’s guidance is to ask in context rather than at first launch (Android notification permission docs). If the reader declines twice, Android stops showing the prompt, and only the settings screen can turn alerts on again.

Notification channels, available since Android 8.0, are the other half. Every alert belongs to a channel such as “Breaking news,” “Daily briefing” or “Local,” and the reader can mute, silence or change the sound of each channel separately. A publisher that puts everything in one channel forces readers into an all-or-nothing choice. Many simply turn the whole app off.

iOS: one prompt, provisional delivery and interruption levels

iOS shows its system permission prompt once. Many news apps first show their own explanation screen, then trigger the system prompt only if the reader says yes. iOS 12 added provisional authorization, which lets an app deliver quietly to Notification Center without asking; the reader then chooses to keep or turn off those alerts.

Since iOS 15, every notification also carries an interruption level: passive, active, time-sensitive or critical. Time-sensitive alerts can break through Focus modes and the scheduled summary, so they should be reserved for news that truly can’t wait. Critical alerts need a special entitlement from Apple and aren’t meant for journalism. Apple documents these options in its UserNotifications framework.

What news deserves a push notification?

A story deserves a push when a reader would be annoyed to learn later that you knew and stayed quiet. That test filters out most content, which is the point.

Good candidates:

  • Verified breaking news that changes something for the reader today: a vote result, an emergency, a major ruling.
  • A story readers explicitly follow, such as an ongoing trial or a local election, delivered through its own topic channel.
  • A daily briefing at a fixed time, which readers can plan around and switch off separately.
  • A significant correction to an earlier alert (more on that below).

Poor candidates are features, opinion pieces, listicles and anything whose real goal is traffic. Readers can tell, and the cost of that lesson is the permission itself.

How often should a newsroom send alerts?

Send as often as your readers expect, and no more. There’s no universal number. A national breaking-news app and a weekly satire newsletter serve different promises, and readers judge frequency against the promise you made when they opted in.

A few rules hold across newsrooms:

  • Keep breaking alerts for news that is actually breaking; fill quiet days with silence, not filler.
  • Cap follow-up alerts on a single story. One alert for the event and one for the decisive update is usually enough; the live page can carry the rest.
  • Respect local time. Unless the news is urgent, don’t wake people up.
  • Watch opt-out rates after each alert, not just open rates. A spike in people turning alerts off is the most honest feedback you’ll get.

How do you write a push alert that people trust?

Write the alert so a reader who never taps it still knows what happened. The lock screen is the story for most people who see it.

  1. Lead with the fact. Who did what, where. Put the most important words first, because long alerts get truncated.
  2. Skip the tease. “You won’t believe what the senator said” wins one tap and loses the reader’s trust.
  3. Name the source when it matters. “Officials say” or “according to court filings” tells readers how solid the news is.
  4. Use the brand line. Your publication name should appear in every alert so a screenshot still says who sent it.
  5. Link to a page that loads fast on a phone. A slow page after a tap wastes the alert.

What changes if you publish satire?

Satire is where push alerts get risky. A lock screen strips away the masthead, the layout and every other cue that tells a reader a story is a joke. As we explain in our guide on how to tell satire from fake news, a satirical headline that travels alone is easy to mistake for a real report, and a screenshot of an alert travels further than any article.

A satire publication that uses push should label every alert in the text itself, keep satire and real news in separate notification channels, and avoid the “BREAKING” format unless the alert visibly says it’s satire. The deadpan style we describe in why satire headlines work is exactly what makes an unlabeled alert dangerous.

How should you correct an alert that turned out to be wrong?

Correct it with a new alert to the same audience, and do it quickly. You can’t recall a push that was already delivered, and the original will sit in Notification Center long after the story changes.

  • Send the correction through the same channel and segment as the original.
  • Say plainly what was wrong and what is true now.
  • Update the linked article and note the correction there, as you would for any error. Our corrections page shows how we handle that on this site.
  • Review why it happened: who approved the alert, and whether the “verify first” step was skipped under deadline pressure.

Which metrics show that alerts are working?

The useful metrics measure whether alerts build a habit, not only whether they get taps. Track them per channel and per alert type.

  • Opt-in rate: the share of readers who allow notifications when asked.
  • Open rate: taps divided by delivered alerts, compared within the same alert type.
  • Opt-out rate: how many readers mute a channel or disable alerts after a given alert.
  • Retention: whether readers with alerts on return more often over 30 and 90 days than readers without them.

Open rate on its own rewards clickbait. Opt-out rate and retention punish it, which is why they belong on the same dashboard.

How to set up a news push strategy in seven steps

  1. Write a one-paragraph promise. What readers will get, roughly how often, and what you will never push.
  2. Define topic channels. At least “Breaking” and one regular product, such as a daily briefing. On Android, map each to its own notification channel.
  3. Design the ask. Request permission after a reader shows interest, such as after reading a second story or following a topic, not on first launch.
  4. Set an approval rule. Name who can send a breaking alert and require a second person to check facts and wording.
  5. Prepare correction templates. Agree on wording before you need it.
  6. Pick your metrics. Opt-in, opens, opt-outs and retention, reviewed weekly.
  7. Review monthly. Drop alert types with high opt-outs and low opens, even if someone likes them.

Frequently asked questions

How many push notifications should a news app send per day?

There is no universal number. Match the promise you made when readers opted in: a breaking-news app can send several alerts on a busy day, a niche publication may send a few a week. Watch opt-out rates after each alert to find your limit.

Do readers need to install an app to get news alerts?

No. Web push works from a website in most desktop and Android browsers. On iPhone and iPad, web push only works after the reader adds the site to the Home Screen, which is why many publishers also offer email alerts.

Why did my Android app stop getting notification opt-ins after an update?

Apps that target Android 13 or later must ask for the POST_NOTIFICATIONS permission before sending anything. If the request appears at first launch with no context, many readers decline, and after two refusals Android stops showing the prompt.

Should satire publications send push notifications?

They can, but every alert should say it is satire in the text itself and travel in its own notification channel. A lock screen removes the masthead and design cues that tell readers a story is a joke.

Can you delete a push notification after it is sent?

Not reliably. Once delivered, the alert stays on the device. The honest fix is a correction alert to the same audience and a correction note on the linked article.

From the blog of The Smattering, where we write plainly about satire, media literacy and how we work. More posts.

Get the next one first

Free satire in your inbox once or twice a week.