Redirect Rules Generator
Create a single path redirect or migrate same-path URLs from a URL list, HTML page, XML sitemap, text file, or JSON file. Processing stays in your browser.
Paste absolute HTTP(S) URLs or paths beginning with /. Migration keeps each path and query on the destination origin.
No file selected.
One .html, .xml, .txt, or .json file; maximum 10 MB. Links and sitemap locations are extracted locally.
Choose a rule type and enter the source information.
Imported files stay in this browser. Review generated rules before applying them; the tool does not test or deploy server configuration.
A QUICK WALKTHROUGH
How to use this tool
- Choose a single redirect or URL migration, then enter a path and target or select migration URLs.
- Choose Apache or Nginx, a 301 or 302 status, and optional HTTPS or www canonicalization.
- Generate, review, copy, or download the rules before adding them to your server configuration.
Single redirects and URL migrations
Single mode maps one source path to an absolute HTTP(S) target URL. Migration mode reads absolute URLs or extracts links from one local HTML, XML sitemap, TXT, or JSON file up to 10 MB, then maps same-origin paths and queries to a new origin. Files are never uploaded.
Choose server syntax
Apache output uses mod_rewrite directives for .htaccess. Nginx output uses exact-match location blocks and is intended for placement inside the matching server block. These are configuration drafts; review rule order and server context before use.
Local validation and limits
The browser accepts only HTTP(S) origins, rejects unsafe host/path input, deduplicates migration URLs, and limits generated rules to 10,000. HTTPS and canonical-host rules use the selected redirect status. The tool does not contact or change your server.
GOOD TO KNOW
Common questions
Does the tool deploy rules to my server?
No. It creates text locally for you to review and place in your server configuration.
Which files can migration mode read?
One .html, .xml, .txt, or .json file up to 10 MB. HTML links and XML sitemap loc values are extracted locally; TXT uses one URL per line and JSON string values containing HTTP(S) URLs are collected.
Does batch migration change URL paths?
No. It keeps each source path and query on the destination origin. Use single mode when an individual URL needs a different destination path.
Where should I place Nginx output?
Inside the appropriate Nginx server block. Nginx does not read .htaccess files.