Map each old path
Use exactly two columns: a source path and its destination. Sources are exact paths, without wildcards or queries.
Publishing & SEO / Made for the task at hand
Turn a source-to-target CSV into exact-path Nginx or Netlify-style 301 redirects. Catch duplicate paths and simple redirect loops before exporting rules.
Add your source, or try the example, then choose “Build redirect rules”.
Results are temporary. Download anything you want to keep.
A practical little workflow
Use exactly two columns: a source path and its destination. Sources are exact paths, without wildcards or queries.
Duplicate sources, self redirects, simple relative-path loops and unsupported characters produce errors.
Download the rules, keep a backup and test on your own hosting. No destination availability check is made.
Before you get started
Built for a focused job.
Review important results before use.
Inside the appropriate server block. Run your server’s configuration test before reloading. Existing locations and other rules can change behavior. Nginx sources with percent escapes are rejected because its location matching uses normalized URIs; use a tested custom rule for those paths.
No. It generates conservative exact-path rules. It does not crawl your site, follow external redirect chains or verify target responses.
The _redirects format is hosting-specific. Verify your provider’s supported syntax, rule limits and precedence before using it. Query forwarding depends on the hosting platform.
Working text and local files are processed in this browser tab and are not sent to a server or an AI service. Reloading clears this workspace. Optional analytics and feedback have separate privacy controls; see Privacy below.