New post published
New: {{post_title}}
A {{read_time}}-minute read on {{topic}}. Tap to read.
Use case
ReachBell for bloggers & content sites.
Push the post the moment it goes live, send a weekly roundup people actually read, and turn casual visitors into return readers — without bloating the page.
The problem
The bloggers tax: pageviews leak, subscribers don't compound.
Without a re-engagement layer, every post starts from zero. A push notification is the cheapest second pageview you can buy.
Most blogs and content sites live and die by referral traffic — search, social, and the home page. Search gives you an entrance; it almost never gives you a second visit. The reader bookmarks the post, closes the tab, and you never see them again. The cheapest way to fix that is web push: one click and the next post arrives on their lock screen instead of being lost to the algorithm.
The catch is that most push tools assume a marketing team behind them. They charge per send, expect daily campaigns, and bury the simple “tell my subscribers when there’s a new post” use case under a segmentation builder. Solo authors and small editorial teams need the opposite: zero-config new-post sends, a roundup template that doesn’t need a designer, and a free tier that holds for the first thousand subscribers.
The third problem is preference. Readers care about specific topics, not the whole site. A push for “Ten React tips” sent to a designer who came in via a CSS post is a one-click unsubscribe. ReachBell’s tagging + preference-center combo means subscribers can self-segment with two clicks — your unsubscribe rate drops, your relevance score climbs.
Templates
Templates for the publish button.
Six templates that cover 90% of what a blog or content site needs to send.
Weekly roundup, Sunday morning
This week on {{site_name}}
Our five most-read posts plus one staff pick. Coffee not included.
Trending now
{{post_title}} is taking off
A piece you might have missed — most-read today on the site.
Series-follower update
Part {{episode}} of {{series_name}} is up
You subscribed to this series — tap to pick up where you left off.
Welcome email to new subscriber
Thanks for subscribing
You'll get an email when something new lands. Here are three pieces to start with.
Comment reply notification
Someone replied to your comment
{{commenter_name}} responded on "{{post_title}}". Tap to read and reply.
Automation flows
Three flows for a one-person editorial team.
Built once, fired by the CMS — no daily click work.
New-post push automation
Every time you hit publish, your subscribers hear about it on whichever channel they chose.
- 01Trigger: WordPress hook on `publish_post` posts the title, slug, and category to ReachBell.
- 02Branch on category — readers tagged with that category get the push; others do not.
- 03Send web/mobile push first; respect quiet hours per timezone.
- 04After 24 hours, email the post to push-skipped subscribers who opted into email digests.
- 05Append UTM tags automatically so the analytics dashboard attributes the visits cleanly.
Weekly roundup
A single curated email every Sunday morning, generated from the week's top-performing posts.
- 01Cron: every Sunday at 08:00 in the subscriber's timezone.
- 02Query the last 7 days of posts, sorted by combined pageviews + push clicks.
- 03Render the roundup template with the top 5 posts and an editor's note.
- 04Send to the `weekly_digest` segment, suppress subscribers who already got an individual push for each top post.
- 05Track opens, clicks per slot, and surface the worst-performing slot to the author next week.
Subscriber growth loop
Turn one-time readers into repeat subscribers without a popup that nukes Lighthouse.
- 01Trigger: visitor reaches scroll depth > 60% on any post (front-end event fires to ReachBell).
- 02Wait 4 seconds, then show the soft prompt — copy and timing controlled from the dashboard.
- 03If accepted, write a `subscribed_from_post` tag with the slug so future analytics can attribute.
- 04After 24 hours, send the welcome email with three handpicked posts in the same category.
- 05After 7 days, prompt the subscriber to pick categories so future pushes are filtered properly.
In the wild
Who's using it.
Dogfooded across our own content properties.
StumpScore publishes editorial content alongside live scores — match previews, player profiles, post-match analyses — and uses the new-post flow above to push every long-form piece to subscribers who tagged the relevant team. The roundup runs every Monday morning so the weekend Tests get a second life.
VedHoroscope uses the same primitives for a different content shape: daily horoscopes are essentially a one-post-a-day publishing schedule, sent on timezone-aware cron. OmegleCo.’s blog uses the subscriber-growth loop to convert SEO traffic into push subscribers; the soft prompt fires only after scroll, so Lighthouse scores stay where they were.
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Does ReachBell work with WordPress out of the box?
Yes. The WordPress plugin auto-fires push notifications on publish, hooks into Yoast and Rank Math metadata, and respects your scheduled-post times. It also installs the soft prompt and service worker without touching theme files.
How do I push without becoming spam?
Set per-project frequency caps (e.g. max 1 push per day for marketing) and quiet hours. Categorise readers so they only get pushes about topics they tagged. Capped sends are skipped, not failed, so the audit log still shows what would have gone out.
Can subscribers pick which categories they want?
Yes. The hosted preference centre lists every tag you expose and lets subscribers toggle individual channels per category. Changes are reflected instantly in the segment engine, so the very next campaign respects the new preference.
What about RSS-style "send when there's a new post" without me clicking send?
That's the new-post flow above. The WordPress plugin posts to ReachBell on publish, the flow fires, and a push goes out — no manual step. For non-WordPress sites, any CMS that supports a publish webhook works the same way.
Will pushing posts hurt my Core Web Vitals?
No. The opt-in prompt and service worker are around 6 KB combined, load deferred, and never block paint. The prompt is configurable to appear after scroll depth or time-on-page so it doesn't fire on first paint — which also lifts opt-in rates.