Choose one primary managed browser, connect it to the correct child account, configure the platform-supported controls, reduce unmanaged alternate routes, and create a site-request process.
Why this decision matters
Web access is where phone and computer controls meet an open-ended system. A filter can help, but predictable account structure, browser choice, child understanding, and regular review do more work than a long block list alone.
A practical starting sequence
Choose the managed route
Use the browser supported by the family-control system and make the child’s profile obvious.
Audit the edges
Check other browsers, guest profiles, private windows, VPNs, extensions, downloads, in-app browsers, and school accounts.
Build the request loop
Test one allowed site, one blocked site, one false positive, and the parent response process.
What the child experiences
The child should know which browser and profile to use, why a site may be blocked, and how to request access without hiding the destination.
Filters make browsing boundaries more deliberate; they cannot assess every page, image, message, or intent. False positives and false negatives are normal operational risks.
When to review it
Review the browser monthly at first and whenever a new browser, extension, VPN, school account, or unexplained browsing route appears.
Use the complete browser audit
The Browser Safety Guide turns this framework into a device-by-device review with exact checks and gaps.
Current official sources
Interfaces and defaults change. These first-party sources were checked for this page; verify the live device before publishing or relying on an exact menu path.
- Google: Manage Chrome with Family Link
- Microsoft: Filter websites and searches
- Apple: Use Screen Time for a child