URL Redirect Generator

What This Tool Does

This generator is used to get the correct redirect code from a source URL to a destination URL, all for any site that happens to be running on any platform.

• Apache (.htaccess) — you can use mod_alias (Redirect) or mod_rewrite (RewriteRule) in the .htaccess file as you require.
• This is no longer required with Nginx, as it supports rewriting web requests or returning them in your server block.
• If a site doesn't have access to server configuration, it can be redirected from PHP — a header("Location: ...") redirect for sites without server config access.
• For use if server-side redirects are not truly possible HTML meta refresh should be used.

Redirect config formats are different for each platform: WordPress, Next.js, Vercel, Netlify, Cloudflare Pages.

Select the type of redirect (301 or 302 — most often), type your URLs and let the tool write the syntax for you — no need to memorize the order of apache regexs or Nginx directives.

How to Make a Redirect (Three Steps)

1. Enter your source and destination URLs. The source is the old page that people (and search engines) are now landing on and the destination is where they should be landing instead.
2. Choose your redirect type and platform. Choose 301 for permanent or 302 for temporary and then pick the platform your site is on.
3. Copy the code into place. Copy it into your platform config, PHP file, nginx.conf, or .htaccess file — then try it before putting it into production.

301 vs. 302 (and When to Use 307/308 Instead)

This is the number one redirect redirection error, and has very tangible SEO impacts: A bad redirect status code can make you lose ranks without you realizing it during a redirect.

The rule of thumb for all such cases is that if the old URL is dead, use 301 — this will pass the ranking signals on to the new one for search engines. A popular error is using 302 for a permanent move, which can cause the old and now-dead URL to be indexed rather than the new one as 302 tells search engines "this is temporary, keep checking back.

Common Redirecting Pitfalls that lead to serious issues

• Redirect loops. Page A redirects to Page B, which redirects to Page A — eventually, browsers will limit their redirects and throw up a "Too many redirects" error. This is frequently the case when HTTPS, www, and trailing-slash rules are applied on one-by-one basis without any cross-checking.
• Redirect chains. A redirects to B, which redirects to C, which redirects to D. Every "hop" has latency and reduces some SEO value along the way — always use the "true" final URL that will contain the extra redirect.
• Moving at 302 houses – Permanent move. This is the most popular error that is often made with status-codes and it's a quick one to make if you don't look at the dropdown.
• Query string handling. Other redirection methods will ignore query strings unless you've configured them to do otherwise (such as capturing a query string, like ?ref=email, that you'd like to keep when you redirect).
• Syntax error in .htaccess file. The two can cause a full server error (500) instead of a failed redirect, so always test these .htaccess changes on staging before pushing them live — a missing bracket and malformed RewriteRule can cause a full server error.
• Case sensitive mismatches between /Old-Page and /old-page — these might be different rules depending on your server configuration, so check to be sure you're getting an expected redirect.

Frequently Asked Questions