Netlify _redirects generator
One line per move: the old path, then the new path. The link redirect generator outputs the rules for nginx, Apache, Cloudflare Pages / Netlify and a note for Shopify, so a migration does not lose the pages that already rank.
Netlify _redirects file
Use the "Cloudflare Pages / Netlify" card below. Save it as a file called _redirects with no extension in your publish directory (for example public/ or dist/), so it ends up in the deployed site root. Each line is /old /new 301; Netlify reads the rules top to bottom and the first match wins.
For a folder, use a splat: /blog/* /articles/:splat 301. You can also put rules in netlify.toml under [[redirects]]; the _redirects file is processed first.
How to use it
Plan the moves first with a redirect mapping template and migration QA workflow. For server configuration, see Nginx 301 redirect examples.
Paste the output where your server reads it, then check that each old URL resolves in one hop with the bulk URL checker. Prefer absolute paths for the new URL. If you moved a whole section, a single prefix rule beats hundreds of lines.
Example: enter /old-product /products/new-product. The nginx output is location = /old-product { return 301 /products/new-product; }. After publishing the rule, paste https://your-site.example/old-product into the bulk checker. Look for one 301 hop followed by a 200 at the intended product page; a second redirect or an unrelated destination needs a rule change.