.htaccess Redirect Generator

Generate .htaccess rules for forcing HTTPS, redirecting www to non-www (or vice versa), adding trailing slashes, and single-page 301/302 redirects.

Domain (for www/non-www rules)WWW handling

Force HTTPSAdd trailing slash to URLs

Redirect from pathRedirect to pathRedirect type

.htaccess rules

RewriteEngine On

# Force HTTPS
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# Redirect www to non-www
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]

# Add trailing slash
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ /$1/ [L,R=301]

# Single page redirect
Redirect 301 /old-page /new-page

For Apache servers with mod_rewrite enabled. Back up your existing .htaccess file before replacing it, and test on a staging site first, a bad rule can take your whole site offline.

Ad space

Frequently asked questions

Does this work on Nginx servers?+

No, .htaccess and mod_rewrite are Apache-specific. Nginx uses a different configuration syntax for redirects.

Why redirect www to non-www (or vice versa)?+

Search engines can treat www and non-www as separate URLs; consolidating to one version avoids splitting your SEO signals and prevents duplicate content issues.

Is a 301 or 302 redirect better for permanent changes?+

Use 301 for permanent moves; it passes SEO value to the new URL and tells browsers and search engines to update their records. Use 302 only for genuinely temporary redirects.