If you've ever opened Safari, blocked a site, and then found yourself back on it a minute later, the problem probably wasn't the website. It was the switch sitting one tap away in Screen Time.
That's the part many users overlook when they look up how to block a certain website on Safari. Safari has settings, yes, but the primary control point is Apple's system-level restriction layer, not the browser itself, and Apple's current guidance routes website blocking through Content & Privacy Restrictions and Web Content on iPhone, iPad, and Mac (Apple support for iPhone website blocking). If you don't set a Screen Time passcode, the block is easy to remove from the same settings area in seconds (Apple's iPhone guide).
Why Safari Itself Is Not the Control Point
Safari looks like the obvious place to start. It's where the site loads, so it feels like it should be where the site gets blocked. That instinct wastes time.
Safari's own website settings are for permissions, not blacklists. On Mac, Apple documents Safari's Websites settings for things like camera, location, notifications, and downloads, while the broader content block lives in Screen Time under Content & Privacy Restrictions and Web Content (Apple Safari Websites settings on Mac). That's the practical distinction. One controls what a site can ask for. The other can stop the site from loading at all.
The real lever is Screen Time
Apple's support flow on iPhone and iPad starts with Settings > Screen Time > Content & Privacy Restrictions > Web Content. From there, you choose the content mode and manage site access at the system level, not inside Safari itself (Apple's iPhone support guide). On Mac, Apple points users to System Settings > Screen Time > Content & Privacy > Content Restrictions > Web Content for the same job (Apple Safari guide on Mac).
That shift matters because it changes what you're fighting. You're not trying to outsmart a browser menu. You're setting a device policy.
Practical rule: if you're still clicking around inside Safari's menus, you're in the wrong place.
The last thing to set early is the passcode. Apple's own guidance makes the point bluntly, without a passcode, the restriction can be removed from Settings just as fast as it was added (Apple's iPhone guide). That's why the passcode isn't an extra step. It's the thing that turns a preference into friction.
Blocking a Specific Site on iPhone and iPad
On iPhone and iPad, the clean path is the one Apple already documents. Open Settings, tap Screen Time, turn it on if needed, then set a Screen Time passcode that isn't the same as the device passcode. After that, go into Content & Privacy Restrictions, switch it on, and open Web Content (Apple's iPhone support guide).
Use the exact domain, not a vague idea
For a single site, choose Never Allow and add the exact domain in the field Apple provides. Apple's workflow supports adding sites under Never Allow or Allowed Websites, and that URL-level control is the precise part of the feature for one-site blocking (Apple support documentation). If you type a general term instead of a domain, you'll get a mess. If you block the wrong variant, the site may still open through a different address.
The block page in Safari is generic. You won't get a custom warning or a friendly note to yourself. You'll just hit the restriction and stop.
What usually trips people up
The first trap is assuming one entry covers every way a site can be reached. Apple's guidance and related documentation make clear that website limits can apply across browsers and even in-app browsers, which is useful, but it also means you need to be precise with the domain you add (Apple support guidance). The second trap is the passcode. Without it, the block is easy to undo from the same settings path.
If you've ever turned the restriction off in a weak moment, that's not a moral failure. It's a weak setup. The difference between “blocked” and “blocked long enough to matter” is usually whether the passcode lives in your head, not on the lock screen.
Blocking a Specific Site on Mac
On Mac, don't go hunting for a secret Safari blacklist. Apple's route is still Screen Time, just in a different shell. On recent macOS versions, that means System Settings > Screen Time > Content & Privacy > Content Restrictions > Web Content. Apple's Safari documentation on Mac keeps the same separation clear, Safari's Websites pane handles site permissions, while Screen Time handles broader content blocking (Apple Safari guide on Mac).
The Mac path is the same idea with different labels
Once Content & Privacy Restrictions is on, choose the web-content mode and move into the block list. Apple's current web-content modes include Unrestricted Access, Limit Adult Websites, and Allowed Websites Only in the broader Screen Time framework, and the site-specific block lives in the control area tied to Web Content (Apple support for iPhone website blocking). The mechanics are different from Safari's own settings, but the logic is the same. You're setting policy at the system layer.
A passcode matters just as much on Mac. Apple's guidance around Screen Time and Safari makes the same basic point, the restriction only holds if someone can't casually remove it from the same account settings (Apple Safari guide on Mac).
Don't confuse Safari permissions with blocking
Safari's Websites section on Mac is for permissions like camera, location, and notifications. That's useful, but it doesn't give you a clean website blacklist. If you stay in that pane, you're managing access requests, not preventing navigation.
On Apple devices signed into the same account, the web restriction can carry across them through the same Screen Time framework, which is why a blocked domain on one device often shows up on the others. That's convenient when you want the block to follow you. It's annoying when you were hoping to only close one doorway.
Picking the Right Content Mode in Web Content
The mode you choose matters as much as the site you type in. Apple gives you Never Allow, Limit Adult Websites, and Allowed Websites Only in the Web Content area, and they behave very differently (Apple's iPhone support guide).
Use the least broad mode that still does the job
For blocking one specific site, Never Allow is the correct choice. It gives you a targeted deny list and leaves the rest of the web alone. That's what you want if the goal is to stop one distraction, not rework the whole internet in your house.
Limit Adult Websites is broader and more category-driven. It can catch things you didn't mean to block, and it can miss the exact site you care about. Allowed Websites Only flips everything into a whitelist, which is useful in tightly controlled setups, but it's heavy for most home use because you have to keep adding every domain you want available.
| Mode | Scope | Best For | Setup Complexity |
|---|---|---|---|
| Never Allow | Blocks specific sites you name | One site or a small list | Low |
| Limit Adult Websites | Apple-managed filtering with exceptions | General content filtering | Medium |
| Allowed Websites Only | Only approved sites load | Tight whitelisting | High |
Add the exact domain once you pick the mode
Apple's support flow lets you add sites directly in the Web Content area, including under Never Allow (Apple support documentation). The important part is precision. Enter the exact domain, not a search phrase, and don't assume one variation covers every route into the service.
If you choose the wrong mode first, switch it before you build a list around it. Otherwise you'll end up with a restriction that's broader than you wanted or narrower than you thought.
Why the Block Disappears in Five Seconds
Most failed blocks fail for a boring reason. Somebody can still reach the settings that remove them.
Passcode friction is the difference-maker
Apple's own guidance is direct, if Screen Time doesn't have a passcode, the restriction can be turned off from Settings (Apple's iPhone support guide). That's why people think the block “didn't work,” when the underlying problem is that the block had no guardrail.
A separate Screen Time passcode raises the cost of an impulsive removal. It doesn't make the setting mystical. It just makes the easy exit less available.
Exact URLs matter more than people expect
The other quiet failure mode is domain variation. Apple's website controls are URL-based, and that means the exact string you enter matters. If you only block one host, another variant can still be reachable unless you add it too. That's not a bug, it's how the control is structured.
Shared accounts add another layer of friction. If several people use the same Apple account, they're operating inside the same trust boundary. That's fine in a family setup where everyone agrees, but it makes casual bypass easier if the passcode is widely known.
A block that can be reversed by memory alone usually gets reversed.
The short version is simple. The website isn't the hard part. The settings access is.
Going Beyond Safari With Router Level Blocks
When the device setting won't stay put, the next layer sits outside the device. A router-level block lets you filter a site at the network level, so the restriction isn't living inside Safari or even inside the operating system.
Where this makes sense
Consumer routers often include parental controls or access restrictions. That's the place to look if you want the block to apply to every browser on the network instead of just Safari. It's also the place people go when a Screen Time block gets undone or when multiple devices need the same restriction.
Some routers also support device-based filtering, including MAC address filtering. That lets you aim the restriction at one device instead of the whole network, which is useful if only one iPhone or Mac needs the lock.
The limits are real
Router controls are stronger in one way and weaker in others. They don't travel with the phone when it leaves your Wi-Fi, so mobile data can slip around them. They also take more technical comfort than a Screen Time setting, and the interface varies a lot by router.
Practical rule: use router filtering when you want the block to live outside the device, not when you need something quick before dinner.
Apple's own device controls are still the first place to try for a single-site block on Safari. But if you need a wider net, the router is the cleaner backstop.
If you want the same kind of friction on Android, TiedSiren is built around a committed session that holds you to the choice you made up front. It blocks the Android Settings screen during a running session, which is useful when the problem is the quick undo at the moment of weakness.
Enhanced by the Outrank tool