How to block websites on Chrome

Nudge works well when Chrome is both useful and dangerous. You may need Chrome for docs, dashboards, localhost, research, billing, or admin work. That does not mean every Chrome tab should remain available.

1. Create a Nudge preset for the work mode, such as Coding, Writing, Study, or Admin.
2. Keep Chrome available if the session needs browser access.
3. Add distracting domains to the blocked websites list.
4. Keep the apps that belong in the session, and leave non-work apps out.
5. Start the preset from the menu bar when the block begins.

This is the cleanest answer for Mac users because the rule follows the work session, not just the browser. Chrome can remain a tool without becoming the path back into every distracting site.

Chrome lets you allow or deny permissions for a specific site without changing default settings globally. This is useful for removing distraction channels like notifications, pop-ups, redirects, sound, intrusive ads, and other permissions.

1. Open Chrome.
2. Go to the site you want to change.
3. Click the icon next to the web address.
4. Open site settings or permissions.
5. Set noisy permissions like Notifications, Pop-ups and redirects, Sound, and Ads to Block where appropriate.

This does not stop you from typing the URL and visiting the site. It removes specific behaviors that make the site more disruptive.

Chrome blocks many pop-ups by default, and you can manage pop-ups and redirects from Settings, Privacy and security, Site Settings, Pop-ups and redirects. You can also block pop-ups for a specific site and use the pattern [*.]example.com when you need to cover subdomains.

Notifications deserve separate attention. If a distracting site can still reach you through browser notifications, open the site's permissions and set Notifications to Block. This is often the fastest win for news sites, social sites, forums, and web apps that keep pulling attention back.

The limitation is simple: pop-up and notification blocking reduces interruptions. It does not create a protected work mode.

A Chrome blocker extension can be the right answer if you want a browser-only blocklist. It can block specific URLs, categories, or schedules depending on the extension. That is enough for some people.

The weakness is scope. An extension may not protect Safari, another browser, desktop apps, or the broader Mac workflow. It also may be easier to disable than a dedicated focus app. If the distraction problem is bigger than Chrome, use Nudge or another system-level method instead.

Screen Time can create app and website limits, and Content & Privacy settings can restrict web access. This is useful as a built-in baseline, especially when you do not want to install another app.

The hosts file is more manual. It can block domains at the system level, but it is awkward to toggle for different work modes and easy to manage badly. Use it only if you are comfortable editing system files.

For a fuller Mac walkthrough, use the broader guide: How to block websites on Mac.

What should you use?

Use Chrome settings when you only need to quiet a site. Use a Chrome extension when the problem is a browser-only blocklist. Use Screen Time or hosts rules when you want a broader Mac baseline.

Use Nudge when Chrome is part of focused work, but specific sites are not. That is the common Mac productivity problem: the browser is necessary, but not every website should be available during the session.

FAQ