Redirects module

Access the redirects module in the TYPO3 backend under Site Management > Redirects.

Open Redirects module


Redirect list

You will see a list of the existing redirects with the following columns labels.

  1. Source Domain
  2. Source Path
  3. Target
  4. Count: Number of "hits" (only if hit counter is on)
  5. Last Hit on: When was the most recent redirect "hit" (only if hit counter is on)
  6. Action buttons: View page, edit, disable and delete

It is also possible to sort by clicking on the Source Host or Source Path column headers and changing the sort order by clicking again, as also done elsewhere in the backend.

By clicking on the Source Path of one of the columns or on the pencil edit icon , you can edit the record. Clicking on a link in the Destination column, should open the link target.

The + sign on the top will open an edit form to create a new redirect.

It is also possible to filter, e.g. by the Source Path, Status Code or only show redirect records which were "Never hit" (see Information on Hit counter which must be explicitly enabled via Feature Toggle).

Edit form

When creating a new redirect or editing an existing one, the edit form will open.

A redirect generally consists of these 2 parts which are separated in the edit form:

  1. A source part (host, path, query parameters) which is matched against the URL. If it matches, the redirect is applied
  2. A target part which defines where the redirect should redirect to and some additional parameters like the HTTP status code, whether to force HTTPS and keep query parameters

Also, the redirect has some additional parameters that are specific for the redirect record but not relevant when generating the redirect, such as the Protected field.

Admin users will see the respective database fields from the table sys_redirect in square brackets (e.g. Source Domain [source_host]) next to the label if in debug mode.

Non-admin users may not see all the fields. By default Source Domain, Source Path and Target are enabled, the rest are exclude fields and must be enabled in the backend group permissions, see backend user configuration.

General tab

Edit redirect


Source Domain


It is possible to select one of the domains from the site configuration or use the wildcard (*). In this case the redirect applies to all sites!

Source Path


Can be an actual path, e.g. /path. For URLs with different entry points for languages, you should use the full path, e.g. /en/path. Regular expressions are possible, but then is_regexp must be enabled. Regular expressions must be enclosed in delimiters, e.g. #^/path/([a-zA-Z]{1}[a-zA-Z0-9_/-]+)# or /^\/path\/([a-zA-Z]{1}[a-zA-Z0-9_/-]+)/.

Respect GET Parameters


If on, matching is also performed on query parameters. If off, matching is only performed on the path.

Is regular expression?


Evaluate the Source Path as regular expression.




The redirect target, can be a

  • path, e.g. /features
  • URL, e.g.
  • page ID or page URI, e.g. t3://page?uid=1
  • file URI, e.g. t3://file?uid=1
  • path with reference to regular expression capturing group if the regular expression feature is used with e.g. capturing groups in Source Path, e.g. /newpath/$1
Status Code HTTP Header


The HTTP status code that will be sent to the client. This is 307 (Temporary Redirect) by default.

Force SSL Redirect


When redirecting, use HTTPS when constructing the target URL. This will even be the case, if a full URL is given as target (e.g. or if the entry point of a site uses HTTP, so make sure your site supports HTTPS (which is recommended anyway).

Keep GET Parameters


When redirecting, add query parameters of original URL (with possible changes) to the target. By default, the query parameters are omitted, so source URL would be redirected to If there are already query parameters in the target field, these are used instead.



This does not affect the redirect itself. It protects the record from automatic deletion (e.g. with redirects:cleanup).

Statistics tab

Statistics tab with hit counter

This tab is only available, if the hit counter is enabled. Here you can disable the hit counter for a specific redirect and also see read-only statistics.

Hit Counter


Disable the hit counter only for this redirect.




read only

Number of hits for this particular redirect. (How often was the page accessed which triggered this redirect?)

Last Hit on



read only

When was the last hit on this redirect?

Created At



read only

When was this redirect created?

Access tab



If disabled, the redirect has no effect.



If this is not empty, "now" (current time) must be after Start time for the redirect to have effect.



If this is not empty, "now" (current time) must be before Stop time for the redirect to have effect.

Regex examples

Example 1: Source path with regular expression and capturing group


Source Path Is Regular Expression target
#^/path/([a-zA-Z]{1}[a-zA-Z0-9_/-]+)# true$1

with the following result:

URL result URL

Example 2: Source path with regular expression, capturing group and relative target


Source Path Is Regular Expression target
#^/another/path/([a-zA-Z]{1}[a-zA-Z0-9_/-]+)# true /newpath/$1

with the following result:

URL result URL

Using a relative target is necessary if a redirect must work on multiple domains or multiple environments.

Automatic redirects creation

Redirects are created automatically on slug changes, if EXT:redirects is installed and automatic creation is enabled in site configuration.

A redirect from the old URL to the new URL will be created. All sub pages are checked too and the slugs will be updated and redirects will be created for these as well.

After the creation of the redirects a notification will be shown to the user.

Revert redirect

The notification contains two possible actions:

  • revert the complete slug update and remove the redirects
  • or only remove the redirects