---
title: "Introduction"
manual: "Relaunch Redirects"
version: "main"
permalink: "https://docs.typo3.org/permalink/fuf/relaunch-redirects:introduction@main"
source: "Introduction/Index.rst"
rendered: "2026-10-17T17:10:51+00:00"
---

# Introduction {#introduction}

## What it does {#what-it-does}

A relaunch usually changes the page tree, the slugs and often the URL
scheme: `/leistungen/architektur.html` on the old website becomes
`/leistungen/architektur` on the new one, `/referenzen/` becomes
`/projekte/`. The extension answers one question for every URL of the
old website: what does a visitor get on the new site?

1.  You import the URLs of the old website: its XML sitemap, a list from the
    Google Search Console or a crawler, or any list of URLs and paths.
1.  The extension follows every URL through the new site the way the TYPO3
    frontend would: redirects of EXT:redirects first, then the page router.
1.  For every URL that would end in a 404 it suggests the most likely page of
    the new site, for example the page with the same path without
    `.html`, or the only page with the same name.
1.  You confirm the suggestions, pick another page or ignore the URL. The
    redirects are created in the TYPO3 redirects module, where they can be
    edited like any other redirect.

![The backend module lists the old URLs that need a decision, with a suggested target page for each](../Images/ModuleOverview.png)

## Features {#features}

-   Imports XML sitemaps, sitemap indexes (also gzip compressed), text lists
    and CSV exports.
-   Follows redirect chains, loops, regular expression redirects, redirects
    that respect query parameters and shortcut pages.
-   Treats the old production domain as an alias of the staging domain, so
    redirects for `www.example.org` are found on
    `stage.example.org`.
-   Sees the new site like an anonymous visitor: hidden pages, folders and
    access restricted pages count as missing, also when the check runs on the
    command line or for an administrator.
-   Suggests up to three target pages per URL, with a score. Suggestions of 90
    and more are ticked: the old URL has the same path, or its page name
    exists only once on the new site.
-   Fixes broken redirects by pointing them to a new target.
-   Writes the redirects through the DataHandler, with the permissions of the
    editor, stored on the root page of the site like the redirects TYPO3
    creates on slug changes.
-   Exports the list as CSV, also for Excel with German settings.
-   Console commands for imports, checks in deployment pipelines and bulk
    creation of safe redirects.
-   Supports TYPO3 13.4 LTS and 14.3 LTS. Backend in English and German.

## What it does not do {#what-it-does-not-do}

The check works inside TYPO3 and requests nothing over the network. It does
not see rewrite rules of the web server (for example in `.htaccess`),
and it does not render pages. See [Limitations](https://docs.typo3.org/permalink/fuf/relaunch-redirects:limitations@main) for the details.

Suggestions are proposals. Below a score of 90 they are not ticked, and a
person decides.