Web / Server

Redirect Planner

Plan redirects in a structured way, validate old and new URLs and create a clean mapping list for migrations, relaunches and technical SEO work.

What is the Redirect Planner for?

During a relaunch, URL change or content migration, old addresses need to point reliably to the correct new destinations. The Redirect Planner helps you collect old URLs, new URLs, status codes and notes in a clear table.

You can add individual redirects through the table fields or paste multiple rows as CSV, semicolon-separated data or tabular data. The result can be exported as a mapping list, CSV, Apache rules, Nginx rules or a Markdown table.

Create redirect mapping

Enter URL mapping

Enter old and new URLs. Relative paths such as /old-page/ are allowed, as well as full URLs with https://.

One redirect per line. Semicolon, comma and tab-separated data are supported. Order: old URL; new URL; status code; note.

Ready.
0 Entries
0 Errors
0 Warnings

Mapping table

Old URL New URL Code Note Check Action
No redirects have been added yet.

Export

Notes for redirect plans

  • 301 is suitable for permanently moved URLs.
  • 302 or 307 is intended for temporary redirects.
  • 410 indicates that a resource has been permanently removed and has no new destination.
  • Avoid redirect chains. Old URLs should point directly to the final destination whenever possible.
  • After a relaunch, test important pages manually in the browser and in the server configuration.