.htaccess redirect rules visual builder. Essential for migrations, HTTPS, www, trailing slashes.
Per-URL redirects
📄 .htaccess

How to use

  1. Pick a preset (HTTPS, www, trailing slash, etc.) or add custom rules.
  2. Set source URL, destination, and status (301/302) per rule.
  3. Upload the generated .htaccess to site root (public_html/.htaccess).
  4. Test on the live server (clear browser cache).

Key features

  • 6 presets (HTTPS · www · non-www · both trailing slash modes · custom)
  • 301 (permanent) / 302 (temporary)
  • Auto RewriteRule regex generation
  • Multiple rules at once
  • Comments include/exclude option

Use cases

  • Site migration — old URL → new URL 301 redirect (SEO preserved)
  • Force HTTPS — http → https
  • www normalization — prevent Google treating as separate domain
  • Trailing slash — avoid /page vs /page/ duplicate indexing
  • Domain consolidation — after M&A

301 vs 302

301 (permanent) tells search engines "URL moved permanently" — SEO juice transfers to the new URL. Essential for migrations. 302 (temporary) means "temporarily elsewhere" so engines keep the original URL. Use for A/B tests or maintenance. Wrong choice loses SEO — always use 301 for migrations.

FAQ

.htaccess not working.

(1) Check it's Apache (Nginx needs different config) (2) AllowOverride All must be set (3) mod_rewrite must be enabled.

What about Nginx?

Use rewrite or return 301 in nginx.conf. Separate tool coming.

WordPress .htaccess conflict?

Place this tool's rules above the WordPress default block (# BEGIN WordPress).

Free?

Yes.