Skip to main content
Cisco Meraki Documentation

Blocking Websites with Meraki Go

Each Meraki Go network can be configured with customizable web blocking rules, to ensure that users aren’t accessing websites that they shouldn’t be.

Blocking Websites

Web blocking allows you to set specific websites that should be blocked from access on your network. It can be configured in two different locations: Directly from the network’s Usage and Speed settings, or via the Usage and Speed section of the general Settings screen.

 

Adding a New Rule

From the Web blocking screen, you can click the + to input a new website to block. If you have accessed the Web blocking screen from the general settings, you can choose which network to create the rule for by clicking the + next to the appropriate network name.

 

      

NOTE: If a website with a subdomain is provided, only the general website will be blocked. Example: “docs.google.com” will only block access to “google.com”

Deleting an Existing Rule

From the Web blocking screen, you can select the Edit button in the top-right corner. You can then select which rules you would like to delete.

 

Everywhere

If you have a Meraki Go Security Gateway, when accessing the Web Blocking feature from the Settings screen, you will see a section at the top of the list named "Everywhere". This will apply the Web Blocking rule to all internet bound traffic passing through the Meraki Go Security Gateway. This can be useful if you have certain websites that you want to block everywhere on your network, regardless of if the client is connected wirelessly or wired.

 

Blocked page example

If a user tries to access one of the blocked sites, they will be presented with one of two pages, depending on if they were attempting to access the website over HTTP or HTTPS.

HTTP

With HTTP, users will see a screen indicating to them that this page has been blocked.

HTTPS

Due to the nature of HTTPS, we aren't able to present a blocked page. Intead, users will just be unable to access the website, and will instead most likely receive a timeout page.