Safe search for kids: what the settings actually do — and don't

There is a ritual to setting up a child's device: the parent opens the search settings, finds the safety option, switches it on, and feels the specific relief of a box checked. This article is about what actually happened in that moment — not to alarm, but because the vendors themselves document the answer, and a parent deserves to read the documentation the way it is written rather than the way the setup screen implies it.

The fine print, read aloud

Google's three modes are not what the toggle implies. SafeSearch has three states, per Google's own settings page: "Filter," which blocks all explicit results and is applied automatically when Google believes a user may be under 18; "Blur," which blurs explicit images while explicit text and links can still appear; and off. The detail that matters: Blur — not the strict mode — is the default for adults. A family device signed into a parent's account, out of the box, is in partially-covered mode. And Google states the mechanism's boundary plainly: it "only works on Google Search" — the result page is moderated; the web behind it is not Google's problem.

Bing's default is looser. Its "Strict" mode screens explicit text, images, and video; its default, "Moderate," screens "explicit images and videos, but not text." A child reading is a child exposed, in the default state, by design.

The lock is a network project. Making the strict modes mandatory — so a child can't simply flip the setting back — is not a checkbox: Google's official method is a DNS substitution (pointing google.com at forcesafesearch.google.com), Bing's the same (strict.bing.com), and the family-DNS services that automate this add the necessary corollary: block every alternate engine, encrypted-DNS resolver, and VPN, or the lock guards an empty room. The stack can be built — schools build it — and a parent should know that "turn on SafeSearch" was the first step of nine.

And the vendors hedge. Google's troubleshooting page: "no filter is 100% accurate." The parent guides echo it and recommend layering. The box you checked was real; it was also the thinnest layer of a system whose designers assume it leaks.

“"Turn on SafeSearch" is step one of nine — and the vendors' own fine print assumes the system leaks.”

kolbo.life

What parents actually do about it

The honest playbook on general-market devices, in rising order of strength: check the actual mode (strict, not blur/moderate — on every browser, every profile, every device); lock it at the network with a family-DNS service and accept the whole-stack maintenance that entails; add the kids' engines (Kiddle, KidzSearch) for school research while remembering they are sandboxes beside the open web, not replacements for it; and put the deeper enforcement below the apps — on any iPhone or Android, KolBo Secure runs device-policy-level protection with AI sight protection that screens "images, video, and text in real time... at the level of what the eyes see — not just which sites load," from $14.99/month. That last layer answers the fine print's biggest hole: screening what renders, not just what the results page lists.

The design that retires the ritual

Every step above shares the era's assumption: the engine is unsafe, so contain it. The alternative is categorical — a results page that is clean because the index and ranking are built that way, by a builder answerable to this community. That is the homepage's claim for KolBo Search: "not a filtered feed sitting on someone else's index — our own engine, built on open sources, returning clean, relevant results tuned for how this community actually searches" — shipped as the native front door of the KolBo device layer, beside a browser whose protection is compiled in. For a child, that is the difference between search-with-supervision and search that has nothing to supervise: no mode to flip back, because there is no other mode; no lock to maintain, because there is no unsafe state to lock away. The checkbox ritual served its era. Its era is the thing ending.

Frequently asked questions