How to Make School Chromebooks Safe

Published: September 8, 2026. Updated: October 2026 by Andrew Apell, who builds PureWord and previously built Flookup Data Wrangler

Quick Answer

Short answer: Most schools filter which sites pupils may open but nothing cleans the words on the sites that stay open. To make school Chromebooks safe, compare the three layers below, keep the two you have and add on page text filtering with a forced install by organisational unit. Pupils cannot remove a forced extension.

A classroom set of Chromebooks looks controlled. The Admin console blocks categories, search runs through SafeSearch and the devices reset on logout. Then a pupil opens an allowed video and the comments below carry language no teacher would permit in the room. The school filtered places while nobody filtered words.

This guide compares the layers available to schools, recommends a combination for primary and secondary classrooms and explains deployment through forced installation. It is written for teachers and IT administrators rather than parents, so it covers a whole organisational rollout instead of a single device.

Compare the Three Layers

No single layer covers a classroom. Each owns a different part of the problem, and the gaps close only when the layers combine. The table compares them on what each blocks, what each misses and what each costs a school.

One note on reading it: this compares what each layer is designed to do, taken from Google's own Admin console documentation, not a product test or a benchmark. Nothing here was measured on a school network. What the table cannot tell you is how your own pupils respond to each layer, which is the part worth testing yourself before you commit a rollout.

Layer What it blocks What it misses Cost and effort
Admin console web filtering Whole sites and categories by organisational unit Language on allowed sites, including comments and forums Included with Google Workspace for Education. Admin time only.
DNS filtering Domains at the network level, on and off site Page content and anything on permitted domains Low per device cost with a subscription service. Network configuration required.
On page text filtering with PureWord Words on every allowed page, including evasions and inflections Whole site access, spoken audio and mobile apps Free extension. Forced install by organisational unit takes minutes.

The judgement is straightforward. A school with the first two layers still shows pupils unfiltered words every day, because comments, forums and search snippets live on allowed domains. The third layer is the cheapest to add and it covers precisely the gap the others leave open. Nothing here replaces supervision, but supervision stops working at thirty screens per teacher without tooling.

Deploy with Forced Installation

Google Workspace for Education supports forced installation of Chrome extensions by organisational unit. Add PureWord to the forced list for the pupil units and it installs on every managed Chromebook automatically. Pupils cannot disable or remove a forced extension, which removes the failure mode where a filter works until a curious pupil switches it off.

Use separate organisational units for primary and secondary years if your console is arranged that way. The extension itself runs with no account and no analytics, so there is nothing for pupils to sign into and no browsing data leaves the device. See the privacy policy for the full statement, which matters for school data reviews.

Roll It Out, Step by Step

  1. Sign in to the Admin console with an account that can manage Chrome policy for the unit. A delegated administrator limited to devices is enough, and it keeps the rollout away from accounts and mail settings.
  2. Select the organisational unit holding the pupil devices. If primary and secondary are separate units, start with one rather than the whole school, so a mistake reaches a single year group.
  3. Open the Chrome apps and extensions settings for that unit and add the extension to the forced installation list. Forced installation is the difference between a filter that exists and a filter that runs, because a manually installed extension is one pupil click away from removal.
  4. Confirm that pupils cannot disable the extension. The forced list governs the install, and the extension settings should be locked by policy rather than left editable in the browser.
  5. Apply the same unit to SafeSearch and YouTube Restricted Mode. Those cover search results and video content, a different layer from page text, and both are worth having while the text filter handles comments and forums.
  6. Sign a pupil device out and back in, then check. Open an allowed site with a comment section and confirm that masked words appear. A policy change that has not reached the device looks identical to a filter that does not work.

Repeat for the other year group once the first unit behaves as expected. The rollout stays small because it is a policy change, not an installation visit, and checking a single device turns an assumption into evidence.

Word Lists for the Classroom

Primary classrooms need the broadest list. Use the full standard list plus playground insults such as stupid, ugly and shut up, because young pupils repeat screen language in the playground and the complaint lands on the teacher. Add game specific taunts for the titles pupils actually play, since allowed game sites generate most classroom incidents.

Secondary classrooms need the standard list plus current slang, configured with the pastoral team rather than imposed on it. Restraint with mild language counts at this age, because a filter that masks everyday words gets switched off mentally even where it cannot be switched off technically. Pupils who accept the list report problems instead of routing around them.

Where staff share pupil lists between systems, standardising names once in Sheets stops the same child appearing twice under different spellings.

What the Layers Still Miss

Spoken audio in videos passes all three layers, since none of them transcribes sound. Phones on mobile data bypass school DNS and run apps outside Chrome, so the classroom policy and the phone policy remain separate documents. Being plain about that boundary helps set expectations with parents. The school owns the Chromebook while the household owns the phone. Each needs its own controls.

FAQ

Can I force install an extension on school Chromebooks?

Yes. Google Workspace for Education supports forced installation of Chrome extensions by organisational unit, so pupils cannot remove them.

Does a text filter replace the Admin console web filter?

No. The Admin console blocks places and a text filter cleans words. Schools need both layers because each misses what the other catches.

Which word list suits a primary classroom?

Use the full standard list plus playground insults such as stupid, ugly and shut up. Young pupils repeat on screen language at school and at home.

Is pupil browsing data collected?

Not by PureWord. Everything runs on the device with no account and no analytics. See the privacy policy for the details.

Summary

Classroom Chromebooks are usually filtered by place and unfiltered by word. The comparison shows that Admin console and DNS layers cannot clean language on allowed sites, which is where pupils actually meet it. A forced text filtering extension closes that gap in minutes, with lists tuned by key stage and no pupil data collected.

Close the Word Gap on Classroom Devices

PureWord filters words on allowed sites and installs by organisational unit. Free and private.

Add to Chrome
Project Slidecut