Redirect Map Generator for relaunch and URL change
Free generator · without registration
Assign old URLs to their new destinations and create a redirect map as a CSV or rule template for Apache and Nginx. For planning relaunches, CMS changes and individual URL changes.
One assignment per line. Allowed are old and new URLs or paths.
The generated redirect map in the selected format.
Enter old and new URLs and click “Generate Redirect Map”.
Create redirect mapping and take it safely
Correctly assign old and new URLs
Enter one source and one destination per line, separated by blank space, for example /alter-ratgeber https://example.org/wissen/ratgeber. Collect the old URLs in advance from sitemap, crawl or existing exports. The tool does not detect these URLs itself and does not look for suitable successors. Assign each source a content-matched goal; a blanket redirection of all old pages to the homepage is rarely helpful.
Choose CSV, Apache or Nginx
CSV contains the columns source, target and status and is suitable for coordination or for suitable imports. The Apache output uses redirect statements, Nginx uses rewrite. For server rules, enter a path without a domain as the source. Host conditions, query parameters and the order of existing rules must be considered separately. The output is a template; it is neither installed nor tested against your server configuration.
Check duplicate sources and missing targets
With “ignore duplicate sources” the first assignment of an identically entered source is preserved. This does not automatically solve conflicting target decisions. Different spellings or overlapping rules may still be present. Check the full list and get important landing pages separately: the generator does not check HTTP status and does not recognize live redirect chains.
301 or 302 and the post-installation check
For a permanent move 301 is the right choice, for a temporary change 302. Once set up, test representative old URLs: status, final destination, path conservation, and unexpected chains. In addition, update internal links, sitemap and canonical information to the new addresses. Apache Redirect can also capture subsequent path components; therefore, check the appropriate subpaths in addition to the exact source.
Map old guide URLs on suitable successors
Practical example · for illustration
Starting position
Assign /alter-advisor to the new URL /know/advisor; run each old URL only once in the assignment.
Classify the findings
A redirect map is a planned set of rules, not yet an active forwarding.
Specific amendment
Check that each goal meaningfully replaces the old content. Subsequently, install the appropriate output format in the server configuration.
Control and border
Call up old URL with the redirect checker: if possible, a permanent redirect directly to a reachable destination. Redirecting all old pages to the homepage is usually not a suitable assignment.
Questions about use and boundaries
Does the tool automatically create a redirect map from my website?
No. They provide the assignment of old and new URLs. The tool formats and exports this list; a crawl or automatic destination search does not take place.
Can I output directly in . Insert htaccess?
The Apache edition is a template for redirect rules. First, check module, configuration context, paths, and interactions with existing rules. Test the change before productive adoption.
How are duplicate source URLs treated?
If the corresponding option is active, only the first assignment is taken over if the spelling is identical. You should resolve conflicting assignments editorially before exporting.
Does the generator check whether the target pages are reachable?
No. For the HTTP check of the destinations and the control after the setup, use the status code or redirect checker.