Redirect Generator
Redirect Generator is a free tool that turns old and new page addresses into redirect rules for Apache, Nginx, Cloudflare or Next.js, flagging loops.
- Free
- No sign-up
- Runs in your browser
When you rename a page, move to a new website or change platforms, every old address needs to send visitors — and Google — to the new one. Without redirects, old links from Google, WhatsApp shares and other sites land on a "page not found" error and the ranking you built is lost. Paste your old and new addresses and get ready-to-use rules for Apache, Nginx, Cloudflare and Next.js, with chains, loops and duplicates flagged before they go live.
Your workspace
Type of move
Use this for renamed pages and site moves. Google moves the old page's ranking to the new address.
Your server
Fill in the details above, then press the button to see your result.
Guide
How to use it
- 1List each old address and its new address on one line, separated by a space, tab, comma or ->.
- 2Choose 301 for a permanent move (almost always right) or 302 for a short-term one.
- 3Fix any warnings — especially loops, which make a page impossible to open, and chains, which slow every visit.
- 4Pick your server type, copy the rules, and paste them where the note under the box says.
- 5Open a few old addresses in your browser to confirm they land on the right new page.
What the results mean
- 301 redirect
- A permanent move. Browsers and Google update to the new address, and most of the old page's ranking passes across to it. Use this for renamed pages and site moves.
- 302 redirect
- A temporary move. Google keeps the old address in its results because you have said it is coming back. Use it only for things like a short sale page or maintenance.
- Redirect chain
- When A sends to B and B sends to C. Each hop slows the page down and Google may stop following after a few. Point A straight to C instead.
- Redirect loop
- When the redirects lead back to where they started, such as A to B and B to A. Browsers give up with a "too many redirects" error, so the page cannot be opened at all.
Common questions
How long should I keep redirects in place?
At least a year, and ideally for good. Old links on other websites, in WhatsApp chats and in people's bookmarks keep being used for years, and removing the redirect turns every one of them into an error page.
Should I redirect every old page to my home page?
No. Send each old page to the new page that best matches it. Google treats a mass redirect to the home page like a missing page, so the old ranking is lost anyway, and visitors are confused.
Why does the tool warn about addresses with a ? in them?
Most servers match redirects on the page path only and ignore everything after the question mark. A rule for /shop?id=4 will usually either not fire or catch every /shop address. Those need special rules — ask your developer.
Which output should I use?
Use Apache if your hosting uses cPanel or you have a .htaccess file. Use Nginx if your developer manages the server, Cloudflare if your site is on Cloudflare Pages, and Next.js if your site is built with Next.js.
Guides on this topic
- .htaccess Guide: HTTPS, www, Redirects and CachingWhat the .htaccess file does on cPanel hosting, with safe rules to force HTTPS, pick www, add 301 redirects and caching, and how to fix a 500 error.
- Website Migration SEO Checklist: Keep Your Google RankingsMove to a new domain, platform or URL structure without losing Google rankings: URL mapping, 301 redirects, bulk checks, Change of address and sitemaps.
- SEO-Friendly URLs: How to Write a Clean Web AddressEight rules for short, readable web addresses, whether to use Hindi in a URL, and how to change an old address without losing your Google rankings.
- Canonical Tags and Duplicate Content, Explained SimplyWhy websites copy their own pages by accident, what a canonical tag does, when to use a redirect instead, and how to check your site for duplicates.