Safe Search

On your panel it is a single row: safe search, on or off, per child. Underneath it sits the video row, which does the same thing for restricted mode. There are no sliders, no strictness levels, and no per-engine sub-menus, because search providers only really offer one meaningful state and pretending otherwise would be theatre.

What makes the parent version different from the one inside the search engine is that it is held. A setting your child can reach in a menu is a preference. A setting applied from the phone’s management layer, that reasserts itself if something tries to change it, is a rule. The row on your panel shows which of those two you have, and if enforcement drops for any reason the state indicator says so rather than continuing to show a comfortable green tick.

It applies across the phone, not inside one app. The default browser, a second browser installed later, the search box on the home screen, the search widget inside the assistant: they all resolve through the same enforced setting. This is the difference between fixing one app and fixing a device, and it is the reason a parent-held switch survives a child installing a different browser on a wet Sunday.

Every major search engine puts its filter in a settings menu two taps from the results page, and that is entirely reasonable for an adult. It becomes a problem the moment the person you are protecting is also the person with the menu. Nothing has to be hacked and nothing has to be researched. The switch is right there, and turning it off takes less effort than turning it on did.

The second failure mode is quieter and catches families who did everything right. The setting is often stored per browser, per profile, or in a cookie, so it disappears when the cache is cleared, when a private window is opened, when the child signs into a different account, or when a new browser is installed. Parents report having set it three times without ever remembering turning it off, and they are usually telling the truth.

Holding it from the parent side removes both problems at once. The state does not live in a cookie, it is not attached to one browser profile, and it is not reachable from inside the search app. Your child can still see that it is on, because it is listed in their app with your name against it, but seeing a rule and being able to switch it off are very different things.

Restricted mode is the video equivalent of safe search. It hides content the platform’s own systems have flagged as mature, and it also hides comments, which for many parents is the more valuable half. Like safe search it is a per-account, per-browser setting by default, and like safe search it holds properly only when applied from outside the app where a child cannot reach it.

YouTube proper with restricted mode on is a reasonable setting for a secondary school child. It leaves most of the platform available, removes the obviously mature material, and closes the comment sections that turn a music video into something else. It is a filter on an adult product rather than a children’s product, and it should be understood that way.

YouTube Kids is a different product with a different catalogue, an age band you choose, and a much smaller pool of videos. For a child under about nine it is usually the better answer, and the honest way to run it is to make it the only video app on the phone rather than one option among several. Two video apps on the same device means the restricted one gets used when an adult is watching and the other one the rest of the time.

Neither platform’s filter is perfect, and both rely partly on how uploaders label their own content. Restricted mode reduces exposure substantially. It does not promise a curated library, and any product that claims a video platform can be made completely safe by one switch is overselling.

This is the single most misunderstood thing in this area, so it is worth being blunt. Safe search filters what a search engine chooses to show. If your child never uses a search engine to reach a site, the setting is simply not involved. A link pasted by a friend, an address typed from memory, a tap inside a game, a redirect from an advert, a QR code on a poster: none of these pass through a results page and none of them can be filtered by a search setting.

Category filtering is what covers that gap, because it acts on the address itself at the moment the phone requests it, regardless of how the child arrived at it. The two tools overlap barely at all. Safe search cleans up the results a child sees while looking for something ordinary. Filtering stops the destination when they have a direct route to it.

Run together they cover most realistic paths. Run alone, each has a shape of failure that is easy to describe: safe search on its own is defeated by a shared link, and filtering on its own leaves image and video results on a search page technically allowed even when they are not what you want a nine year old scrolling through.

That is why both live on the same panel page, and why the setup below turns them on in the same pass. It takes one extra tap to do both and it roughly doubles what you are actually covering.

It misses anything with its own search box. A social app, a video app, an image board or a messaging app runs its own search inside itself, and the phone’s safe search setting has no influence there. Some of those apps have their own restricted settings worth turning on individually, and some have none at all, which is a genuine argument for app-level rules rather than for tuning search harder.

It misses images and video that are not labelled as mature by the platform, and it misses text on ordinary sites entirely. Safe search is a filter on obviously explicit material. It is not a judgement about whether an article, a forum thread, or a discussion is right for a twelve year old, and it does not try to be.

Then there is autoplay, which is the problem no filter really solves. A child watches one perfectly harmless video, the platform queues a related one, then another, and forty minutes later they are somewhere no individual step would have predicted. Nothing in the chain is explicit, so nothing is blocked, and the drift happens through recommendation rather than through search. Restricted mode trims the worst of what can enter that queue, but the mechanism itself is intact.

The practical answers to autoplay are not filters. Turn autoplay off in the video app itself, use a screen time budget so the session has an end, and put video apps inside a bedtime routine so the queue stops when the evening does. A rabbit hole with a time limit is a very different thing from an open-ended one.