Redirects

Use redirects to declare URL redirects in config. Sources support full path-to-regexp pattern syntax — the same as routes.

Basic redirect

// +config
i18n: {
  redirects: {
    '/old-about': '/about',
  },
}

String redirects use temporary redirects by default (302).

Redirect status

Use object form to choose between temporary (302) and permanent (301) redirects:

redirects: {
  '/old-about': { url: '/about', status: 301 },
  '/preview': { url: '/about', status: 302 },
},

Locale-aware redirects

When the redirect source matches a known route pattern, the redirect applies to all locale variants automatically.

routes: {
  '/specialities/:speciality': {
    en: '/specialities/:speciality',
    ru: '/specialnosti/:speciality',
  },
},
redirects: {
  '/specialities/diver': '/specialities/driver',
},

Incoming URL	Redirects to
/en/specialities/diver	/en/specialities/driver
/ru/specialnosti/diver	/ru/specialnosti/driver

The source is matched against the canonical route pattern. The target is localized using the same route config — so /specialities/driver becomes /ru/specialnosti/driver for Russian.

If the target does not match any route key, it is used as-is without localization.

Param transfer

Named params captured from the source pattern are filled into the target:

redirects: {
  '/medicines/:country': '/drugs/:country',
},

• /en/medicines/ua → /en/drugs/ua
• /ru/medicines/ua → /ru/preparaty/ua (target /drugs/:country localized to RU)

Wildcard tail stripping

Use {*name} (path-to-regexp v8 named wildcard) to capture and discard a URL tail:

redirects: {
  '/medicines/:country/{*rest}': '/drugs/:country',
},

• /en/medicines/ua/extra/path → /en/drugs/ua

Named wildcard params not referenced in the target are silently dropped.

Locale-scoped redirects

Restrict a redirect to specific locales with the locales option:

redirects: {
  '/old-page': { url: '/about', locales: ['en'] },
},

This fires only for English. Other locales are unaffected.

Per-domain redirects

Each domain config accepts its own redirects. Domain-level redirects are merged with global ones; domain entries take priority on key conflicts.

domains: {
  'ru.site.com': {
    defaultLocale: 'ru',
    locales: ['ru'],
    redirects: {
      '/legacy-ru': '/about',
    },
  },
}

See Domains for a full domain config example.

Redirect chain validation

Redirects are validated when the routing config is compiled.

• Redirect chains such as /a -> /b -> /c print a warning so you can flatten them to /a -> /c.
• Redirect loops such as /a -> /b -> /a throw immediately.

This validation runs after domain redirects are merged with global redirects, so domain-specific chains and loops are checked too.

Next: Domains