How to block websites on a child's Chromebook (2026 guide)

Most website-blocking questions from parents are really ChromeOS questions, since Chromebooks are the dominant student laptop in the U.S. — an estimated 93% of districts planned more purchases in 2025, according to industry purchasing data. A workable setup combines ChromeOS's own supervision tools, a browser extension for focus schedules, and a plan for what happens if the device goes offline.

Why does a Chromebook need its own approach to blocking?

ChromeOS is not Windows, and the ecosystem of tools around it works differently. Some controls ship natively in Chrome; others need a personal Google Account or a school-managed one; and a school-issued device is usually locked down by the school itself, not the family.

That last distinction matters more than it looks. A personally-owned Chromebook — the one bought for home use, signed in with a family Google Account — can be supervised the way any Android phone or tablet can, through Family Link. A school-issued Chromebook, by contrast, is enrolled in the school's Google Admin console, and a parent generally cannot layer extra restrictions on top of school-level management. Given how common Chromebooks are in classrooms, most households end up managing two different categories of device: the school's, and the family's own. The rest of this guide focuses on what a parent can actually control — a Chromebook the family owns.

What do ChromeOS's built-in blocking tools cover?

Family Link, Google's free parental-control layer, can supervise a personal Chromebook running ChromeOS 71 or newer. From the "Manage sites, content & apps" section, a parent can block or approve individual websites in Chrome, restrict explicit content, and control which apps a child can install.

It has real limits worth knowing before relying on it as the whole plan. Google's own device-compatibility documentation notes that location reporting is not available for a supervised Chromebook, unlike a supervised phone. More importantly for a mixed-device household, that same supervision does not extend to Windows, Mac, or Linux computers — a child signed into a family Google Account on a Windows laptop can use most of that account's features with little of Family Link's actual enforcement. A family with both a Chromebook and a Windows PC at home will hit that gap directly (a full comparison of alternatives that cover both is worth reading separately, see Google Family Link alternatives for Windows and Chromebook).

How does a browser extension add a focus schedule on top of that?

A browser extension installed on the child's Chrome profile can do something Family Link's website controls do not: enforce a schedule rather than a permanent list. Instead of a handful of sites being blocked around the clock, the same sites are closed off only during agreed windows — after school, during a homework hour — and open the rest of the time.

That distinction changes how a block list gets used day to day. An always-on list tends to get relaxed the first time it is inconvenient, because there is no natural moment to reconsider it. A scheduled list resets itself: the restriction is tied to a time window everyone already expects, not to a standing rule that has to be actively enforced or renegotiated. Pairing a schedule with a simple request flow — where a child can ask for a specific site to be unblocked for a school project, and a parent approves or declines it — keeps the system from turning into a constant point of friction. Details of that approach are covered on the features page.

What happens if the Chromebook goes offline, or a child disables the block?

Any browser-based blocking tool, including a Chrome extension, can in principle be removed by anyone who can reach the extensions page or reset the browser profile. That is true of every product in this category, and an honest one says so rather than claiming to be unbreakable.

What matters more in practice is what happens next. A tool that simply goes silent when disabled is not much use — a parent has no way to know the block stopped working until something else tips them off. A better design flags a stale check-in: if the device has not reported in for longer than expected, the dashboard shows that clearly, so a parent notices the gap and can have a direct conversation rather than trusting a false sense of lock-down. This matters more than it might seem, since classroom-level digital distraction is already a documented concern — 72% of U.S. high school teachers say students being distracted by cellphones is a major problem in their classroom, according to Pew Research Center. The same dynamic plays out at home on a laptop, which is exactly why a reliable check-in signal matters more than a claim of being unbreakable.

What does a workable Chromebook blocking routine look like?

A routine that survives more than a week tends to share a few traits. It helps to remember how much of the day is already screen time before adding more rules on top: among 11-to-17-year-olds with smartphones, phone use during the school day alone runs to a median of 43 minutes, according to Pew Research Center's 2024 teens-and-technology report — a schedule that fits around an already-busy day works better than one that fights it.

• A small, agreed block list. A handful of sites that reliably derail homework, chosen together rather than imposed — long, all-purpose block lists are harder to keep and easier to resent.
• A schedule, not a permanent switch. Restrictions tied to a specific window (say, 3:30–5:30pm on school days) rather than blocked forever.
• A request path. A way for a child to ask for a specific exception without it becoming a negotiation every time.
• An honest status signal. A clear indicator when the device has not checked in, instead of silence.
• A weekly look, not constant monitoring. A short summary of how the week went is usually enough; a full browsing history is not necessary and raises its own privacy questions.

For a step-by-step walkthrough of setting this up, see how StudyLock works, or start directly from the setup page.