How to Block Websites on a Child's Android Phone With Family Link
Block websites on a child's Android phone with Family Link. Learn which settings to choose, how to test a block, and why app access needs a separate check.
Documentation-based guide · Official sources checked October 4, 2026 · Not a hands-on product test
In this guide
To block a website on a child's supervised Android phone, open Family Link, select the child, and go to Controls → Google Chrome and Web. Add the address to the blocked-sites list. This is a documented option for supervised Chrome browsing and some Android apps, not a guarantee that every app on the phone is filtered.
This guide covers a child's account managed with Family Link. It is not an adult self-control setup or an iPhone tutorial. Instructions summarize Google documentation; Kinlumo has not tested them on a device.
Decide what you need to restrict
Before choosing a setting, write down the problem:
| Your goal | Approach to examine |
|---|---|
| Block one distracting website | A specific blocked-site entry |
| Limit browsing to a small approved collection | The approved-sites-only option |
| Reduce exposure to explicit websites | Google's explicit-site filter, with its limitations |
| Stop access to a particular installed app | App controls, checked separately |
A website address and an app icon can lead to the same service through different paths. Define the intended result before assuming one rule covers both.
Add a website block
Google's current instructions are:
- Open Family Link and select your child.
- Go to Controls → Google Chrome and Web.
- Under Manage sites, open the approved/blocked-sites controls.
- Select Add a website and add the address as a blocked entry.
Google distinguishes specific website entries from broader domain entries. A rule for one website does not necessarily cover differently named hosts. Check the address carefully and use Google's explanation when choosing the scope. Menu wording may vary as the app changes. Google's website-control instructions
Test the result instead of adding more rules
These are Kinlumo's suggested checks:
- On the child's supervised phone, open the exact address you intended to block.
- Check an ordinary school or reference site that should remain available.
- Record whether the rule blocks only the intended site or also something needed.
- Review the exception process with your child before the next homework session.
If a site remains accessible, compare the address in the browser with the entry in Family Link. Also confirm you selected the right child and device context. Do not assume a failed test means the child has changed anything.
Check installed apps separately
Family Link also has app-management controls for supported devices. Google documents blocking, allowing, and limiting eligible apps; some apps cannot be blocked or limited in the same way as others. Review the relevant app in the child's controls if your aim includes the installed app rather than only its website. Google's app-management help
A useful final check is to test the website and app as two separate items. Write “website blocked” and “app behavior checked” on your setup notes, rather than one vague “service blocked” statement.
Choose a rule you can maintain
For a younger child with a small set of school websites, an approved list may be easier to explain. For a teenager, individual rules can make the purpose more concrete. These are editorial suggestions, not age-based product guarantees.
Schedule a review after the next school week. Did a rule interrupt research, a class link, or an accessibility tool? If so, narrow it. A block is more useful when the family knows its purpose and how to request a reasonable exception.
Common questions
Does Family Link block every inappropriate page?
No. Google explicitly says its filter is imperfect. Treat filtering as one part of a plan that includes talking about unexpected content and asking for help. Official scope and limitations
Do I need another paid app first?
Start by checking whether Family Link's documented controls solve your specific problem. If they do not, list the missing capability before comparing paid options; paying is not itself a test of coverage.
Will blocking a website stop the same service's app?
Do not assume so. Check both access paths and the separate app controls. The pass condition is the behavior on your actual supervised device.
Read what Android parental controls can do for account and device context. If you need more than website rules, see Qustodio vs Bark for Android.
Kinlumo is not affiliated with Google.