Google Chrome’s new notification policy - how to adjust your web push strategy

The web push ecosystem is changing fast, and the period between 2024 and 2026 has brought the most significant updates in the history of the technology. Google Chrome has introduced several aggressive mechanisms designed to protect users from spam, deceptive content, and notification overload.

For publishers and brands, the message from Google is clearer than ever: quality and engagement are the only ways to maintain a healthy subscriber base. If your strategy doesn't evolve, your domain risks being throttled or silenced entirely by the browser.

The good news? With the right strategy, you can stay ahead of these changes – and even strengthen the quality of your audience.

Below is a breakdown of what Chrome changed, what it means for your push performance, and what we at PushPushGo recommend based on our data.

Timeline: the evolution of Chrome’s web push restrictions

To understand the current landscape, we have to look at how Google has systematically prioritized the user experience over the last few years.

2020-2024: the era of "Quiet Cleaning"

Google began by targeting intrusive permission prompts and "noisy" environments.

February 2020 (Chrome 80)
Google introduces the Quieter Notification UI. This replaced intrusive pop-ups with a bell icon in the address bar for sites with low opt-in rates or for users who frequently block requests.

• January 2024 (Chrome 121)

Introduced "silent pushes" for extensions to reduce visual clutter.

• May 2024

Aggressive application of the Quieter Permission UI, automatically silencing opt-in windows on sites with low user acceptance rates.

• August 2024 (Chrome 128)

Algorithms began flagging "manipulative" prompts, such as those that hide content until a user clicks "Allow."

2025: machine learning and automatic purges

This was the year Chrome began "reading" content and managing user lists based on real-world interaction.

• May 2025: on-device Machine Learning (ML) 

Chrome rolled out an on-device machine learning model that evaluates notification content before it appears on a user’s screen.

This system:

• classifies messages as “useful” or “potentially spammy”

• flags misleading or deceptive content

• analyzes notification wording, frequency, and engagement

• uses internal blacklists of known abusive patterns

If a notification appears harmful or looks like spam, Chrome can:
✅ show a warning, or
✅ automatically unsubscribe the user from that website’s notifications.

Example of a notification identified as potentially spammy

This update applies primarily to Android, but the logic influences Chrome’s broader anti-spam strategy.

• October 2025: automatic permission revocation

On October 10, 2025, Chrome announced a new step - automatically revoking notification permission from sites with low user engagement.

Here’s how it works:

If users haven’t interacted with your site recently and your notifications are ignored or dismissed, Chrome may unsubscribe them automatically and show a message such as:
“Chrome unsubscribed you from notifications due to low activity.”

Users can re-enable notifications through Safety Check, but for many websites, this has caused a noticeable drop in subscriber numbers.

Chrome’s own tests showed a big reduction in unwanted notifications with minimal loss of meaningful engagement - but for publishers who send more frequently, the impact is already visible.

2026: the era of rate limiting 

As of January 2026 (Chrome 144/145), Google has introduced Push API rate limits as a direct consequence of low engagement.

How Chrome evaluates your site

Every day, Chrome calculates whether a site is "disruptive" based on three specific pillars of engagement:

• The Message-to-Time ratio

  The number of push messages sent relative to the actual time a user spends on your site.

• The Prompt-to-Time ratio

  How many permission prompts you show relative to user session duration.

• The Site Engagement score

  A combination of "foreground minutes" (active browsing) and direct interactions with your content.

The consequences of low engagement

If your site is identified as sending a high volume of notifications with very little user engagement, Chrome triggers the following:

• The 1,000/minute cap

  Your sending ability is limited to no less than 1,000 messages per minute. Any requests above this threshold will return an HTTP 429 (Too Many Requests) error.

• The impact on mass campaigns

  For a database of 100,000 subscribers, a "Breaking News" campaign that once took seconds will now take over 1.5 hours to complete.

• The multi-day penalty system

  - 1st day of disruptive behavior: 1-day rate limit.

  - 2nd day: 7-day rate limit.

  - 3rd day (and beyond): 14-day rate limit.

• The path to recovery

  To reset this counter and regain full sending speed, a website must maintain 42 consecutive days of "non-disruptive" (high-engagement) behavior.

What this means for your web push strategy

Chrome’s goal is not to punish legitimate publishers. Their data shows that these changes help boost engagement for sites that send meaningful, targeted, and relevant notifications. 

The official Chrome documentation emphasizes that "nearly all websites will be unaffected by this change." The limit is specifically targeted at a small number of sites that use the Push API as a "megaphone" rather than a precision tool. As a result, you may see:

• Increased opt-outs

  Particularly for sites with high sending frequency and repetitive content.

• Permission revocations

  Chrome will cut your list for you if you aren't providing enough value to keep users active.

• Throttled reach

  If your content is consistently ignored, your ability to reach your full base quickly will be limited.

Are you at risk?

If you answer "No" to any of the following, your delivery rates are likely being throttled:

• Do you segment your audience? Mass blasts result in low engagement and high bounce rates, which flag your site to Google.

• Do you use frequency capping? Sending too many notifications per subscriber daily is a primary trigger for these limits.

• Are your engagement rates healthy? Google prioritizes sites where users actually spend time.Check Google’s engagement standards here.

How to prevent subscriber loss and maintain high engagement

Based on our data at PushPushGo, we have identified clear patterns and actionable ways to stay ahead of these changes.

1. Focus on truthful, high-quality content

Chrome’s ML checks whether notifications:

• mislead users

• include suspicious language

• contain manipulative calls to action

Avoid vague or exaggerated messaging. Be specific, honest, and helpful. Quality of engagement matters more than the quantity of subscribers.

2. Target your campaigns – don’t rely on mass sends

Sites sending mostly mass campaigns are affected the most by the new limits. Use segmentation, behavioral triggers, and category preferences. Personalized messaging keeps engagement high and prevents Chrome from reducing your reach.

3. Monitor sending frequency

Avoid exceeding 4 notifications per day unless you see strong user engagement that justifies more frequent communication.

Excessive frequency is one of the clearest triggers for Chrome’s automated filters.

You can also set up capping, a maximum number of notifications a subscriber can receive per day. To enable this feature, please contact our support team at support@pushpushgo.com.

2. Maintain a minimum 4-hour interval between campaigns

Sending campaigns too close together can:

• lower CTR

• raise user fatigue

• signal “spam-like behavior” to Chrome’s ML model

Spacing messages protects your deliverability.

5. Watch your engagement metrics closely

Chrome considers user interaction signals. If a segment hasn’t engaged for a long time:

• reduce frequency

• use reactivation campaigns

Quality of engagement matters more than quantity of subscribers.

6. Complement push with onsite notifications and pop-ups

If Chrome blocks or revokes permissions, on-site communication tools help you:

• reconnect with users

• regain subscriptions

• explain how to re-enable notifications

Summary: how to stay ahead of Chrome’s changes

Chrome’s updates push the industry toward relevance, transparency, and user protection. This is good news for companies that:

• send meaningful content

• use segmentation

• respect user attention

• maintain healthy frequency patterns

And a challenge for those relying on volume alone.

But with thoughtful adjustments and the right tooling, you can maintain a strong subscriber base and even improve your engagement.

At PushPushGo, we’re monitoring Chrome’s changes closely and adjusting our best practices based on real data from our clients. We will continue sharing new insights and recommendations as Google rolls out additional updates.