Moving pages or a whole domain? Enter old and new URLs and get ready-to-paste 301 redirect rules for your server or platform, so visitors and backlinks land on the right page.
How to use the 301 redirect generator
- Enter old → new URL pairs, one per line.
- Choose your platform: Apache, Nginx, Vercel, Next.js, Netlify or Cloudflare.
- Copy the rules into your config and test a few with the redirect checker.
When to use a 301
Whenever a URL changes for good: a renamed page, a new site structure, http to https, or a domain move. A 301 passes the old URL's link value to the new one and tells search engines to swap it in their index.
Avoid these mistakes
Don't redirect everything to the home page; map each old URL to its closest new page. Avoid chains (A → B → C), and keep redirects in place for at least a year.
Reading the generated rules
Each line is an old path and a new path separated by a space, and the old path must start with /. A * at the end of the old path matches everything below it, and :splat in the new path carries that part across, so /product/* to /products/:splat moves a whole section. Lines that don't fit this format are skipped. Next.js and Vercel write permanent: true, which those platforms send as a 308; search engines treat it like a 301. Netlify, Nginx and Apache use the code you pick. The Cloudflare file is a bulk redirect CSV with example.com as the domain, so replace it with yours before importing.
When redirects don't work
On Apache, Netlify, Vercel and Next.js the first matching rule wins, so put specific rules above wildcards. Apache rules need mod_rewrite enabled and an .htaccess file the server is allowed to read. In Nginx, reload the config after editing. A page that still exists at the old path may be served before the redirect runs on some platforms; delete the old page. If the browser keeps going to the wrong place after a fix, it has cached an old 301; test in a private window or with the redirect checker.