301 is a permanent move: it passes ranking signals to the new URL. 302 is temporary and does not. For a URL that has moved for good, use 301.

Where do I put these?

nginx: in your server block. Apache: in .htaccess or the vhost. Cloudflare Pages / Netlify: a _redirects file at the site root. Shopify: use the URL Redirects screen in admin, not a file.

How many redirects is too many?

One hop is fine; chains (A to B to C) are not. Point every old URL straight at its final URL, and update internal links so they do not redirect at all.

Does this fetch anything?

No. It formats the rules from what you paste, entirely in your browser.

Generate your 301 redirects

One line per move: the old path, then the new path. This produces the rules for nginx, Apache, Cloudflare Pages / Netlify and a note for Shopify, so a migration does not lose the pages that already rank.

How to use it

Paste the output where your server reads it, then check that each old URL resolves in one hop with the redirect check. Prefer absolute paths for the new URL. If you moved a whole section, a single prefix rule beats hundreds of lines.

Questions

Why 301 and not 302?: 301 is a permanent move: it passes ranking signals to the new URL. 302 is temporary and does not. For a URL that has moved for good, use 301.
Where do I put these?: nginx: in your server block. Apache: in .htaccess or the vhost. Cloudflare Pages / Netlify: a _redirects file at the site root. Shopify: use the URL Redirects screen in admin, not a file.
How many redirects is too many?: One hop is fine; chains (A to B to C) are not. Point every old URL straight at its final URL, and update internal links so they do not redirect at all.
Does this fetch anything?: No. It formats the rules from what you paste, entirely in your browser.