WordPress Push Notifications From wp-admin Without a Third-Party Service
Email open rates keep falling. Social algorithms bury your posts. Meanwhile the people who already like your site are one home-screen icon away, and most WordPress stacks still have no way to tap them on the lock screen.
Push is the channel native apps take for granted. Progressive Web Apps can use the same channel. The catch is how most WordPress sites get there: bolt on a third-party push SaaS, pay per message or per subscriber tier, and keep yet another dashboard password next to your ESP.
You do not need that stack. Progressify sends push from your own WordPress admin. No separate push vendor. No per-message fee. Subscribers, devices, and delivery stay on the site you already run.
This is not the offline caching story, and it is not the “when to show the install prompt” story. Those matter. Push is the re-engagement half: someone installed (or at least subscribed), left, and you still have a polite way to bring them back when you publish something worth opening.
The problem push actually solves
A PWA that never notifies anyone is an installed bookmark. Useful, quieter than it should be.
Push closes the loop after install:
- A new post goes live and interested readers hear about it without checking their inbox.
- A WooCommerce drop, restock, or flash sale hits phones that already opted in.
- A membership site can announce a lesson or event without waiting for the next newsletter blast.
The people who opt in already showed intent. They visited, often installed, and said yes to notifications. That list is smaller than your email list and usually warmer.
What breaks the pattern on WordPress is architecture. Many PWA plugins treat push as an add-on that forwards everything to OneSignal, PushEngage, or a similar service. You get another bill, another privacy review, and another place where “the plugin is fine but the push vendor is down.”
Progressify’s product page is blunt about the alternative: push straight from wp-admin, no third-party service, no per-message fees, no separate dashboard to log into. Manual sends and automations on new content. Image, action buttons, and an app badge count. A subscriber list with country, device, and browser.
That is the feature set this guide sticks to. Nothing invented beyond what the live Progressify page and docs describe.
What you need before the first send
Push rides on the same PWA foundation as install and offline.
- HTTPS. Service workers (and therefore push) need a secure origin. Local tunnels and valid SSL on production both count. Plain HTTP does not.
- A working Progressive Web App layer. Manifest, icons, service worker. Progressify generates those when you set an app name, icon (at least 512×512), and colors. If you are still fuzzy on what a PWA even is, start with the plain-English PWA guide, then come back here.
- Permission from the visitor. Browsers will not deliver lock-screen notifications without an explicit allow. Your job is to ask after someone has a reason to say yes, not on the first bounce.
iOS supports PWA push since 16.4. Progressify handles the iOS-specific quirks called out on the product FAQ. Test on a real device, not only desktop Chrome.
How to set up Progressify push on WordPress
1. Install and get the PWA basics green
Install Progressify from WordPress.org (free) or activate the Pro build from your DaftPlug membership. Fill in the web app manifest: name, short name, icon, theme color, display mode.
Open Chrome DevTools → Application → Manifest and Service Workers. Confirm the worker is registered and the manifest is complete. An incomplete manifest is a common reason install (and later engagement) never feels “app-like.”
2. Turn on push in Progressify settings
In Progressify → Push Notifications (see the docs under push notification settings), enable subscription controls so visitors can opt in. Keep the permission prompt tied to a clear moment: after install, after a second visit, or from a “Notify me of new posts” control, not stacked on top of three other overlays in the first ten seconds.
Pro unlocks the fuller push and automation set described on the Progressify page. Free is enough to validate the PWA shell; plan the membership when you want the engagement layer for real. One DaftPlug Pro licence unlocks Progressify Pro plus Lightify, Generatify, Rankify, and Snapshotify. Plans differ by site count (1 / 5 / 100), not by which plugins you get.
3. Grow the subscriber list on purpose
Push without subscribers is a compose box into the void. Treat opt-in like you treat email signup:
- Ask people who already scrolled, read, or installed.
- Explain what they will get (“New posts and restocks, a few times a week, easy to mute”).
- Respect dismissals. If someone said no, do not nag every page view.
Progressify keeps a subscriber list with country, device, and browser so you can see whether Android Chrome, iOS Safari, or desktop Edge is carrying the list. Use that when you debug “why did this send miss half our readers.”
4. Send a manual notification from the overview
Docs cover composing from the overview page. Keep the first live send boring and useful:
- Title: short, specific (“Weekly digest is up” beats “Check this out!!!”)
- Message: one reason to open
- Image / action buttons: optional, but useful when you have a clear primary action (“Read post”, “View product”)
- Badge count: the little number on the app icon when supported
Send to yourself on two devices first. Confirm lock screen appearance, tap-through URL, and that the badge behaves. Only then send to the full list.
5. Automate on new content (when you are ready)
Manual sends are for launches and corrections. Automations are for the boring rhythm: new post, new product, site events Progressify can hook. Turn automation on only after the manual path is trustworthy. A broken auto-push that fires on every draft save will burn trust faster than no push at all.
Start with one content type. Blog posts for a content site. Products for a shop. Measure open and uninstall signals for a week before you widen the triggers.
Pitfalls that make push feel spammy or broken
Asking for permission too early. A cold first-visit push prompt trains people to hit Block. Block is sticky. Earn the ask.
Treating push like a second newsletter. Three promotional blasts a day will get you muted. Use push for timely, high-signal moments. Leave long-form digests to email.
Ignoring iOS’s install path. Safari does not use the same install prompt event as Chromium. If your audience is heavy on iPhone, pair push with Progressify’s installation page that walks through Share → Add to Home Screen (documented under installation prompts). Push opt-in still needs the installed / eligible context the platform requires.
Assuming “sent” means “delivered to every phone.” OS battery savers, revoked permissions, and uninstalled PWAs all thin the list. Watch the subscriber list and delivery diagnostics in the docs’ sending guide when numbers look off.
Running a third-party push plugin beside Progressify. Two service workers fighting for the same origin is a classic mess. Pick one push path. Uninstall the other.
Forgetting HTTPS after a host move. Migrate to a host that serves a bad cert or a temporary HTTP canonical and push dies quietly. Fix SSL before you blame the plugin.
How this fits the rest of the PWA
Push is one slice. Offline caching, timed install prompts, bottom tab bar, dark mode, and (on Pro) Android / iOS store packages are the rest of Progressify’s all-in-one pack. If your goal is store listings as well as browser install, the no-code Android and iOS apps guide covers the generate-and-submit path without a native rebuild.
Keep the jobs separate in your head:
- Install prompts grow the home-screen base.
- Offline and app shell make the installed thing feel worth keeping.
- Push brings people back when you publish.
Skipping push leaves the most expensive part of acquisition (getting someone to care once) without a cheap re-engagement loop.
Membership note (so the pricing question is answered once)
Progressify Pro is not a lonely SKU. It ships inside the DaftPlug membership: one licence, every Pro plugin. Free builds stay on WordPress.org where listed. Annual Pro starts at $37.99 for one site, with Pro Plus and Pro Max for 5 and 100 sites. Fourteen-day money-back. Details live on pricing.
Takeaway
If your WordPress site already has repeat visitors, push is overdue. You do not need a second SaaS and a per-message line item to get it. Put Progressify on the site, get the PWA basics healthy, grow opt-ins after intent, send one careful manual notification, then automate publishing events you would have emailed about anyway.
The lock screen is not reserved for companies with native app teams. It is available to any WordPress site willing to treat push as a first-class channel instead of an afterthought bolted onto someone else’s dashboard.