The Chrome 2026 update has marketers in splits. Web push notifications have been around since 2015. For most of that time, the rules were simple – get subscribers, send notifications, and drive traffic.
Chrome has been tightening things gradually. Quieter permission prompts in Chrome 80. ML-based spam detection on Android. In October 2024, automatic permission removal of users who haven’t recently engaged on the website.
Publishers are now dealing with rate limits, silent subscriber removal, and spam filters that flag the kind of headlines that have driven clicks for years. The channel still works. But the way you use it needs to change.
What Chrome Actually Changed And What It Means For Your Push Strategy
1. Push API Rate Limiting
Publishers, especially news sites, send many notifications about breaking news, sports scores, weather alerts, and new listicles. The risk here is sending too many pushes to users who haven’t visited the site in a while. If you send high volumes of notifications but have low user engagement, Chrome restricts your ability to send messages to a value no less than 1000 per minute.
A publisher with 500,000 subscribers hitting this limit would take over 8 hours to reach their full list. At 1 million subscribers, that’s 16+ hours. For example, a breaking news alert sent at 9 AM becomes a midnight notification, basically when the news has gone cold, and users have read it elsewhere.
What most publishers don’t realise is that this compounds. It isn’t a one-strike system. The second consecutive day of disruptive behaviour extends the limit to seven days. A third pushes it to 14. And getting back to full sending speed requires 42 consecutive days of strong engagement. That’s six weeks of clean behaviour to undo three bad days.
What to do
The fix isn’t to send less news, but to send only to engaged segments. Subscribers who visited in the last 7 days get full frequency. Dormant subscribers get one, maybe two notifications a week. A smaller, engaged send will always move faster than a bloated blast that Chrome has decided to slow down.
2. Engagement-Based Evaluation
The three metrics that Chrome watches are push volume vs. time-on-site, permission prompts vs. time-on-site, and overall site engagement. Many publishers send 10 push notifications a day to a subscriber who spends only 2 minutes a month on the site. Chrome sees that ratio and flags the domain as disruptive.
What to do
Segment subscribers by recency. Eg – users who visited in the last 7 days get full frequency, while dormant users get a maximum of 1–2 notifications per week.
Easily segment based on the last website visit in the iZooto dashboard
3. Automatic Permission Revocation
Chrome automatically silently revokes subscriber permissions if they haven’t engaged recently. You will not know it until you see the delivery numbers drop.
What to do
Run a re-engagement push campaign. Your evergreen stories, top stories of the day or some e-book offer you want to share. Start targeting dormant subscribers before Chrome removes them.
4. ML-Based Spam Detection
Stay away from clickbait headlines. Phrases like “You won’t believe what happened next” or “SHOCKING: Celebrity does XYZ” are exactly the kind of patterns Chrome’s on-device ML models are trained to flag.
What to do
Before hitting send, ask yourself if this headline would pass your own editorial desk. If not, rewrite it. Make it factual and value-driven. For example, instead of “This city is turning dangerous. Find out why”. You can try headlines like “Crime rate in Bangalore rises 18% in Q1.”
What next?
The publishers who will feel this the most are the ones who’ve been playing the volume game with big lists, mass blasts, and hoping something sticks. Stop focusing solely on growing your subscriber list and focus on creating better experiences. Those days are getting harder. But if you’ve been sending notifications your readers actually want, Chrome’s changes don’t hurt you, they quietly clear the road ahead.
You can read more about the update on Chrome’s official blog. If you have any questions, reach out to us at support@izooto.com, and we will be more than happy to help.
