A restaurant owner I talked to this year had a notification plugin installed on his old site, left over from a past web designer, that was supposed to alert regular visitors about daily specials. When I asked how many people were actually subscribed, he didn't know, and when we checked, the number was eleven. Eleven people, out of a few thousand monthly visitors, had ever said yes to that permission prompt. That's the real story with push notifications on a small business website: the idea sounds like free marketing, but almost nobody grants the permission that makes it work, which is why I build this into a client's overall service package only when there's a specific, repeat-visit reason for it, and skip it for everyone else.
Should a Small Business Website Have Push Notifications?
For most small service businesses, no. A push notification requires a visitor to accept a browser permission prompt before they leave your site, and the overwhelming majority of people either ignore that prompt or actively deny it, especially from a business they've visited once. The feature works by registering a background service in the visitor's browser that can deliver an alert even when your site isn't open, which sounds powerful, but the permission step in front of it is a hard filter that most of your traffic never passes. If your real goal is reaching customers after they leave your site, a text message signup or an email list gets that message in front of far more of them, with no permission prompt standing in the way.
How Do Push Notifications Actually Work?
A visitor lands on your site, and at some point, your site asks their browser for permission to send notifications. If they click "allow," the browser registers what's called a service worker, a small background script that can receive and display messages even when your website isn't open in a tab. From that point forward, you (or a notification platform like OneSignal or PushEngage) can send an alert that pops up like a text message on their phone or a system notification on their computer. The technology itself is solid and has been a W3C web standard for years. The problem isn't how it works. It's how few people ever get past the first step.
Why Do So Few People Actually Opt In?
Three reasons, and they compound. First, most sites ask for permission the moment someone lands on the page, before that visitor has any context for why they'd want it, which Google's own developer documentation calls the single worst time to ask, since a block at that point can't be undone and the site loses the chance to ask again later (web.dev, push notification permission UX). Second, browsers have made it harder to abuse this prompt on purpose. Chrome rolled out a "quieter" permission interface specifically because so many sites spammed visitors with notification requests, which means your prompt is now competing against a browser that's actively trying to protect users from exactly this kind of ask. Third, once someone blocks or ignores the prompt, most browsers won't let your site ask again, so you typically get one shot per visitor, forever.
Does It Work the Same on Every Phone?
No, and this is the detail that changes the math for a small business. Android phones and desktop browsers (Chrome, Firefox, Edge) support the standard web push permission directly, no extra steps. iPhones are different. Apple only added support starting with iOS 16.4, and even then, it only works if the visitor adds your website to their home screen like an app first, something almost no one does for a plumber, a dentist, or a med spa they're checking out for the first time (WebKit, Web Push for Web Apps on iOS and iPadOS). If a meaningful share of your customers are on iPhones, which is true for most service businesses I work with, push notifications quietly exclude a big piece of your audience before you've sent a single alert.
Push Notifications vs. Text Alerts vs. Email: What Actually Reaches Customers?
| Push notification | Text message (SMS) | ||
|---|---|---|---|
| Requires browser permission | Yes, one-time ask | No | No |
| Works reliably on iPhone | Only if added to home screen | Yes | Yes |
| Typical open/response rate | Low, most visitors never opt in | High, most people read a text within minutes | Moderate, depends on subject line |
| Reaches visitor if they close the tab | Yes, if permission was granted | Yes, always | Yes, always |
| Setup cost | A plugin or service, often $10 to $50/month | A phone number and a signup form, often free to low-cost | Free to low-cost with Mailchimp or similar |
| Best use case | Returning visitors to a content-heavy site | Appointment reminders, order updates | Promotions, newsletters, less time-sensitive updates |
I've written in more detail about the tradeoffs of an SMS marketing signup and an email newsletter signup for a small business, and both reach more of your customers for less effort than push notifications, because they don't depend on a browser permission a visitor has to say yes to while they're still deciding whether to trust you.
When Does a Push Notification Actually Make Sense?
There's a narrow case where it's worth it: a business with genuinely frequent repeat visitors who come back to the same site often, like a blog with daily posts, a news-style publication, or an online ordering app customers reopen several times a week. In those cases, a visitor has enough reason to want updates that the permission ask lands with real context behind it. A roofing company's website or a dentist's website doesn't get that kind of repeat traffic, and most of their visitors show up once, decide whether to call or book, and don't come back to the same page again for months, which is exactly the pattern where a notification permission prompt has nothing to earn its place.
A restaurant comes closest to the exception, since regulars genuinely do check back for specials and hours. Even then, I'd rather see that restaurant put the effort into a fast, well-built restaurant website that's easy to bookmark and reload in under a second than into a notification feature that depends on a permission most visitors will never grant.
What Should You Do Instead?
Put your effort into a channel the customer already checks every day. A simple text message signup tied to appointment reminders, or an email capture tied to a specific reason to email (a seasonal promotion, a maintenance reminder), does the same job push notifications are trying to do, minus the permission wall. If you run a storefront business where people visit your site repeatedly, like checking a restaurant's weekly specials, a page that's fast and easy to bookmark will outperform a notification feature that most visitors will never grant permission for anyway. I'd rather spend that development time making sure your site loads in under a second and ranks well, which is work I can show you directly in a free mockup and speed test, than build a feature that converts at a rate most plugins won't even show you.
What Should You Do Next?
Skip push notifications unless you have a specific, repeat-visit reason for them, and put that budget toward a text or email signup instead, since both reach more of your real customers. If you want a second opinion on what your website actually needs instead of what a plugin vendor is selling, I'll build you a free mockup first and we can talk through what's worth adding and what isn't.
