Htaccess Redirect Generator by Toolwavee
Create clean 301, 302, HTTPS, www, non-www, page and domain redirect rules in seconds. Your URLs stay inside your browser.
Redirect settings
Choose a redirect type and enter the requested URLs.
Generated code
Review the rule before placing it in your .htaccess file.
Complete the form, then click Generate.
How to use this htaccess redirect generator
The Htaccess Redirect Generator by Toolwavee creates Apache redirect rules without requiring you to memorize rewrite syntax. The tool runs locally in your browser and does not send the URLs you enter to a server.
Choose a type
Select a page, domain, HTTPS, www, folder, or 410 rule.
Enter URLs
Provide the source, destination, or domain requested by the form.
Generate code
Click the button and carefully review the resulting directive.
Copy and test
Back up the file, paste the rule, save it, and test the old URL.
Which redirect status should you use?
| Status | Meaning | Recommended use |
|---|---|---|
| 301 | Moved permanently | A lasting URL change, deleted page with a close replacement, or permanent domain migration. |
| 302 | Found / temporary | A short campaign, temporary landing page, or change that will be reversed. |
| 307 | Temporary; preserves request method | A temporary move where POST and other request methods must remain unchanged. |
| 308 | Permanent; preserves request method | A permanent move that must preserve the original request method. |
| 410 | Gone | Content intentionally removed with no suitable replacement. |
Where should the code be added?
On many Apache hosting accounts, the file is located inside public_html or the document root of your domain. In cPanel File Manager, enable “Show Hidden Files” if you cannot see it. Download a backup before editing. On WordPress websites, place custom redirect rules before the standard # BEGIN WordPress block so WordPress does not overwrite them.
Important redirect best practices
- Redirect an old URL to the closest relevant replacement, not automatically to the homepage.
- Avoid redirect chains. Send the first URL directly to the final URL.
- Do not create a loop by redirecting a destination back to its source.
- Confirm the destination returns a successful response and is indexable when appropriate.
- After a migration, update internal links and your XML sitemap to use final URLs.
- Check hosting, WordPress plugins, CDN rules, and .htaccess for duplicate redirects.
Frequently asked questions
Does this tool change my website automatically?
No. It generates code only. You must review the rule and add it to the correct .htaccess file yourself.
Can I use this on WordPress?
Yes, if WordPress is hosted on Apache or an Apache-compatible server that permits .htaccess overrides. Always back up the existing file.
Will it work on Nginx?
No. Nginx does not use .htaccess files. Ask your hosting provider for an Nginx redirect rule.
Why am I seeing “Too many redirects”?
Your rule may send a URL back to itself or conflict with a hosting, CDN, SSL, or plugin redirect. Restore your backup and inspect every redirect layer.
Is the generated code guaranteed to work?
The generator creates standard rule patterns, but servers and existing configurations differ. Test on staging or ask your host or developer to review important changes.