Redirect Generator
Turn old and new URLs into 301 redirect rules for nginx, Apache, Netlify, Vercel, Cloudflare and Caddy.
How to use the Redirect Generator
- 1Add redirects row by row, or import a CSV with old and new URLs.
- 2Choose the status code and whether each rule matches exactly, a whole folder or a regular expression.
- 3Pick your server, copy the rules, and use the checks to remove redirect chains and loops before going live.
About Redirect Generator
The Redirect Generator turns a list of old and new URLs into ready-to-use redirect rules for nginx, Apache .htaccess, Netlify _redirects, Vercel vercel.json, Cloudflare bulk redirect CSV and Caddy. Add rules one by one or import a CSV, choose a 301, 308, 302 or 307 status per rule, and decide whether each one matches an exact path, a whole folder by prefix or a regular expression. Options keep query strings such as UTM parameters and make matching case-insensitive.
Before anything goes live, the checks follow every redirect through the list and find chains, where one old URL leads to another redirect, and loops that would end in a too-many-redirects error. Fix chains rewrites each rule so it points straight at the final address. A tester shows the hops for any path you enter, and the output for the selected server can be copied or downloaded as a file.
It is built for site migrations, domain moves, URL restructures and shop relaunches, where hundreds of 301 redirects have to be written without mistakes. Developers, SEO specialists and agencies can prepare bulk redirects in one place and hand over the right file for each hosting setup.
Frequently asked questions
What is the difference between a 301 and a 302 redirect?
A 301 says the page has moved for good, so search engines move its ranking to the new URL. A 302 is temporary: the old URL stays in the index. 308 and 307 are the same pair but keep the request method, which matters for forms and APIs.
What is a redirect chain?
A URL that redirects to another URL that redirects again. Every hop adds delay, and Google follows at most 10 hops. Fix chains lets each old URL point straight to its final destination.
Should I redirect every old URL to the home page?
No. Redirect each old page to its closest new equivalent. Google treats mass redirects to the home page like missing pages (soft 404s).
Where do the rules go?
nginx rules go into the server block of your site's config, Apache rules into .htaccess in the web root, Netlify rules into a _redirects file in the publish folder, Vercel rules into vercel.json, and Cloudflare's CSV into a bulk redirect list.
How long should I keep 301 redirects?
Google recommends keeping them for at least a year, and longer is better while old links still send visitors. Removing a redirect turns the old URL back into a 404.
More in Web & SEO
Write title, description, Open Graph, Twitter and hreflang tags with pixel-based length checks.
See how your page looks in Google on desktop and mobile, truncated close to where Google cuts it.
Preview link cards for Facebook, X, LinkedIn, Slack, Discord, WhatsApp and iMessage before you share.