There are various options you can set from the Options page, accessible from the top menu.
Redirection will log every redirect and every 404 on your site unless you configure otherwise. You can set the amount of time to keep these logs to:
- Two months
- A month
- A week
- A day
The logs can also be disabled by selecting No Logs.
Note that log expiry is performed using WordPress cron, and it is important that your site is set up to allow this.
You can customise the level of IP information that is collected by Redirection. By default it will collect the full IP address of every redirected URL and 404 error. This is the preferred mode and allows you to display further information about where your visitors are from.
If you live in a country that has strict laws detailing the collection of IP addresses then you may want to use the ‘Anonymize IP’ option, or even disable it entirely.
The options are:
- No IP logging
- Full IP logging
- Anonymized IP logging (the last part of the IP address is masked – 18.104.22.168 becomes 22.214.171.124)
Note that Redirection supports IPv4 and IPv6 addresses.
Redirection can monitor for URLs changes to posts, pages, and custom post types, and auto-create a redirect from the old post URL to the new post URL.
It can also be configured for deleted posts, although these will be auto created as disabled redirects and you will need to fill in the target URL and then enable.
Select what you want to monitor:
Note that any custom post types you have on your site will also appear in this list. For example, WooCommerce products.
And then select which Redirection group you want the redirects to appear in.
You can also set up an associated redirect, which will be created at the same time. This allows you, for example, to redirect AMP pages at the same time.
The way this works is that if your old post was
/2017/12/01/old-post and this is redirected to
/posts/old-post, then a second redirect will be created for
You can view your redirect logs using an RSS reader. The RSS Token is used to provide a unique key so that the RSS reader does not need a username/password to access your logs.
You can manually set this key, or you can delete it to auto-generate a new one.
If you do not provide a target URL for a redirect then the auto-generate URL will be used to generate one for you. This can be used to create URLs with unique IDs for tracking purposes.
For example, if you set the auto-generate URL to
/track/$hex$ then a redirect created with a blank target URL will be changed into something like
If you make use of the Apache module (see the Groups page) this is where you configure the path of your
.htaccess file. Please make sure the web server has write permissions to the file. Redirection will append to the file.
Force HTTP to HTTPS
Enabling this option will cause Redirection to force any access to the HTTP version of your site to be redirected to the same URL on HTTPS.
Before you enable this please ensure your site can be accessed via HTTPS, as if enabled without HTTPS access then the plugin will stop working. If you do get into this situation then visit the ‘support’ page and the plugin will auto-disable this option if it detects a problem.
By default a browser will cache a redirected URL such that it won’t request the URL again should the user re-request it.
The Redirect Cache option allows you to configure the expiry time of this cache.
If you often make changes to redirections then having a lower expiry time (or none at all) will mean your users will be redirected to the most recent target.
If you make few changes to redirections then a longer expiry time will mean your users make fewer requests to your server.
If you do change a redirection and find that your browser is still using the old redirect, then the expiry cache is to blame. You will need to clear your browser cache manually and think about using a smaller cache time.
Redirection uses the WordPress REST API to communicate with WordPress. For the majority of users this is shouldn’t cause any issue. However, some setups may experience problems caused by security plugins or other issues, and you may need to change how Redirection uses the REST API.
The options are:
– Default – use the default REST API, as defined by
get_rest_url(). This is the standard API, and the preferred setting
– Raw – sometimes the default API may not work, and you can try using the API via
– Proxy via Admin AJAX – this proxies the API requests via the older style WordPress admin AJAX
If you change this setting and something breaks you can go to the Support page and Redirection will attempt to fix it.
If none of these settings fix the problem then you almost certainly are running security plugin that is blocking all requests. This will likely cause other problems, and you should try and reconfigure the plugin.
Clicking the red Delete button will remove all data associated with Redirection and disable the plugin.
You should do this if you want to clear everything and start again. This may be necessary if you are having problems.
Note this this button will not appear when you install Redirection globally on a multi-site, and are viewing the plugin through a subsite.