That standard is mostly used to indicate “adult” websites (porn, basically) which is useful, but rather a different thing than what I’m advocating. There are ma

That standard is mostly used to indicate “adult” websites (porn, basically) which is useful, but rather a different thing than what I’m advocating. There are many websites intended for adults that should not be blocked when Google’s safe search is turned on. It should be possible to write a web crawler for the children’s Internet. Whether it’s a client-side or server-side header doesn’t matter for that use case. Roughly distinguishing between children and adults based on behavior can’t be stopped and shouldn’t be considered a privacy violation. For example, see how Lego does it: https://www.lego.com/en-us https://www.lego.com/en-us A client-side header would let them do a redirect instead of a dialog box. There could be alternatively be a server-side header that causes a redirect, but either way, they could distinguish child-locked devices from unlocked based on the destination of the redirect.