Push has a spam folder now

The week I stopped blaming the headline

For a few years my Monday started with a number. A six-figure list of browser subscribers, on a dashboard, and the first thing I did was compare it to last Monday. The list shrank most weeks. Never dramatically. Enough that after a quarter you had a hole you could not explain in a meeting.

I blamed the headlines first. Then the send times. Then where the permission prompt sat on the article page. I rewrote a lot of copy for a problem that was not living in the copy.

What the browsers did while we argued about headlines

In October 2025 Chrome said it automatically removes notification permission for sites a user has not interacted with recently, when engagement is very low and notification volume is high. Chrome informs the user. The user can re-grant permission in Safety Check or on the site, or turn auto-revocation off. Installed web apps are not revoked by this feature. Desktop and Android.

Three months later the second piece landed. In January 2026 Chrome began rolling out Push API rate limits for sites that send many notifications with little site engagement. A site judged disruptive is limited to no less than 1,000 messages per minute, and requests above that come back as HTTP 429. The daily factors Chrome names are push messages per time on site, permission prompts per time on site, and engagement. The block escalates: one day, then seven, then fourteen. It resets after 42 consecutive non-disruptive days. This applies to the Push API only, not the Notifications API, and Chrome states nearly all websites will be unaffected.

Then on 11 August this year Chrome Security published the shape of the whole system. Auto-revocation for low engagement and for sites with repeated suspicious-notification warnings. Behavioral detection of coordinated abuse networks. Server-side rate limits in FCM, the same 1,000 per minute for disruptive domains. And a streamlined permission model that includes one-tap unsubscribe on Android. Whatever gets revoked is something the user can review in Safety Hub.

Safari came at it from a different angle. Declarative Web Push shipped with Safari 18.4 on 31 March 2025, for Home Screen web apps on iOS and iPadOS. A site can request a subscription and show a user-visible notification from a standardized JSON payload, with no installed service worker in the loop. It is more energy-efficient and private by design, and it stays backwards compatible with original Web Push. Apple's reason there is battery and privacy rather than abuse, but the effect on a sender is similar. More of the mechanics belong to the platform now.

Read in order, those stop looking like separate announcements. That is a channel growing an immune system in public, on a schedule.

The phrase is ours

We say push has a spam folder now. That is our metaphor for what those actions add up to. It is not a Chrome feature and not a name anyone at Google gave anything. There is no folder to open, no place a message goes to sit. If a vendor tells you their tool keeps you out of the push spam folder, ask them which screen it is on.

The metaphor earns its keep for one reason. It makes people behave correctly. Email teams already know how this ends. When volume stopped matching value the inbox providers built filters, and being a sender turned into a job with a reputation attached to it. Web push spent a decade without that layer. Now it has one, built by the browsers, and it does not care how good your CMS integration is.

The number I wish I had a decade ago

Chrome states that less than 1% of all notifications receive any interaction from users.

I would have printed that and taped it to the wall of every planning meeting I sat in. Not to win the argument about one story. To make the base rate visible. Ninety-nine out of a hundred of these things are wallpaper, and each of them still spends something: a bit of permission, and a bit of whatever patience a reader has left for you.

Why I think this is good news

If your plan was volume, the browsers just repriced your plan. If your plan was judgment, the floor under you rose, and a chunk of the noise you were competing with is now being throttled by somebody else's infrastructure.

Notification fatigue used to be a thing people asserted in meetings without being able to price it. It has a price now, and the price has dates on it. That is the assumption the product runs on. A Nudge is the message that survives the question of whether it should have been sent at all, and the work I find interesting is in the ones you hold back.

Where I would look this week

Take your last 30 days and split the sends by whether the person had opened anything from you in the two weeks before. Then ask what you sent to the other group, and what you got back for it. If your tool cannot answer that, the gap is the finding, and it was there long before any of this shipped.