FREE TOOL — NO SIGNUP REQUIRED

Redirect Generator

Map reviewed local paths to safe destinations and generate draft redirect rules for Apache, Nginx, or Next.js. Test every rule before deployment.

Generated Apache .htaccess Config

RewriteEngine On

Redirect 301 /old-page /new-page
Redirect 301 /blog/old-post /blog/new-post

How to Use This Tool

  1. 1

    Add redirect rules by entering the old URL path and the new destination URL.

  2. 2

    Choose your server platform — Apache (.htaccess), Nginx, or Next.js.

  3. 3

    Copy the generated redirect configuration and add it to your server config or application code.

Why This Matters for SEO

When a page moves, a direct permanent redirect gives visitors and search engines a working route from the old URL to the new one. It also signals that the destination should be treated as the canonical replacement. This tool formats rules for the selected server platform, but they should still be tested before deployment.

Frequently Asked Questions

What's the difference between permanent and temporary redirects?+
A 301 or 308 signals a permanent move and that the destination should become canonical. A 302 or 307 signals that the move is temporary and the original URL should remain canonical.
Do redirects hurt page speed?+
Every redirect adds another request and some latency. Avoid chains such as A → B → C; send users and crawlers directly from A to C where possible.
How long should I keep redirects active?+
Keep permanent redirects for as long as people, links, bookmarks, or crawlers may use the old URLs—ideally indefinitely. Removing them can turn old routes back into errors.

Related Free Tools

Review Redirects Before and After a Migration

Use crawl findings to identify broken paths and redirect chains in the URLs you review. Test every rule and monitor search performance; no migration workflow can guarantee stable rankings.

Start Free Trial