Turn titles into clean URL slugs with Arabic transliteration, diacritic removal, stop words and a length limit
Redirect Rules Generator
Write redirect rules (from → to with a 301/302/307/308 code) and generate them for Apache .htaccess, Nginx, IIS web.config and Cloudflare _redirects, with correct regex escaping and detection of redirect loops and chains.
Workspace
Output
How the result is calculated
Each line /from /to [code] is read (default code 301). For Apache RewriteRule ^path$ target [R=code,L] is generated with every special regex character escaped (. + ? ( ) [ ] …) so it matches only that exact path. The rules are then followed over the paths: if a path returns to itself it is a loop, and more than one hop is a chain you are warned to shorten. Codes other than 301/302/307/308, invalid lines and duplicate sources are rejected.
Limits:
The simulation matches paths literally and is not equivalent to the full Apache engine (RewriteCond conditions, custom regex patterns, query strings). The tool does not test a live server and does not generate wildcard-pattern rules. Test the rules in a staging environment before production.
FAQ
What is the difference between 301 and 302?
301 is permanent and passes SEO signals; 302 is temporary.
Why warn about chains?
Every hop slows the page and weakens crawling; redirect once to the final destination.
