Skip to content
toolsbox

Redirect Generator

Turn old → new URL lists into redirect rules for Apache, Nginx, Cloudflare, Vercel and more.

  • Free
  • No sign-up
  • Runs in your browser

What is a redirect generator?

A redirect generator turns a list of old and new URLs into ready-to-paste server configuration. Paste URL pairs as CSV, TSV or two columns, or enter a single redirect, choose the status code, and the tool writes the rules for your platform. It saves hours on site migrations and removes the typos that creep in when hundreds of rules are written by hand.

Output is available for Apache .htaccess using Redirect, RedirectMatch or RewriteRule, Nginx using return or rewrite inside a server block, Caddy, Cloudflare Bulk Redirects as a CSV for upload, Netlify _redirects, Vercel vercel.json and IIS web.config. Options cover preserving the query string, forcing a trailing slash, and sitewide rules for HTTP to HTTPS and www or non-www.

Before you copy anything, the generator checks your list for problems that hurt SEO: duplicate sources pointing to different targets, chains where A redirects to B and B redirects to C, and loops where URLs redirect back to themselves. Everything runs in your browser, so migration maps stay on your device.

How to generate redirect rules

  1. 1

    Paste your URL pairs

    Paste old and new URLs from a spreadsheet as CSV, TSV or two columns, one redirect per line. For a single redirect, type the source and destination directly.

  2. 2

    Choose the status code

    Select 301 or 308 for permanent moves and 302 or 307 for temporary ones. Most migrations should use 301 or 308.

  3. 3

    Pick your server or platform

    Choose Apache, Nginx, Caddy, Cloudflare, Netlify, Vercel or IIS, then set options for query strings, trailing slashes, HTTPS and www handling.

  4. 4

    Fix duplicates, chains and loops

    Review the validation panel. Point every chained source directly at its final destination, and remove loops and conflicting duplicates before deploying.

  5. 5

    Deploy and test

    Copy or download the rules into your config, reload the server, then spot-check old URLs with a redirect chain checker to confirm each returns a single hop to a 200 page.

When to use a redirect generator

Site migrations and redesigns

Map every old URL to its closest new equivalent so rankings and backlinks carry over when URL structures change.

Domain changes

Moving from one domain to another needs page-to-page redirects, not a blanket redirect to the new homepage, which Google may treat as a soft 404.

Content consolidation

When you merge thin or overlapping articles into one stronger page, redirect the retired URLs to the consolidated version.

Switching hosts or platforms

Moving from Apache to Nginx, or from a traditional server to Netlify or Vercel, means rewriting every rule in new syntax. Paste the pairs once and generate the new format.

Cleaning up redirect chains

Years of migrations stack redirects on top of each other. Paste your existing map to find chains and flatten them into single hops.

Choosing status codes and avoiding redirect mistakes

Google treats 301 and 308 as strong signals that the target should become the canonical URL, and 302 and 307 as weak signals that the original may return. The difference between each pair is the request method: 307 and 308 require the browser to repeat the same method, so a POST stays a POST, while 301 and 302 allow it to change to GET. For ordinary page moves, 301 and 308 behave the same for SEO.

Chains cost you. Googlebot follows up to 10 redirect hops before giving up, but every extra hop adds latency for users and wastes crawl requests. Point each old URL straight at its final destination, and update internal links so they reference the new URLs directly rather than relying on redirects.

Syntax details matter. In Apache, a Redirect rule matches by prefix, so Redirect 301 /blog /articles also sends /blog/post to /articles/post; use RedirectMatch with an anchored pattern when you need exact matches. Avoid mixing mod_alias and mod_rewrite rules for the same URLs, because they run in separate phases. On Vercel, permanent: true issues a 308 and permanent: false a 307.

Google recommends keeping redirects in place for at least a year after a site move. In practice, keep them as long as the old URLs still receive links or traffic.

Frequently asked questions

Is the redirect generator free?

Yes, the redirect generator is free, with no account and no limit on the number of URL pairs. All output formats, the options and the duplicate, chain and loop checks are included. It is built for developers and SEO teams handling migrations who need accurate rules for several platforms quickly.

Are my URLs uploaded anywhere?

No, the redirect generator runs entirely in your browser, and your URL list is never uploaded or stored. Migration maps often reveal unreleased site structures, so nothing leaves your device until you copy or download the rules. The tool does not fetch your URLs either; it validates the list as written.

Should I use a 301 or a 308 redirect?

Either works for permanent page moves, and Google treats both as strong canonical signals. Choose 308 when the URL receives POST requests, such as a form or API endpoint, because it preserves the method. For standard page redirects, 301 remains the most widely supported choice across older tools and platforms.

Do 301 redirects lose PageRank?

No, Google has stated that 3xx redirects do not lose PageRank. Signals consolidate to the target, provided the destination is relevant. Redirecting many unrelated pages to the homepage can be treated as a soft 404, so map each old URL to its closest equivalent instead.

What is a redirect chain and why does it matter?

A redirect chain is when one URL redirects to another URL that redirects again before reaching the final page. Chains slow users down and waste crawl requests, and Googlebot stops after 10 hops. The generator flags chains in your list so you can point every source directly at its final destination.

Does the generator handle query strings?

Yes, the preserve query string option carries parameters from the old URL to the new one in every output format. Defaults differ by server: Apache RewriteRule passes query strings unless told otherwise, while some platforms drop them. Setting the option explicitly keeps behavior consistent across platforms.