What’s in This Guide
This guide covers how to protect your content using a redirect in your Global Restriction.
If you’d rather use a custom message, read our How To Protect Content Using a Custom Message guide.
Setting up how to protect your content is the second of the 3 main steps for creating a Global Restriction.
Protecting content using a redirect applies only to Global Restrictions.
Are you looking to protect a block instead?
If you want to protect a block in the WordPress block editor, head over to our How To Add a Restriction to a Block guide.
Use a Redirect to Protect Your Content
Here’s how you tell Content Control to protect your content with a redirect.
1. Add a new Global Restriction or hover over an existing one and click Edit
If this is a new restriction, enter a name for it (e.g., “Redirect Protection”).
2. Click Protection then click Redirect
For Where will the user be taken?, you can:
- Keep the default Login & Back option: If you aren’t allowed to see the protected content, you’ll get redirected to the login page. Once you log in with the right role, you’ll get redirected back to the post/page you were at before successfully logging in. You’ll keep seeing the login page until you log in with the proper role or go to another page you’re allowed to view.
- Select Home Page: If you aren’t allowed to see the protected content, you’ll get redirected to the homepage. If you use the rules Content Is A Page or Content Is The Home Page, you must add AND Is Not The Home Page (exclude the home page) to avoid the too many redirects error.
- Select Custom URL: If you aren’t allowed to see the protected content, you’ll get redirected to the URL you entered here (see the screen capture below). Make sure your custom URL is valid and working. Be careful to check your content rules. They must not include your custom URL to avoid the too many redirects error.
Above: You can enter any valid URL for the Redirect Protection.