>_ tools --redirects

Bulk .htaccess 301 Redirect Generator

Paste your old → new URLs, review every row in a validated table (so you see what will be generated), then pick the redirect method, status and matching - and paste the result into .htaccess. Everything runs in your browser; nothing is uploaded.

STEP 1 - Paste old → new URLs

One pair per line. Separate with comma, tab, semicolon, pipe or 2+ spaces. A header row like "old,new" is skipped automatically.

0 lines

STEP 2 - Review & fix

0 redirects

Every row is shown and validated. Edit a path by tapping it; remove a row with the ×.

StatusOld URLNew URL

STEP 3 - Options & generate

OUTPUT - .htaccess redirect block

0 chars
Where to put it: paste the generated block ABOVE the WordPress permalink rules in your .htaccess - The [R=301,L] flag stops processing, so rules above permalinks win. Test on a staging URL before going live; a 301 is cached by browsers and search engines, so a wrong redirect is hard to undo.
no server · everything computed in your browser · one HTML file
.htaccess Generator The full config - this tool does the redirect chapter. Nginx Config Generator The same redirects, translated for Nginx. .htaccess ⇄ Nginx Converter Port an existing redirect block to another server. Debug Log Analyzer If a redirect loops, the log tells you why.

>_ FAQ

Where do I put the redirect block?

Paste it ABOVE the WordPress permalink rules in your .htaccess. The [R=301,L] flag stops processing, so rules above permalinks win.

Does it escape special characters?

Yes - regex metacharacters in old URLs (dots, plus, parens, etc.) are auto-escaped so the pattern matches literally. Full URLs are collapsed to clean path targets.

Can I include query strings or trailing slashes?

Yes - toggle options let you match optional trailing slashes and carry query strings through the redirect.