Domain Name

Select redirect type

Redirect From www to non-www Redirect From non-www to www

Get Your HtAccess Code

Htaccess Redirect Generator: Build Working Apache Redirects in Seconds

The Htaccess Redirect tool from Tools Hub turns a confusing, error-prone Apache configuration task into a simple form you can fill out in under a minute. Instead of memorizing arcane RewriteRule syntax or copying snippets from forums that may or may not work on your server, you describe what you want — redirect an old page to a new one, force HTTPS, move a whole domain, or send everything to your homepage — and the tool generates clean, copy-ready .htaccess code. It is a free htaccess redirect generator that requires no sign-up, adds no watermark to your output, and runs entirely in your browser so the rules you build are never uploaded to a server.

Anyone who runs a website on Apache hosting needs reliable redirects at some point. Bloggers migrating to a new permalink structure, store owners retiring discontinued product pages, developers consolidating two sites into one, and SEO specialists preserving link equity after a redesign all rely on htaccess 301 redirect rules to keep traffic and search rankings intact. If you have ever searched for how to redirect using htaccess, htaccess redirect to another domain, or htaccess redirect http to https and ended up with code that broke your site or did nothing at all, this generator was built for you. It produces standards-compliant directives that work with mod_rewrite and the classic Redirect directive, so you get working redirection in htaccess the first time.

How to Create an Htaccess Redirect

Generating a redirect with this tool follows a short, predictable path. You never touch raw configuration until the code is ready to paste. Here is the full process from start to finish:

1. Choose your redirect type. Pick from the common scenarios: redirect a single old URL to a new URL, redirect an entire domain to another domain, force HTTP to HTTPS, force www to non-www (or the reverse), redirect all pages to the homepage, or set up a custom wildcard pattern. Each type loads the correct directive style.
2. Enter the source URL or path. Type the old address you want to move away from — for example /old-page.html or an entire host like old-domain.com. The tool accepts both relative paths and full URLs and normalizes them for you.
3. Enter the destination. Provide the target the visitor should land on, such as /new-page.html or https://new-domain.com. For domain moves, the tool can preserve the rest of the path automatically so deep links keep working.
4. Select the status code. Choose 301 for a permanent move (the right choice for SEO and the most common option), or 302 for a temporary redirect. The tool defaults to 301 because that is what preserves search rankings.
5. Toggle extra options. Decide whether to preserve query strings, match case-insensitively, or append a trailing-slash rule. These switches let you fine-tune behavior without writing the flags by hand.
6. Generate the code. Click the button and the tool instantly outputs a clean block of .htaccess directives, complete with the required RewriteEngine On line where needed.
7. Copy and paste. Use the one-click copy button, then open your site's root .htaccess file and paste the block near the top. Save, upload, and test in a private browser window.

That is the entire workflow. You can build a single rule and leave, or stack several redirects in one session and paste the whole set at once.

Why Use the Htaccess Redirect Tool

Hand-writing Apache rewrite rules is one of those tasks that looks simple until a stray slash or a missing flag silently breaks your whole site. This generator removes that risk and saves real time. Here are concrete situations where it earns its place in your toolkit:

• Site migrations and redesigns. When you change your CMS, theme, or URL structure, hundreds of old links can break overnight. Generate a batch of htaccess 301 redirect rules so every legacy URL points to its new home and your Google rankings transfer cleanly.
• Moving to a new domain. Rebranding or merging companies? Use the htaccess 301 redirect to new domain option to forward every visitor and every backlink from the old domain to the new one while keeping the deep path intact.
• Forcing HTTPS. After installing an SSL certificate you must send all http:// traffic to https://. The http to https redirect htaccess preset writes the secure-redirect rule correctly, including the condition that prevents infinite loops.
• Standardizing www vs non-www. Search engines treat www.example.com and example.com as separate sites unless you pick one canonical version. A single generated rule consolidates them.
• Retiring product or blog pages. When you discontinue an item or merge two articles, redirect the old URL to the closest relevant page instead of dropping visitors on a 404.
• Consolidating thin content to the homepage. The htaccess redirect all pages to homepage option is handy during a temporary maintenance phase or when sunsetting a microsite.
• Cleaning up index files. Redirect index.php or index.html to the root so your homepage has one clean canonical URL — a frequent request behind searches like redirect index.php to root htaccess.

Understanding the .htaccess File and Apache Redirects

To use redirects well, it helps to understand what you are actually editing. The .htaccess file (the leading dot makes it hidden on Unix systems) is a per-directory configuration file read by the Apache web server. When a request comes in, Apache checks for an .htaccess file in the requested directory and its parents, then applies any directives it finds before serving the page. Because it works on a per-directory basis and is read on every request, it lets you change server behavior — including redirects — without touching the main server config or restarting Apache.

