301 Redirect Generator

Use 301 for anything permanent: it tells search engines the move is final and passes the old page’s ranking signals to the new URL. A 302 says the change is temporary, so the old URL stays indexed — useful for a short campaign, wrong for a migration. The detail most people miss is chains. If A redirects to B and B later redirects to C, every visitor and crawler makes two hops, which wastes crawl budget and dilutes the signal passed along. Whenever you add a new redirect, check whether its target is itself already redirected and repoint the original straight at the final destination. One more practical warning: a syntax error in .htaccess takes down the whole site with a 500, so always test on a staging copy.

Apache rules take the form RewriteRule ^old-path$ /new-path [R=301,L], where ^ and $ anchor the match to the whole path. Nginx uses location = /old-path { return 301 /new-path; }, and Netlify-style hosts use a plain “from to code” line.

These are exact-match rules, one per URL — wildcard and pattern-based redirects, query-string matching and conditional rules by hostname or language are out of scope and need hand-written configuration. The generator cannot verify that your target URLs actually exist or return 200. Always test on staging first: a malformed .htaccess returns a 500 error for the entire site, not just the redirected pages.

Four redirects — including one from a full https:// URL and one to an external domain — produce four anchored rules wrapped in an IfModule block, ready to paste at the top of .htaccess.

1. List your redirects, one “old URL, new URL” pair per line.
2. Choose your server type and status code.
3. Fix any redirect chains the tool flags.
4. Test on staging, then deploy the rules.

• Using 302 for a permanent move, so the old URL keeps the rankings.
• Leaving redirect chains in place instead of flattening them.
• Forgetting to escape dots, so ^page.html matches more than intended.
• Redirecting everything to the homepage instead of the closest equivalent page.

The 301 Redirect Generator converts a list of old and new URLs into ready-to-paste redirect rules for Apache, Nginx or Netlify-style hosts. It normalises full URLs down to paths, escapes regex characters, removes duplicates and flags redirect chains before you deploy.

Anyone migrating a site, restructuring URLs or cleaning up after a redesign.

• Three server formats from one list.
• Escapes dots and other regex characters that would otherwise match too broadly.
• Detects redirect chains, which quietly waste crawl budget.
• Accepts full URLs, paths, commas, tabs or arrow separators.

• Migrating to a new URL structure without losing rankings.
• Redirecting old .html pages to clean URLs after a rebuild.
• Consolidating duplicate or retired pages.
• Pointing legacy campaign URLs at their current equivalents.