What Your Child Sees When a Site Is Blocked
Blocked requests don't fail mysteriously — they land on a clear page explaining the block. Here's what it says and how the built-in ask-a-parent flow works.
The blocked page
Instead of a cryptic error, your child sees a Guardian-CORR page that explains in plain language: the site was blocked by your family's rules, which category triggered it (for example, Gambling), and which profile the device belongs to. There's no scary language — the message is factual and calm, because the goal is a family conversation, not a punishment screen.
The "ask a parent" button
Many blocks include a request option. Your child can tap it and add a short message explaining why they need the site — for homework, for a game with friends, whatever the reason. That lands in your Access Requests queue with the site, the child, and the device, and you approve or deny from the portal.
Why this beats silent blocking
Silent failures look like broken Wi-Fi — kids get frustrated and parents get blamed. A clear block page does the opposite: the child knows exactly what happened, and the request path gives you a low-friction way to say yes when the answer is actually yes.
Blocked events also land in your activity log, so you'll see patterns even when no request is submitted.