Web push notifications from your website: worth asking for?
Short answer: Web push is worth it only if you have something timely that a visitor would genuinely want interrupting their day: an order ready to collect, a booking reminder, a restock they asked about, a live update. If your news can wait for an email, skip it. When you do use push, never ask on arrival; ask after the visitor does something that makes the value obvious, and expect iPhone users to need your site added to their Home Screen first.
Browser notification prompts have a poor reputation, mostly earned by sites that ask the moment you land, before you've read a word. That habit has given the prompt a bad name. Used well, though, web push can do something email can't: tell a customer, right now, that their thing is ready. The decision is about whether you have that kind of message.
How web push works, in brief
A website registers a service worker, a small script that runs in the background. MDN's Push API documentation explains that once the service worker is active it can subscribe using PushManager.subscribe(), producing a subscription with an endpoint and encryption keys. Your server (or a push service acting for you) sends messages to that endpoint, and the browser shows them as notifications, even when your site isn't open.
On iPhone and iPad, the picture is narrower. WebKit's announcement for iOS and iPadOS 16.4 introduced web push for Home Screen web apps: the visitor first adds your site to their Home Screen, and only then can the web app ask for permission, and only in response to a direct action such as tapping a "subscribe" button. Once allowed, notifications appear like any app's, can be managed per web app in Notifications settings, and respect Focus modes.
The decision tree
1. Do you have messages that are time-sensitive for the individual customer? Examples: "Your order is ready to collect", "Your table is ready", "Your appointment is in an hour", "The size you wanted is back".
- Yes → go to 2.
- No (blog posts, general offers, newsletters) → skip web push. Email or social does this job without the interruption.
2. Do customers come back to your site repeatedly, rather than once?
- Yes (regular orders, bookings, a members' area) → go to 3.
- No (a one-off purchase, a quote request) → use SMS or email for the one update you need to send. Push permission is a long-term relationship; don't ask for it to send one message.
3. Do most of your customers use iPhones?
- No, or a mix → go to 4.
- Yes, mostly → go to 3a.
3a. Will they realistically add your site to their Home Screen?
- Yes (a regular-use booking or ordering site that already behaves like an app) → go to 4, and plan a short "add to Home Screen" guide.
- No → skip web push for now, or treat it as a bonus for Android and desktop users while relying on SMS or email for the rest.
4. Can you send messages without a person remembering to? Push only pays off if it's triggered by events: order status changes, booking reminders, stock arriving.
- Yes (your booking or shop system can fire events) → use web push, carefully, with the permission approach below.
- No → fix the automation first. Hand-sent pushes stop the moment you get busy.
Most small business sites land on "skip" at step 1 or 2, and that's a good outcome. It saves your visitors a pointless prompt.
How to ask without getting blocked
web.dev's guidance on permission UX is blunt: asking as soon as a user lands gives no context and blocks them from what they came to do. It recommends asking at a moment where the value is clear, and describes a double permission pattern:
- Show your own message first, in your site's design, explaining what you'll send and why it helps.
- Only if they tap "Yes", trigger the real browser permission prompt.
The reason this matters: if someone blocks the browser prompt, you generally can't ask again through it. Your own pre-prompt can be declined harmlessly and shown later.
Good moments to ask:
- On the order confirmation page: "Want a notification when your order's ready to collect?"
- After booking: "Get a reminder an hour before your appointment?"
- On a sold-out product: "Notify me when it's back."
Bad moments: on page load, in the middle of checkout, or on a blog post.
What to send, and what not to
| Send | Don't send |
|---|---|
| Order or booking status for that person | Daily "check out our blog" pings |
| Reminders they opted into | Generic discounts to everyone |
| Back-in-stock alerts they asked for | Anything you'd hesitate to send by text |
| Genuinely urgent changes (closed today, slot moved) | Repeats of the same message |
Keep messages short, specific and actionable, and make tapping one go to the exact page that matters (the order, the booking), not your homepage.
Setting it up
You have two broad routes:
- A hosted push service. Third-party services (OneSignal is one example) provide the service worker code, subscription storage, sending dashboard and analytics. Fastest to start; check pricing, where data is stored and how easy it is to export subscribers before committing.
- Built into your own system. Your developer adds a service worker and sends pushes from your booking or order system when events happen. More work, but notifications sit directly on your own data and triggers.
Either way, give people an easy way to turn notifications off from your site, and say in your privacy notice what you send. Check the rules where you operate for consent wording.
Measuring whether it's working
Track four numbers each month:
- Prompt acceptance: of people who saw your own pre-prompt, how many said yes.
- Permission granted: of those, how many allowed the browser prompt.
- Click-through: taps per notification type.
- Opt-outs: unsubscribes after each kind of message.
A rising opt-out rate after a particular message type is your signal to stop sending it.
FAQ
Do web push notifications work on iPhone?
Yes, for websites added to the Home Screen as web apps, from iOS and iPadOS 16.4 onward, according to WebKit. In regular Safari tabs the experience differs, so don't assume iPhone visitors can opt in from a normal browser visit.
Is web push a replacement for an app?
For simple status updates, it can cover part of what an app would do. It doesn't replace the store presence, offline features or deeper device access an app offers.
Will push notifications annoy customers?
Only if you send things they didn't ask for. Event-based, personal messages tend to be welcome; broadcast promotions tend to drive opt-outs.
Can I send push without a service worker?
No. MDN notes an active service worker is needed for a site to receive push messages.
If you have a booking or ordering flow where a "ready now" notification would genuinely help, show us how customers wait today.