Chrome now limits web push notifications from sites that send a lot of messages but get very little engagement in return. If your store sends push notifications that people want and click, the change is very unlikely to touch you; if you send many messages that people ignore, Chrome can slow your sending down for days at a time.
This post explains what Chrome announced, how it decides which sites to limit, what a limit looks like in practice, and the simple habits that keep a Shopify store on the right side of the rule. Every rule below comes from Google's own pages, and each one is linked where it is used.
New to web push? Start with our guide to web push notification marketing, then come back here.
Add free push notification app to Shopify
Get free Shopify push notificationsWhat Chrome Changed
In January 2026 the Chrome team announced that Chrome would begin rolling out rate limits for the Push API, aimed at sites that send a high volume of notifications with little engagement from the people who receive them. In August 2026 Google confirmed that these limits are now in place: disruptive sites are limited to 1000 messages per minute and receive an HTTP 429 response above that.
Two details in that announcement matter for store owners:
- It is aimed at a small group of sites. In the Chrome team's own words, "Nearly all websites will be unaffected". The rule is written for sites whose notifications people mostly ignore.
- It covers push messages, not every notification. The limit applies to the Push API, which is what delivers a notification when the shopper is not on your site. Chrome says sites can still show notifications while the site is open through the separate Notifications API.
This is not the first step Chrome has taken against unwanted notifications. The same announcement lists earlier ones: quieter permission prompts from Chrome 80 for sites that people rarely accept, warnings on Android about notifications that look spammy, and automatic removal of permission for sites that Google Safe Browsing marks as abusive. Google has since added that Chrome also removes notification permission from sites that have repeatedly received suspicious notification warnings. The new limits add one more layer on top of these.
What Chrome Measures
Chrome does not look at one number. According to the Chrome developer blog, it calculates three things every day:
- Push messages sent per time spent on the site. How many pushes a site sends compared with how much time people actually spend on it.
- Permission prompts shown per time spent on the site. How often a site asks people to allow notifications compared with how long they stay.
- User engagement. This is based on Chrome's site engagement score and the minutes people spend with the site in the foreground.
A site that sends a high volume of messages while getting very little engagement is treated as disruptive. Notice what this means: a store with an active audience can send regular campaigns without trouble, while a store that sends just as many messages to people who never visit can be flagged. The balance between sending and engagement is what counts, not the raw number of messages.
What counts: sending against engagement
The second measure is easy to miss. It is not only about what you send; it is also about how often you ask. A permission prompt that appears again and again, to visitors who leave quickly, counts against the site too.
What Happens When a Site Is Flagged
When Chrome treats a site as disruptive, it limits how fast that site can send push messages. The announcement says the limit will be set to a value "no less than 1000 per minute", and that requests above the limit receive an HTTP 429 response, the standard "too many requests" answer. In plain terms, messages above the limit are refused rather than delivered.
The limit also grows longer if the behaviour continues. Chrome gives this schedule on the same page:
- After the first day of disruptive behaviour, the limit applies for one day.
- After the second day, the limit applies for seven days.
- After the third day and every day after, the limit applies for 14 days.
- The count resets after 42 days in a row without disruptive behaviour.
How long a limit lasts
For a store, the timing is the real risk. A limit that lasts 14 days could cover a whole sale period, and the count only clears after six weeks of good behaviour. Chrome also notes that the specifics may change over time, so treat these numbers as today's rule rather than a promise.
A limit of 1000 messages per minute still lets a lot through. The bigger lesson is the signal behind it: a high volume of pushes that people ignore is what Chrome treats as disruptive, so every message you send should be one people want to open.
The Other Rule: Chrome Can Remove Permission
The sending limit sits beside a second change that Google announced in October 2025. Chrome on Android and desktop automatically removes notification permission from sites a person has not interacted with recently. Google says this happens only when there is very low engagement and a high volume of notifications being sent.
The difference between the two rules matters:
- The rate limit works on the whole site. It slows down how fast the site can send to everyone.
- Permission removal works person by person. A shopper who has stopped engaging can quietly stop being a subscriber, and Chrome tells that person when it removes the permission.
Google also shared why it made the change: less than 1% of all notifications receive any interaction. In its testing, Google reports that sites sending fewer notifications saw their clicks go up. People can grant permission again by visiting the site and turning notifications back on, and Google says the feature does not remove permission for installed web apps.
Two rules, two scopes
What This Means for a Shopify Store
Both rules point the same way. Chrome rewards push notifications that people want and quietly works against ones they ignore. For a Shopify store this has three practical effects.
Your subscriber list can shrink on its own
If a shopper ignores your messages for long enough, Chrome may remove your permission for that person. A list that looks big on paper can be smaller in practice if many subscribers have stopped engaging. Sending more to win them back is the wrong move, because high volume with low engagement is exactly what both rules look for.
Every blast to the whole list carries more weight
Sending the same campaign to every subscriber, many times a week, is the pattern most likely to look disruptive. Messages that reach the right people, at the right moment, are the ones that earn clicks and visits, and visits are part of what Chrome measures.
How you ask matters as much as what you send
Because Chrome counts permission prompts against time spent on the site, a prompt that fires on every page view, for visitors who leave in seconds, works against you. Asking at a better moment, to visitors who are already engaged, keeps that measure in balance. From Chrome 155, Chrome on Android shows a lighter notification prompt that closes by itself if the shopper does not answer, and Google advises asking at a relevant moment rather than as soon as the page loads.
What to Do in Your Store
None of this needs new tools. It needs the kind of push marketing that already works best. Here is a short checklist:
- Lead with messages people expect. Abandoned cart reminders and welcome messages go to people who have just been on your store, so they are timely and relevant by nature. They are the backbone of a healthy push program.
- Use segments instead of sending to everyone. Send each campaign to the shoppers it actually fits, rather than to your whole subscriber list.
- Send fewer, better campaigns. Google's own testing found that sites sending fewer notifications saw clicks increase. Cut the weakest campaign of the week before you add a new one.
- Give each message a reason to click. A real offer, such as a discount in a cart reminder, earns more engagement than a generic "check out our store".
- Time your reminders. Send cart reminders while the shopper still remembers the product, and space them out rather than sending them all at once.
- Ask for permission at a sensible moment. Avoid prompting every visitor on arrival; ask once people have shown interest. In Firepush the opt-in prompt can wait for a set number of seconds or page views before it appears.
- Watch your click rates. If clicks on your campaigns fall week after week, slow down and look at what you send before Chrome does it for you.
- Plan big sales ahead. Do not wake up a quiet list with a burst of messages right before a sale. Keep a steady, useful rhythm in the weeks before so your audience is engaged when it counts.
Give each message a reason to click
Firepush already supports this way of working: cart reminders, delayed sending, discounts in reminders, welcome messages and segments are all part of the app. For more ideas on what to send, see these six examples of ecommerce push notifications.
Add free push notification app to Shopify
Get free Shopify push notificationsThe Short Version
- Chrome now limits push sending for sites that send many messages with little engagement, and most sites are not affected.
- A flagged site is held to a rate of no less than 1000 messages per minute, for one, seven or 14 days, and the count resets after 42 good days in a row.
- Chrome can also remove permission person by person when someone stops engaging.
- The fix is good push marketing: relevant, well timed, segmented messages, fewer blasts, and a polite permission prompt.
Stores that send pushes people want have little to worry about. The rule simply makes that the only kind of push marketing that keeps working.