SEO Tools

301 Redirect Generator

Generate 301 redirect rules for Apache (.htaccess), Nginx, or a plain JSON map online for free — from a list of old and new URLs, instantly.

Private by default Instant results No signup

Overview

What is a 301 redirect?

A 301 redirect permanently sends visitors and search engines from an old URL to a new one, passing along most of the original page's ranking signals. It's the standard way to handle moved pages, renamed URLs, or a domain migration without losing existing search traffic or breaking bookmarked links.

This tool takes a list of old-URL / new-URL pairs and produces ready-to-use rules for Apache's .htaccess, Nginx config, or a plain JSON redirect map.

Guide

How to use it

1Add a row for each redirect (from → to)

2Choose Apache, Nginx, or JSON output

3Copy the generated rules

4Paste into your server config or redirect middleware

How the rules are built

For Apache, each pair becomes a Redirect 301 directive. For Nginx, each becomes a rewrite ... permanent; block. The JSON format outputs a simple old-to-new key/value map that's easy to feed into a custom redirect middleware or serverless function.

Why it helps

Features & benefits

Apache, Nginx, and JSON output formats

Bulk redirect rules from a simple row-based editor

One-click copy of the generated config

100% private — nothing leaves the device

Why this runs entirely in your browser

Redirect maps can reveal a site's URL structure or migration plans, so nothing is uploaded. The rules are assembled in JavaScript locally in the tab, which means it keeps working offline once the page has loaded.

Common uses

Redirecting old URLs after a site restructure, mapping legacy pages during a domain migration, or generating a batch of redirects after renaming a set of product or blog URLs.

Frequently asked questions

A few things people usually want to know before trusting the numbers.

Why use a 301 instead of a 302 redirect?

A 301 signals a permanent move and passes most ranking signals to the new URL, while a 302 signals a temporary move and search engines keep indexing the old URL.

Where do I put the Apache rules?

Into your site's .htaccess file, typically in the root directory, or into the main Apache virtual host configuration.

Where do I put the Nginx rules?

Inside the relevant server block in your Nginx configuration file, then reload or restart Nginx for the changes to take effect.

What's the JSON format useful for?

It's a plain old-to-new URL map that's easy to load into custom redirect logic — for example, a Next.js middleware or a serverless function.

Is my URL list uploaded or stored anywhere?

No. All rules are generated locally in your browser. Nothing entered here is sent to a server, stored, or shared.