How to use the 301 Redirect Generator
- 1
Paste one redirect per line: the old URL, then the new URL, separated by a comma, tab or space.
- 2
Choose your server: Apache, Nginx, or Netlify and Cloudflare Pages.
- 3
Fix any chains or loops flagged, then add the rules and test a few old URLs.
Why redirects protect rankings
When a URL changes, a 301 redirect tells Google the page moved permanently and passes its ranking signals to the new address. Missing redirects turn backlinks and bookmarks into 404s, which is the most common reason traffic drops after a redesign or platform move.
Avoid chains and loops
Each extra hop slows the redirect and weakens the signal. The generator flags:
- Chains: A redirects to B, which redirects to C (point A straight to C)
- Loops: A redirects to B, which redirects back to A
- Duplicates: the same old URL listed twice with different targets
- Self-redirects: an old URL that points to itself
A safe migration checklist
Crawl the old site before launch, map every URL that has traffic or backlinks, launch the redirects with the new site, then crawl the old URL list again to confirm each returns a single 301 to a 200 page. Watch the Pages report in Search Console for a few weeks.
Frequently asked questions
301 or 302?
Use 301 for permanent moves so ranking signals transfer. Use 302 only for temporary changes.
Should I redirect everything to the homepage?
No. Redirect each old page to its closest equivalent. Google treats mass redirects to the homepage like 404s.
How long should redirects stay in place?
At least a year, and ideally permanently for URLs with backlinks.
Is my data stored?
No. Rules are generated in your browser.