.htaccess Redirect Generator

An .htaccess redirect is a directive in Apache's .htaccess configuration file that automatically sends visitors and search engines from one URL to another. The .htaccess file is a per-directory configuration file that Apache reads on every request, making it the standard way to manage redirects on shared hosting and Apache-based servers without modifying the main server configuration. Our .htaccess redirect generator produces two types of directives: the simple Redirect directive for exact path matches, and the more powerful RewriteRule directive (which requires RewriteEngine On) for prefix wildcards and regular expression patterns.

1. 1. Add Your Redirect Rules: Enter the source path (e.g. /old-page) and destination URL (e.g. https://example.com/new-page) for each redirect. Choose the redirect type (301, 302, 307, 308) and match mode (exact, prefix, or regex). Add as many rules as needed using the "Add Another Rule" button. All generation runs locally in your browser - your URLs never leave your device.
2. 2. Instant Browser-Based Generation: Click "Generate .htaccess" and the tool produces the correct Apache directives for each rule. Exact matches use the Redirect directive. Prefix and regex matches use RewriteRule with the appropriate flags. The RewriteEngine On header is added automatically when needed.
3. 3. Copy or Download: Copy the generated rules to your clipboard or download the complete .htaccess file. Paste the rules into your existing .htaccess file or upload the downloaded file to your server's web root directory.

• 301 - Permanent Redirect: Tells browsers and search engines that the resource has permanently moved. Browsers cache the redirect and search engines transfer link equity (PageRank) to the new URL. Use 301 for permanent URL changes, domain migrations, and HTTP → HTTPS.
• 302 - Temporary Redirect: Tells browsers the resource has temporarily moved. Browsers do not cache the redirect and search engines do not transfer link equity. Use 302 for maintenance pages, A/B testing, and temporary promotions.
• 307 - Temporary (Method Preserved): Like 302 but guarantees the HTTP method (GET, POST) is preserved in the redirect. Use 307 when redirecting form submissions or API endpoints temporarily.
• 308 - Permanent (Method Preserved): Like 301 but guarantees the HTTP method is preserved. Use 308 for permanent redirects of API endpoints or form submissions where the method must not change.

The .htaccess file must be placed in the directory you want the rules to apply to - usually the web root (public_html or www). Apache must have AllowOverride All (or at least AllowOverride FileInfo) enabled in the server configuration for .htaccess files to be processed. Test your redirects after uploading using a browser or a tool like curl to verify they work as expected. Incorrect .htaccess rules can cause redirect loops or 500 errors - always keep a backup of your original .htaccess file before making changes.