Skip to content
Writing & timing · 10 min read

Web push notification best practices (2026 checklist)

Everything that matters for web push in one place — from the first prompt to the hundredth campaign. Each item links to a deeper guide when you need detail.

Get started — freeTry a live notification
Updated By the Pusharoo team
In short
  • Ask politely and at the right moment — never on page load.
  • Support iPhone properly with a manifest and an Add to Home Screen hint.
  • Write specific, short, honest messages and send them when people are awake.
  • Segment, measure clicks, clean dead subscriptions and keep data to a minimum.

1. Opt-in

  • Use a two-step opt-in: your own soft prompt, then the browser dialog only after “Allow” (why).
  • Wait for a signal of interest — a few seconds, a scroll, or a click on “Get alerts”.
  • Say what you’ll send and how often.
  • Respect “Not now”: wait days, not minutes, before asking again; never re-ask after a browser block.

2. iPhone and iPad

  • Add a web app manifest so the site can be saved to the Home Screen (PWA guide).
  • Show iPhone visitors a short “Share → Add to Home Screen” hint instead of a prompt that can’t work.
  • Test from the Home Screen icon on iOS 16.4+ (iPhone guide).

3. Copy

  • Front-load the value in about 30–40 characters (limits).
  • Be specific: product, number, deadline (copywriting).
  • Link to the exact page, not the homepage.
  • Use your own logo as the icon; no third-party badges (white-label).

4. Timing and frequency

  • Send during waking hours in your subscribers’ time zones (best times).
  • Keep the frequency you promised (frequency).
  • Schedule ahead rather than sending whenever you remember.

5. Targeting and automation

  • Segment by device, language, recency and inactivity (segments).
  • Run a short welcome series for new subscribers (automations).
  • Send win-back messages to inactive subscribers sparingly.

6. Deliverability and hygiene

  • Serve sw.js from your root with no long caching (caching notes).
  • Remove subscriptions the push service reports as gone (404/410) — automatic in Pusharoo.
  • Set sensible time-to-live for time-sensitive messages (deliverability).
  • Run only one service worker per scope to avoid conflicts.

7. Measurement

  • Track click-through per campaign and per automation step (CTR guide).
  • Add UTM tags so analytics attributes visits and sales (analytics).
  • Watch opt-in rate when you change the prompt (opt-in rate).

Starting from zero?

Do these five first: create a free account and install the two files (docs); set a delayed, branded soft prompt with a frequency promise; add a manifest for iPhone; create a short welcome automation; and schedule your first campaign with UTM-tagged links. Everything else on this list is refinement.

Content plan

  • Welcome series for every new subscriber (examples).
  • A predictable rhythm: one or two campaigns a week for most sites.
  • Seasonal peaks planned in advance (calendar).
  • Win-back for subscribers inactive 30–60+ days (guide).
  • A/B test one element per campaign.

Compliance in one line each

  • GDPR: explicit opt-in via the browser, clear notice, minimal data (guide).
  • CCPA: list push data in your notice, honour requests, don’t sell it (guide).
  • CASL: identify yourself in the prompt, easy opt-out (guide).

8. Privacy and trust

  • Collect only what you need; avoid cookies and fingerprinting for push.
  • Explain push in your privacy notice and make unsubscribing easy (privacy guide).
  • Never use push for deceptive alerts (“Your device is infected”).

Questions

What is the most important web push best practice?

A polite, well-timed opt-in. It decides how big and how engaged your list becomes, and browsers now penalise sites that ask on page load.

Do these best practices apply to app push too?

Most do — specificity, timing, frequency and segmentation are universal. The opt-in and iPhone details are web-specific.

How do I know if my push strategy is working?

Track opt-in rate, click-through and unsubscribes over time, and attribute visits with UTM tags in your analytics.

What’s the biggest push notification mistake?

Asking for permission on page load with no context. It wastes your one prompt and can trigger the browser’s quieter UI for your site.

How often should I review my push programme?

Monthly: check opt-in rate, CTR per campaign, unsubscribes and which automations still earn clicks. Retire what doesn’t.

The push opt-in prompt, done right

Two-step soft prompts, timing rules, copy that converts, and what never to do on page load.

Push notification copywriting: 12 rules that earn the tap

Twelve practical rules with before-and-after rewrites: specificity, verbs, honest urgency, tone and testing.

How often should you send push notifications?

Frequency guidelines by site type, the warning signs of over-sending, and how to set expectations at opt-in.

Push notification deliverability: what really affects delivery

Expired subscriptions, TTL, offline devices, Focus modes and worker errors — and how to fix each.

More in Writing & timing: 30 web push notification examples (and why they work) · Push notification character limits, in practice · The best time to send push notifications · Welcome push notifications that set the tone · Holiday push notification calendar for 2026–2027 · All guides

Free for life. No limits.

Unlimited subscribers, campaigns and automations. No badges. About five minutes to install.

Get startedTry a live notification