How to block notifications from a site in Chrome on Mac: steps for current Chrome

Three places to block notifications on your Mac

Chrome gives you three places to stop notifications, and each one works at a different level. The site info menu handles one site while you have it open. Chrome settings reach any site, including ones you are not visiting right now. macOS controls the whole Chrome app, so it can silence every alert Chrome sends.

Block one site from the address bar

This is the fastest route when the annoying site is already open. Load the page, then click View site information on the left end of the address bar. Beside Notifications, open the dropdown and choose Block. From then on, that site loses its notification permission in Chrome on this Mac.

The control sits next to the address, not inside Chrome's three-dot menu. It is easy to look in the menu first, but the setting lives here.

A block applies to the exact address you loaded. If the alerts keep coming, check which address they come from and repeat the steps for that address.

Block a site from Chrome settings when it is closed

Use settings when the site is closed, or when you want to block a site you have not visited for a while. Open the three-dot More menu at the top right, then choose Settings. Go to Privacy and security, then Site settings, then Notifications. This page holds the lists that control what Chrome allows.

Under Not allowed to send notifications, click Add. Type the address of the site, then click Add again. The site now sits in that list. You can remove it from the same list later.

Type the main address of the site, such as news.example.com, which is only a placeholder here. Then reload a page from that site and watch for the prompt to stop.

Change the default for every site

The default decides what happens when a site asks for permission. Google's help page lists Allow sites to ask as the default, with a choice to use quieter messaging. Quieter messaging lets sites ask without a pop-up. A bell icon appears in the address bar when a site does this.

Setapp's 2026 guide describes three options instead: sites may send notifications, sites may not, or sites may use quieter messaging. The labels differ between sources, so read the choices on your screen. If prompts annoy you most, pick the option that does not let sites send notifications.

Changing the default does not reset sites you already approved. If one of them keeps sending alerts, find its entry in the lists and block it directly. Blocking the site is the surest way to stop it.

Turn off Chrome notifications at the macOS level

Use this route when you want Chrome to stop every notification from the app. Apple's steps live in System Settings, not in Chrome. Choose Apple menu > System Settings, then click Notifications in the sidebar. Scroll down if you do not see Application Notifications, then open it and click Google Chrome.

Turn off Allow notifications, and macOS stops showing Chrome alerts. That covers every site, not just one. Chrome settings and System Settings are separate, so check both when a block does not seem to work.

Apple's page shows these steps for macOS 27 Golden Gate. The version selector also lists macOS Tahoe 26 and Sequoia 15, but the page does not say whether the steps differ. If your window looks different, use the version selector on Apple's page to match your system.

If you keep notifications on, choose an alert style. Apple lists None, Banners, and Alerts. Banners disappear after a while. Alerts stay on screen until you dismiss them. A quieter style is an easy step before you block Chrome outright.

Why blocking is worth the minute it takes

Notification prompts make up a large share of what Chrome asks you. Google Research reports that 74% of all Chrome permission prompts are about notifications. In its 2021 study, notification prompts were granted 10% of the time on desktop and 21% on Android.

A low grant rate means most people say no to these prompts. Google's study also tested a quieter prompt design. That design produced up to 30% fewer unnecessary actions on the prompts.

Edge cases and mistakes people make

Most failed blocks come from a few common slips. Check this list before you decide the block did not work.

• Blocking the wrong address. A similar site name can be a different entry. Read the address bar before you click Block.
• Changing only the default. A site you already approved can keep sending alerts until you block it directly.
• Assuming Chrome settings control macOS. Chrome settings and System Settings are separate, so changing one does not change the other.
• Still getting messages after you turned off pop-ups. Google's pop-up help says you may be subscribed to notifications. Unsubscribe on the site itself if it offers that option.
• Missing a permission Chrome removed. Chrome may remove permissions for sites you have not used for a while. Those removals are listed under Permissions removed.

Blocking one site does not change the others, so you can work through a list one site at a time. Start with the sites that interrupt you most often.

Check that the block worked

Reload the site and wait for the page to finish loading. If the site asks for permission again, the block did not apply to that address. Open View site information and confirm that Notifications reads Block.

Then open the Notifications list in Chrome settings. Blocked sites appear under Not allowed to send notifications. A short list is the goal, so review it every few months and remove any site you no longer need to block.

Choose block, quiet, or allow for each site

Blocking suits sites that send promotions and rarely show you anything useful. Quieter messaging suits a site you use but do not want pop-ups from. Allow fits tools you rely on every day, such as a web chat or a calendar in the browser.

A simple test helps. If you cannot remember the last time an alert from a site helped you, block it. You can change the setting back from the same panel, so a wrong choice is cheap to fix.

Which Chrome version this guide covers

Wikipedia lists 157.0.8103.39 as the current stable Chrome release for Windows and macOS. It is dated 3 November 2026. Google's own release post was not readable when this page was checked, so confirm the version against Google's channels before you rely on it.

Google's help pages do not name a version. The Setapp guide does not state which Chrome or macOS version it tested either. The menu names here come from those pages, so a later update could rename a label.

Related privacy settings to check next

Notifications are one kind of permission. Cookies are another. If you also want to limit tracking, read How to block third-party cookies in Chrome on Mac. It covers the settings path and per-site fixes.

If you want to clear the site data that builds up over time, read How to clear browsing data in Chrome on Mac. That is a separate job from blocking alerts, so treat it on its own.

If a block does not stick

Collect three details before you ask for help: the site address from the address bar, your Chrome version, and whether the alerts come from Chrome or from macOS. Those three details narrow the cause fast.

Then go back through the troubleshooting list. Often the cause is a second place where the site still has permission, so check the Chrome lists and the macOS switch together.