The two ways to write a redirect

There are two main mechanisms, and knowing the difference clears up most confusion you see in searches like htaccess not redirecting properly:

The Redirect and RedirectMatch directives (mod_alias). These are the simplest. A line like Redirect 301 /old-page.html https://example.com/new-page.html tells Apache to send a permanent redirect. RedirectMatch adds regular-expression matching for patterns. This style is easy to read and perfect for straightforward one-to-one moves.

The RewriteRule directive (mod_rewrite). This is the powerful engine behind complex redirects — forcing HTTPS, handling wildcards, preserving query strings, and applying conditions with RewriteCond. A typical HTTPS rule looks like RewriteEngine On followed by RewriteCond %{HTTPS} off and RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]. The tool generates whichever mechanism fits your chosen scenario, so you never have to decide which module to invoke.

301 versus 302: which status code to pick

The HTTP status code your redirect returns matters enormously for SEO. A 301 means "Moved Permanently" — it tells browsers and search engines that the old URL is gone for good and that ranking signals should flow to the new URL. This is what you want for nearly every migration. A 302 means "Found / Moved Temporarily" — search engines keep the old URL indexed because you have signaled the change is short-lived. Use 302 only for genuinely temporary situations like A/B tests or seasonal promotions. Picking the wrong code is a common, quiet cause of lost rankings, which is why this generator defaults to 301 and asks you to opt into 302 deliberately.

Common Redirect Recipes This Tool Generates

Below are the most-requested patterns, all of which the generator produces with the correct syntax and safeguards built in.

Redirect one URL to another URL

The bread-and-butter case behind searches like htaccess redirect url to another url. You supply the old path and the new destination, choose 301, and the tool outputs a single tidy line. Because it uses an exact match, unrelated pages stay untouched.

Redirect to another domain while keeping the path

For a full move, the htaccess redirect to another domain recipe forwards every request to the new host. With path preservation enabled, a visitor who bookmarked old.com/blog/article lands on new.com/blog/article rather than the bare homepage — critical for keeping backlinks valuable.

Force HTTPS for the whole site

The http to https htaccess recipe includes the RewriteCond %{HTTPS} off guard so the rule fires only on insecure requests, avoiding the redirect loop that catches so many people. This is the secure way to handle securely redirect with htaccess after enabling SSL.

Wildcard and folder redirects

Need to move an entire directory? The htaccess redirect wildcard and htaccess redirect to folder options use pattern matching to map /old-folder/anything to /new-folder/anything in one rule, so you do not have to list every file individually.

Redirect everything to the homepage or to the index

When you want a clean sweep, the tool writes a catch-all that sends every request to /. Variations cover htaccess redirect to index and the reverse — stripping index.html or index.php from URLs so your homepage resolves to the clean root address.

Tips for Reliable Redirects

A few habits separate redirects that just work from ones that cause support tickets. Keep these in mind as you deploy the code this tool produces.

• Place redirect rules near the top of the file. Apache reads .htaccess top to bottom. Put your redirects before caching, compression, or WordPress rewrite blocks so they take effect first.
• Always test in a private window. Browsers cache 301 redirects aggressively. Use an incognito or private window, or a different device, when verifying so you are not fooled by a cached result.
• Back up the original file first. Before pasting anything, copy your existing .htaccess to .htaccess.bak. If something misbehaves, you can restore in seconds.
• Avoid chaining redirects. Sending A to B to C wastes time and dilutes SEO value. Point every old URL directly at its final destination.
• Mind the order of HTTPS and domain rules. If you force HTTPS and change domains, sequence the rules so a visitor is not bounced twice. The tool helps by letting you combine these into a single clean block.
• Use 301 for permanent changes only. Because browsers cache permanent redirects, a 301 you set by mistake is hard to undo on visitors who already cached it. Be sure before you commit.

Editing .htaccess on Windows, Mac, iPhone, and Android

One advantage of this generator is that it runs in any modern browser, so you can build redirect code on whatever device is in front of you and apply it however you manage your site.

On Windows and Mac

Open the tool in Chrome, Edge, Firefox, or Safari, generate your rule, and copy it. Then edit .htaccess using your hosting control panel's file manager, an FTP client like FileZilla, or a code editor such as VS Code. On Windows, remember the file has no name before the dot, so save it as .htaccess exactly — some editors add a hidden .txt extension you must remove.

On iPhone and Android

The generator is fully responsive, so you can create a redirect from your phone while away from your desk — handy when a site emergency strikes. Generate the code, copy it, and paste it into your host's mobile file manager or a mobile FTP app. Because the tool needs no installation and stores nothing, it works the same on iOS Safari and Android Chrome as it does on desktop.

Privacy and Security

