How do I create a 301 redirect in htaccess?

Add a line like "Redirect 301 /old-page /new-page" to your .htaccess file. This generator builds those lines for you: enter each old → new pair, pick 301, copy the output, and paste it near the top of .htaccess. A 301 tells browsers and search engines the move is permanent, passing most SEO value to the new URL.

What is the difference between 301 and 302 redirects?

A 301 is permanent: search engines transfer ranking signals to the new URL and browsers may cache it. A 302 is temporary: search engines keep the old URL indexed and do not pass full ranking value. Use 301 for renamed pages and site migrations, 302 for short-term changes like a holiday page or A/B test.

How do I redirect an old URL to a new URL in htaccess?

List the pair as "/old-url -> /new-url" in the generator's "Redirect pairs" field (targets can be paths or full https:// URLs), choose 301, and paste the generated "Redirect 301" line into .htaccess. Then test the old URL — it should land on the new one with a 301 status.

How do I force HTTPS with htaccess?

Tick "Force HTTPS" in the generator. It adds the standard block: "RewriteCond %{HTTPS} off" plus "RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]", which 301-redirects every http:// request to https://. Paste it with "RewriteEngine On" above it.

How do I redirect www to non-www in htaccess?

Set "WWW handling" to "www-to-non-www". The tool generates a host-condition block that 301-redirects every www.example.com request to example.com. Pick one canonical version (www or non-www) and use it consistently — mixing them splits SEO signals.

Do htaccess redirects affect SEO?

Done right, no: 301 redirects pass most ranking signals, which is why migrations use them. Problems come from redirect chains (A→B→C), redirect loops, or 302s used for permanent moves. After deploying, crawl the old URLs and confirm each returns a single 301 straight to the final destination.

Htaccess Redirect Generator

What is Htaccess redirect generator?

Htaccess Redirect Generator — Generate Apache .htaccess redirect rules in seconds: 301/302 redirects, force HTTPS, plus www handling — copy-paste ready output, free, no signup.

This tool generates Apache .htaccess rules with the open-source htaccess-redirect-generator engine (0xelitesystem, MIT), mechanically ported from its pure generation core: each pair becomes an Apache "Redirect <code> <from> <to>" line (mod_alias), while the optional blocks emit standard mod_rewrite rules — "RewriteCond %{HTTPS} off" for force-HTTPS and host-condition RewriteRules for www-to-non-www / non-www-to-www. Old paths are validated as site paths (not full URLs) and normalized to a leading slash, exactly like the engine. One deliberate one-character fix vs upstream: the vendored www conditions contained a double backslash (^www\\.) that never matches a real www host; this tool emits the correct ^www\. instead. Limitations: literal paths only — no wildcards or regex, one pair per line; the tool never checks that old paths exist or targets respond, so verify every rule after deploying; output assumes Apache with mod_rewrite/mod_alias and does nothing on Nginx or hosts that ignore .htaccess.

Why use this htaccess redirect generator?

🎯

Built for htaccess redirect generator

Generate Apache .htaccess redirect rules in seconds: 301/302 redirects, force HTTPS, plus www handling — copy-paste ready output, free, no signup.

📋

Transparent & honest

Path redirects are literal "Redirect <code> <from> <to>" lines (mod_alias) — no wildcards, regex, or query-string matching.

🔒

Private by design

Everything runs in your browser. Your inputs never leave your device.

📱

Works everywhere

Fully responsive — perfect on desktop, tablet, and mobile. No app needed.

🔄

Regularly updated

Regularly maintained and reviewed to ensure accuracy.

💡

Free forever

No accounts, no limits, no watermarks. Use Htaccess Redirect Generator as much as you need.

How to use Htaccess Redirect Generator

1List each redirect in the "Redirect pairs" box, one per line, as /old-page -> /new-page (the target may be a path or a full https:// URL).
2Choose the "Redirect type": 301 for permanent moves (passes SEO value to the new URL), 302 for temporary ones.
3Tick "Force HTTPS" to redirect the whole site to https://, and use "WWW handling" to standardize on www or non-www.
4Run the tool and copy the generated rules from the ".htaccess rules" output.
5Paste the rules near the top of your site's .htaccess file, save, then test an old URL in a private browser window (or curl -I) to confirm the redirect status code.

What can you do with Htaccess Redirect Generator?

Htaccess redirect generator — Generate Apache .
301 redirect htaccess — Generate Apache .
Apache redirect generator — Generate Apache .
Redirect old url to new url htaccess — Generate Apache .
Force https htaccess — Generate Apache .

Good to know

Path redirects are literal "Redirect <code> <from> <to>" lines (mod_alias) — no wildcards, regex, or query-string matching.
Old paths must be site paths like /old; full URLs as the source are rejected, matching the engine.
The tool does not verify old paths exist or targets respond — test every rule after deploying (curl -I the old URL).
Output assumes Apache with mod_rewrite/mod_alias enabled; it has no effect on Nginx or hosts that ignore .htaccess.

How it works

This tool generates Apache .htaccess rules with the open-source htaccess-redirect-generator engine (0xelitesystem, MIT), mechanically ported from its pure generation core: each pair becomes an Apache "Redirect <code> <from> <to>" line (mod_alias), while the optional blocks emit standard mod_rewrite rules — "RewriteCond %{HTTPS} off" for force-HTTPS and host-condition RewriteRules for www-to-non-www / non-www-to-www. Old paths are validated as site paths (not full URLs) and normalized to a leading slash, exactly like the engine. One deliberate one-character fix vs upstream: the vendored www conditions contained a double backslash (^www\\.) that never matches a real www host; this tool emits the correct ^www\. instead. Limitations: literal paths only — no wildcards or regex, one pair per line; the tool never checks that old paths exist or targets respond, so verify every rule after deploying; output assumes Apache with mod_rewrite/mod_alias and does nothing on Nginx or hosts that ignore .htaccess.

Examples

Single 301 after a URL change

Output: "Redirect 301 /old-blog-post /blog/new-post" — paste-ready, passes link equity to the new URL.

Site migration with HTTPS

Two 301 Redirect lines plus the force-HTTPS RewriteCond/RewriteRule block.

Standardize on non-www

Adds the www-to-non-www host-condition block so every www URL 301s to the bare domain.

People also search for these — this tool handles them all:

htaccess redirect generatorhtaccess redirect generator301 redirect htaccessapache redirect generatorredirect old url to new url htaccessforce https htaccess