Local URL mapping · review before deployment
Generate 301 rules from a redirect map
Turn tab-separated old paths and destination URLs into reviewable Apache or Nginx 301 rules. Input stays in your browser; generated server configuration is not tested.
Paste a reviewed old-to-new URL map to create one 301 rule per row. This tool formats configuration locally; it does not fetch URLs, install rules, or test your server.
Use one mapping per line. The old value must be a path beginning with `/`, without a query or fragment. The destination must be an absolute HTTP or HTTPS URL. Blank lines and lines beginning with `#` are ignored.
No rules generated.
Example
/old-page/ → https://www.example.com/new-page/In the input box, replace the arrow with one real tab character; this display example is not directly pasteable as a mapping row.
Review and test before use
- Check that every destination is the intended, relevant replacement. Do not redirect unrelated or removed pages to the homepage just to avoid a not-found response.
- Apache output uses an exact path match in `RewriteRule`; Nginx output uses an exact `location =` match. The generated directives do not include a server block, domain-wide scheme policy, or query-string transformation.
- Apply rules only in the right configuration context and after checking existing rules. Order, proxy/CDN behavior, application routing, and server configuration can change the result.
- Test representative old URLs in staging or a controlled environment. Confirm the response status, `Location` header, final destination, and absence of loops or unintended chains.
Sources checked November 3, 2026
- Apache HTTP Server: RewriteRule and rewrite flags — Apache documents the pattern/substitution structure and flags such as `R` and `L`; exact behavior depends on configuration context.
- Nginx: return directive — the module can return a redirect with a specified status and URL; verify placement in the correct configuration context.
- Google Search Central: site moves with URL changes — prepare a URL map, implement redirects, test them, and monitor the move.
- Website migration checklist — prepare and record per-URL checks alongside the redirect map.
This tool validates input shape and emits text only. It cannot determine whether a mapping is correct for your site or whether the server will accept or execute the generated rules.
How it works
Choose Apache .htaccess or Nginx, then enter one old path and one absolute destination URL per line, separated by a tab. Generate the snippet, review each mapping, and test it in a suitable staging environment before deployment.
Good to know
Does this check that a redirect works on my server?
No. It validates the entered path and destination formats and creates configuration text in your browser. It does not contact a server, install rules, or test status codes, redirect chains, or loops at runtime.
What inputs does it accept?
Each non-empty line must contain an old path beginning with /, a tab, and an absolute HTTP or HTTPS destination URL. Old paths cannot include a query or fragment. Duplicate old paths and configuration characters that could change directive behavior are rejected.
Should every removed URL redirect to the homepage?
No. Review the destination for each old URL and use a relevant replacement only where one exists. For removed content without a replacement, choose the appropriate response with your site owner; this generator cannot decide that for you.
Impact — TODO: apply/approval and configure referral URL — referral link not configured.
CJ Affiliate — TODO: apply/approval and configure referral URL — referral link not configured.
PartnerStack — TODO: apply/approval and configure referral URL — referral link not configured.