The redirects module provides the models and user interface for managing arbitrary redirection between urls and Pages or other urls.


The redirects module is not enabled by default. To install it, add wagtail.contrib.redirects to INSTALLED_APPS and wagtail.contrib.redirects.middleware.RedirectMiddleware to MIDDLEWARE in your project’s Django settings file.

    # ...


    # ...
    # all other django middleware first


This app contains migrations so make sure you run the migrate django-admin command after installing.


Once installed, a new menu item called “Redirects” should appear in the “Settings” menu. This is where you can add arbitrary redirects to your site.

For an editor’s guide to the interface, see our how-to guide: Manage redirects.

Automatic redirect creation

Wagtail automatically creates permanent redirects for pages (and their descendants) when they are moved or their slug is changed. This helps to preserve SEO rankings of pages over time, and helps site visitors get to the right place when using bookmarks or using outdated links.

Creating redirects for alternative page routes

If your project uses RoutablePageMixin to create pages with alternative routes, you might want to consider overriding the get_route_paths() method for those page types. Adding popular route paths to this list will result in the creation of additional redirects; helping visitors to alternative routes to get to the right place also.

For more information, please see :meth:~wagtail.models.Page.get_route_paths.

Disabling automatic redirect creation

Wagtail’s default implementation works best for small-to-medium sized projects (5000 pages or fewer) that mostly use Wagtail’s built-in methods for URL generation.

Overrides to the following Page methods are respected when generating redirects, but use of specific page fields in those overrides will trigger additional database queries.

If you find the feature is not a good fit for your project, you can disable it by adding the following to your project settings:


Management commands


./ import_redirects

This command imports and creates redirects from a file supplied by the user.





This is the path to the file you wish to import redirects from.


This is the site for the site you wish to save redirects to.


If the redirects imported should be permanent (True) or not (False). It’s True by default.


The column index you want to use as redirect from value.


The column index you want to use as redirect to value.


Lets you run an import without doing any changes.


Lets you inspect and approve each redirect before it is created.

The Redirect class

class wagtail.contrib.redirects.models.Redirect(id, old_path, site, is_permanent, redirect_page, redirect_page_route_path, redirect_link, automatically_created, created_at)
static add_redirect(old_path, redirect_to=None, is_permanent=True, page_route_path=None, site=None, automatically_created=False)

Create and save a Redirect instance with a single method.

  • old_path – the path you wish to redirect

  • site – the Site (instance) the redirect is applicable to (if not all sites)

  • redirect_to – a Page (instance) or path (string) where the redirect should point

  • is_permanent – whether the redirect should be indicated as permanent (i.e. 301 redirect)


Redirect instance


You can create an API endpoint to retrieve redirects or find specific redirects by path.

See the Wagtail API v2 Configuration Guide documentation on how to configure the Wagtail API.

Add the following code to add the redirects endpoint:

from wagtail.contrib.redirects.api import RedirectsAPIViewSet

api_router.register_endpoint('redirects', RedirectsAPIViewSet)

With this configuration, redirects will be available at /api/v2/redirects/.

Specific redirects by path can be resolved with /api/v2/redirects/find/?html_path=<path>, which will return either a 200 response with the redirects detail, or a 404 not found response.