Redirect rules can expose the structure of your site, so it matters where the code is built. This htaccess redirect generator performs all logic in your browser using JavaScript. The URLs you type and the directives that come out are never transmitted to Tools Hub or any third party — there is no upload step and nothing is logged. You can disconnect from the internet after the page loads and the generator still works. Combined with no sign-up requirement and no account, this makes it safe to use even with internal or staging URLs you would not want to share. As always, the file you ultimately edit lives on your own server, fully under your control.

Tips & Troubleshooting

Why is my htaccess redirect not working at all?

The most common cause is that AllowOverride is set to None on your server, which makes Apache ignore .htaccess files entirely. Check with your host that overrides are enabled. The second most common cause is that the file is named incorrectly — it must be literally .htaccess with the leading dot and no extension. Also confirm mod_rewrite is enabled if your rule uses RewriteRule.

Why do I get a "too many redirects" loop error?

This usually happens with HTTPS or www rules that lack a proper condition, so the rule keeps firing on its own output. The code this tool generates includes the necessary RewriteCond guards to prevent loops. If you wrote a rule by hand, regenerate it here and replace the old block.

My redirect works but drops the path or query string. How do I fix it?

Enable the "preserve path" and "preserve query string" options before generating. For domain moves, path preservation maps the full original URL onto the new host. Without it, every request lands on the bare homepage, which hurts both users and SEO.

Should I put the redirect above or below my WordPress rules?

Place custom redirects above the # BEGIN WordPress block. WordPress controls everything between its BEGIN and END markers and may rewrite that section, so rules placed inside it can be lost during updates. Keeping yours above the block keeps them safe and gives them priority.

Will a 301 redirect hurt my Google rankings?

No — done correctly, a 301 passes the large majority of ranking signals to the new URL and is the recommended way to move content. Problems arise only from chains, loops, or using 302 by mistake. Stick to direct 301s and your rankings should transfer smoothly.

The redirect appears cached and I cannot test changes. What now?

Browsers cache 301 responses hard. Test in a fresh incognito window, clear your browser cache, or use an online HTTP header checker that does not cache. On your own machine you can also append a dummy query string to force a fresh request.

Related Tools

Tools Hub offers a full suite of free web utilities that pair naturally with redirects. If you are managing a site, these are worth bookmarking:

• Robots.txt Generator — create a clean crawler-control file to sit alongside your redirect rules and guide search engines.
• HTML Minifier — shrink page markup for faster loads once your new URLs are live.
• URL Encoder / Decoder — safely encode special characters in destination URLs before pasting them into a rule.
• Meta Tag Generator — build canonical and SEO meta tags that reinforce the canonical URLs your redirects establish.
• QR Code Generator — turn your new canonical URLs into scannable codes for print and packaging.
• Password Generator — create strong credentials for the FTP and control-panel accounts you use to upload the edited file.

Frequently Asked Questions

Is the Htaccess Redirect tool really free?

Yes. The generator is completely free with no hidden tiers, no usage caps, and no credit card. You can build as many redirect rules as you need, as often as you like, at no cost.

Do I need to create an account or sign up?

No. There is no sign-up, no login, and no email required. Open the page and start generating .htaccess code immediately.

Does the generated code contain any watermark or branding?

No. The output is clean, standard Apache configuration with no comments advertising the tool, no hidden tracking, and no watermark. What you copy is exactly what runs on your server.

Are my URLs uploaded anywhere?

No. Everything happens locally in your browser. The source and destination URLs you enter never leave your device, which makes the tool safe for internal, staging, or confidential addresses.

Can this tool redirect to another domain and keep the full path?

Yes. Choose the domain-redirect option and enable path preservation. A request to old.com/blog/post will then forward to new.com/blog/post instead of dropping the visitor on the homepage, which protects your backlinks and user experience.

Can I force HTTP to HTTPS with this generator?

Absolutely. The http to https redirect htaccess preset writes the secure-redirect rule with the loop-prevention condition included, so once your SSL certificate is installed every visitor is sent to the encrypted version of your site.

Does it support wildcard and folder-wide redirects?

Yes. Use the wildcard or folder option to map an entire directory to a new location in a single rule, so you do not have to enumerate every file. This covers the common htaccess redirect wildcard and folder-migration cases.

What is the difference between 301 and 302, and which should I choose?

A 301 is a permanent redirect that passes SEO value to the new URL and is the right choice for almost all moves. A 302 is temporary and keeps the old URL indexed; use it only for short-lived changes like tests or promotions. The tool defaults to 301 so you get the SEO-safe option automatically.

Will these rules work on Nginx or only Apache?

The .htaccess format is specific to the Apache web server (and Apache-compatible setups like LiteSpeed). Nginx uses a different configuration syntax and does not read .htaccess files, so these rules are intended for Apache-based hosting, which covers the majority of shared and managed WordPress plans.