Blogs, magazines & communities
Push notification best practices for blogs, magazines, entertainment, gaming and community sites
How often to send, what subscribers signed up for, what holds their attention and the mistake that loses it, for blogs, magazines, entertainment, gaming and community sites.
Updated · By the SharePush team
- Usual cadence
- 2–7 campaigns a week
- How solid this is
- Reasoned from the opt-in No independent study of push in this sector has been published. This follows from what the subscription promised, so weigh your own numbers above it.
What do people expect from push notifications on blogs, magazines, entertainment, gaming and community sites?
They liked what you make enough to want to know when there is more of it. That is a lower-urgency promise than news, and it tolerates far less volume.
How often should blogs, magazines, entertainment, gaming and community sites send push notifications?
The usual band is 2–7 campaigns a week. Around one a day at the top end. Nothing independent has been published at this granularity; the band follows from what the subscription promised.
That band is a starting point, not a target. Your own click rate is the better judge: it moves before the unsubscribes do.
What works on blogs, magazines, entertainment, gaming and community sites
- Push the pieces you would put on your homepage, not everything that went live.
- Let people pick topics: a broad catalogue with no topic choice is the fastest route to irrelevance.
- One a day is a ceiling to justify, not a quota to fill.
- A quiet week is fine. Volume for its own sake costs more than it returns here.
What is the most common push notification mistake on blogs, magazines, entertainment, gaming and community sites?
Publishing on a schedule and pushing everything on it. Not every post is worth an interruption, and treating them as equal drags the whole channel down.
The rules every site shares
Your sector changes the volume, not the rules. Chrome runs three systems against every site that sends web push (on-device spam warnings, automatic permission revocation and push API rate limits), and the same five habits keep you clear of all of them.
- Earn the permission before you ask for it The prompt itself is scored. A low acceptance rate pushes you into Chrome’s quieter UI and counts against you in the rate-limit formula.
- Treat volume as a budget, not a lever Volume is only half of every Chrome penalty: the other half is time spent on your site. Five pushes a day is fine for a daily-visit audience and disruptive for a once-a-month one.
- Write copy the classifier does not flag The model reads your title, body and buttons. It was trained largely on synthetic examples, so it is unpredictable: write like a newsroom, not like an ad.
- Send to the people who asked for that thing Relevance is the only input you fully control that raises engagement and lowers volume at once. It fixes both sides of the ratio Chrome measures.
- Prune before Chrome prunes you A dead subscriber is not neutral. They are the denominator dragging your engagement ratio under the revocation threshold, and they take the live subscribers down with them.