A 301 redirect is permanent and tells search engines to transfer all ranking power (link equity) to the new URL. A 302 redirect is temporary and signals that the original URL may return, so search engines keep the old URL indexed. Use 301 for permanent moves and 302 for short-term changes such as A/B tests or maintenance pages.
Redirect Generator — htaccess & Nginx
Generate Apache .htaccess and Nginx redirect rules instantly. Supports 301, 302, 307 and 308 redirects, bulk mode, domain moves, HTTPS enforcement, www normalization, trailing slash rules and regex patterns. A free tool by WebEvra.
Single URL Redirect
Bulk Redirects
Format: old-path,new-path — one pair per line, separated by comma or tab.
Domain Redirect
Force HTTP to HTTPS
Redirect all HTTP traffic to HTTPS. The redirect type for this rule is always 301.
WWW Normalization
Trailing Slash Rule
Regex Redirect
Use $1, $2, etc. for capture group backreferences. Apache uses RewriteRule; Nginx uses rewrite.
Generated Code
Generated redirect rules will appear here...
Combined Rules 0 rules
Add rules above to combine them here...
About This Tool
This free Redirect Generator by WebEvra helps developers and site owners create server-side redirect rules without memorizing the syntax for Apache .htaccess or Nginx configuration files. Whether you are migrating a website, enforcing HTTPS, normalizing URLs, or setting up bulk redirects during a domain change, this tool generates production-ready code that you can copy and paste directly into your server configuration. Everything runs client-side in your browser — no data is sent to any server.
Frequently Asked Questions
To create a redirect in .htaccess, add a line like
Redirect 301 /old-page https://example.com/new-page to your .htaccess file in the site root. For pattern-based redirects, enable mod_rewrite with RewriteEngine On and use RewriteRule directives. This tool generates the correct syntax for you automatically.In Nginx, redirects are configured inside a server block using
return 301 https://example.com/new-page; for simple redirects or rewrite ^/old-path$ /new-path permanent; for pattern-based rules. Unlike Apache, Nginx does not use .htaccess files; changes must be made in the Nginx configuration and the server reloaded.Yes, redirects significantly affect SEO. A properly implemented 301 redirect passes approximately 95-99% of link equity to the new URL, preserving your search rankings. Redirect chains (multiple hops) can dilute link equity and slow crawling. Always use 301 for permanent URL changes, avoid redirect loops, and keep chains to a minimum for best SEO results.
Apache uses .htaccess files with mod_rewrite directives that are read on every request and can be placed in any directory. Nginx uses centralized configuration files inside server blocks and requires a server reload after changes. Nginx is generally faster because it does not re-read config files per request. The redirect logic is equivalent, but the syntax differs significantly between the two servers.