Chrome removes push permission from ignored sites: reminders that survive
By Alan Magliocca · November 13, 2026
Quick answer: In an August 11, 2026 post, Google said Chrome revokes notification permission from sites people haven't recently engaged with and throttles disruptive senders to 1,000 push messages a minute. Ask for push permission at the right moment, send only a few useful reminders, and keep email and text alongside push.
- Chrome automatically revokes notification permission from sites a person hasn't recently engaged with, and from sites that repeatedly trigger suspicious-notification warnings.
- Google doesn't publish the engagement threshold or time window, so you can't plan around an exact number of days.
- Push from disruptive domains is capped at 1,000 messages a minute, with an HTTP 429 error beyond that.
- Push works best as one of three channels, saved for the moments closest to the start time.
What happened
On August 11, 2026, Google published a Chrome security post on how Chrome fights abusive notifications. It was written by Hannah Buonomo of Chrome Security, Jonathan Li of Safe Browsing and Nidhi Davawala of Firebase Cloud Messaging. Google says these defenses cut notifications on Android by over 7 billion a day in Q1 alone.
The post describes several layers:
- Revocation based on engagement. Chrome automatically revokes notification permission from sites a person hasn't recently engaged with. It also revokes it from sites that have repeatedly received suspicious-notification warnings. People can review and re-grant revoked permissions in Chrome's Safety Hub. Google doesn't say how long "recently" is.
- Abuse-network detection. Chrome looks for coordinated behavior across groups of sites and can revoke permission from networks that serve scams or malware.
- Server-side throttling. Firebase Cloud Messaging rate-limits push. It weighs message volume against the time people spend on the site, how often the site asks for permission, and overall engagement. Disruptive domains are capped at 1,000 messages per minute, and anything over that gets an HTTP 429 response. Limits grow with repeat offenses and reset only after a period of good behavior.
- A simpler permission model. Chrome added a new notification prompt on Android and one-tap unsubscribe on Android.
What it means for people selling with webinars
A web push reminder rides on a permission the attendee can lose without doing anything. That matters for events, because of how people use event sites. Someone registers, lands on a thank-you page, and may not visit your site again until the event starts. If the event is weeks away, that's a long stretch without engagement. Google doesn't publish the cut-off, so you can't know the exact day a permission might lapse. You can only make it less likely.
The throttling rules point the same way. Chrome judges push volume against how much time people actually spend on your site. A site that sends many pushes to people who rarely visit looks like the pattern Google is trying to stop. A site that sends a few pushes people act on does not.
The practical upshot: push is a strong channel for the last hour before an event, and a weak one to lean on alone weeks ahead. Email and text still carry the early reminders. If you send to a very large list, the 1,000-per-minute ceiling gets its own walkthrough in Chrome's 1,000-per-minute push limit.
How many push reminders should an event send?
Fewer than you think. Here is a schedule that keeps push for the moments where it does the most good. It's a planning example, not a Google rule.
- At registration, on the thank-you page: ask for push permission with a clear reason, for example "Get one alert 15 minutes before we start." Send the confirmation email right away.
- 24 hours before: email with the date, time in the attendee's time zone and the join link.
- 1 hour before: email, plus a text for anyone who agreed to texts.
- 15 minutes before: web push with the join link.
- At the start time: web push saying the event is live, with the join link.
- After the event: email with the replay.
That's two push messages per event. Each one is tied to a moment the attendee asked for, so it's likely to be opened rather than ignored. For the full channel-by-channel plan, see Email, text or push? A reminder schedule for 2026.
A checklist for push reminders that keep their permission
- Ask after the yes, not before. Request permission on the thank-you page, after someone registers, not as a pop-up on arrival.
- Say exactly what you'll send. "Two alerts: 15 minutes before and when we go live" is a promise people can accept.
- Keep every push useful. Each one should carry the join link and the start time.
- Don't promote through the reminder channel. Use push for "we're starting", not for every offer.
- Give people a reason to come back. A page with the agenda, a preparation checklist or a short video brings attendees back to your site before the event.
- Watch what happens after the push. Count clicks and joins from push, and drop any message that doesn't earn them. Measuring reminders by join rate and show-up explains how.
What to do this week
- List every web push your events send now, with timing. Remove anything that isn't tied to a start time or a replay.
- Move your permission request to the thank-you page, and rewrite the prompt text to say exactly which alerts people will get.
- Make sure every event also sends email reminders, and text reminders to people who agreed to them, so a lost push permission doesn't mean a missed event.
- For events more than two weeks out, add one reason to revisit your site before the date.
- If you send to a large list, check your push provider's logs for HTTP 429 responses. They mean Chrome is throttling you.
How BrightStage AI helps
BrightStage AI sends event reminders by email, text and web push, so push is one channel among three rather than the only one. Web push is confirmed on desktop and Android. You can split-test thank-you pages (A/B/C), which is where you'd test how and when you ask for push permission. When the reminder lands, the Join window lets attendees join the event or install the app. If you're comparing platforms on reminder options, AIVX Labs keeps a list of webinar platforms with SMS reminders.
Sources
Frequently asked questions
How long before Chrome revokes push permission from a site?
Google doesn't say. The post says Chrome revokes permission from sites a person hasn't recently engaged with, without giving a threshold or time window.
Can an attendee get a revoked permission back?
Yes. Google says people can review and re-grant revoked notification permissions in Chrome's Safety Hub.
Does the 1,000-messages-a-minute limit apply to every site?
Google describes it as the cap for disruptive domains, judged on message volume against time spent on the site, prompt frequency and engagement. Sends beyond the cap get an HTTP 429 response.
Related reading
Written by Alan Magliocca, founder of BrightStage AI and AIVX Labs (Podavinci LLC). Written with AI assistance and checked against the linked sources. Follow along: LinkedIn · YouTube · TikTok · X · Facebook · Instagram · Skool community
