Nginx Rewrite Rule Generator

What Are Nginx Rewrite Rules and Why Do They Matter?

Nginx rewrite rules are server-side directives that intercept incoming HTTP requests and transform the URI before the web server decides how to handle them. They are one of the most powerful features in Nginx configuration, enabling everything from simple page redirects to complex URL rewriting logic using Perl-compatible regular expressions (PCRE).

Whether you are migrating a legacy PHP application to a modern framework, consolidating multiple domains, or enforcing HTTPS across your entire site, rewrite rules are the mechanism that keeps your links working and your SEO rankings intact during the transition.

Understanding Core Nginx Directives

• Rewrite (rewrite pattern replacement [flag]): Modifies the client's request URI according to regular expressions. Supports internal parsing loops or browser redirects. Evaluated top-to-bottom within a server or location block.
• Return (return code [text/url]): Returns an immediate HTTP status directly to the browser (such as 301, 302, 403, or 500). Nginx documentation recommends return over rewrite for simple redirects because it skips regex execution blocks for maximum throughput.
• Redirect Flags:
  • permanent returns HTTP 301, instructing search engines and browsers to permanently cache the new URL and transfer link equity.
  • redirect returns HTTP 302, used for temporary migrations where the original URL may return.
  • last stops rewrite processing and forces Nginx to scan for a new matching location block with the modified URI.
  • break stops rewrite processing and serves content from the current location block without starting a new location search.

Capture Groups and Dynamic URL Rewriting

Nginx rewrite rules support PCRE capture groups. Enclose sub-expressions in parentheses in your match pattern (e.g., ^/blog/(.*)$), then reference them as $1, $2, etc. in the destination string. This enables powerful wildcard redirects — for example, redirecting an entire legacy blog directory to a new path while preserving all post slugs: rewrite ^/blog/(.*)$ /articles/$1 permanent;

The 'if' Directive in Nginx — Use With Caution

Nginx's if directive allows conditional execution of rewrite rules based on server variables like $host, $scheme, or $http_user_agent. However, the Nginx community has a well-known guideline: "if is evil." Nested if blocks are not supported and produce configuration errors. Always test with nginx -t before reloading. This generator strictly produces flat, single-level if blocks to ensure valid output.

SEO Best Practices for Nginx Redirects

For search engine optimization (SEO), always use 301 permanent redirects when consolidating domains (like forwarding non-www traffic to www) or restructuring site directories permanently. This ensures all existing link equity passes cleanly to the new target URLs. Use 302 redirects only when the move is temporary — search engines do not transfer link authority for temporary redirects. After deploying redirects, validate them in Google Search Console to confirm the URL change has been processed correctly.

How to Apply Generated Rules to Your Nginx Server

Copy the generated rule and open your Nginx virtual host config file (typically at /etc/nginx/sites-available/yourdomain). Paste the rule inside the appropriate server or location block. Then run sudo nginx -t to validate the syntax. If the test reports success, apply the change with sudo systemctl reload nginx. Never skip the nginx -t step — a syntax error will prevent Nginx from reloading and may take your site offline.