Nginx Redirect Generator

An Nginx redirect generator writes location blocks that return 301 or 302 redirects for specific URLs and an optional HTTP to HTTPS server block. Always run nginx -t before reloading.

It runs entirely in your browser. Nothing you paste or upload is sent to a server or stored.

How to read the result and act on it

Check each generated location block: the path to match, the return statement and the status code. Use 301 for permanent moves and 302 only for temporary ones. If you included the HTTP to HTTPS server block, confirm it listens on port 80 and returns a 301 to the https version of the requested URI. Place the blocks inside the correct server context in your site's config file, then run nginx -t to test the syntax before reloading the service. Afterwards, test a sample of old URLs with a redirect checker and confirm each reaches a 200 page in one hop. Keep a copy of the previous config so you can roll back quickly.

Common mistakes to avoid

Reloading Nginx without running nginx -t first is the main risk, since a syntax error can stop the reload and leave you troubleshooting live. Putting redirects in the wrong server block, such as the HTTPS block when they should run on both, produces unexpected results. Exact-match locations use an equals sign, while prefix locations also match longer paths, so a loose match can redirect more than intended. Redirect chains and loops appear when a destination is itself redirected. Special characters and query strings need care. Avoid redirecting unrelated pages to the homepage. Remember that a CDN or caching layer can hide changes until it is purged.

Where do Nginx redirect rules go?

Inside the relevant server block of your site configuration, followed by a test and reload.

How do I redirect a whole folder?

Use a regex location with a capture group, such as rewrite ^/old/(.*)$ /new/$1 permanent; the generator covers single URLs only.

How do I redirect a URL in Nginx?

Add a location block with an exact match and a return statement, for example location = /old { return 301 /new; }. Run nginx -t to test, then reload Nginx. Check the old URL afterwards to confirm one hop.

What is the difference between return and rewrite in Nginx?

Return sends a redirect straight away and is simpler and faster for fixed redirects. Rewrite changes the URI using patterns and can be chained with other directives. For plain URL redirects, return is generally the cleaner choice.

• .htaccess Redirect Generator: Generate Apache 301 and 302 redirect rules, including HTTPS and www forcing.
• Redirect Checker: Trace every redirect hop from a URL to its final destination, with status codes.
• HTTPS Redirect Checker: Check that http:// and www variants of a site redirect to one secure canonical address.

Browse all 41 free technical seo tools, or see the full free SEO toolbox. If you would rather have this handled for you, take a look at our technical SEO services and the results from real projects.