301 Redirect Generator
Paste your old and new URLs, pick your server, and copy ready-to-use 301 rules. The tool flags duplicates, chains and loops before they reach production. For the full process, see the site migration SEO guide.
# 301 yönlendirmeleri — fatihemincakiroglu.com/araclar/yonlendirme-olusturucu
RewriteEngine On
RewriteRule ^eski-hakkimizda/?$ /hakkimda [R=301,L]
RewriteCond %{QUERY_STRING} ^id=12$
RewriteRule ^urun\.php/?$ /urunler/mavi-gomlek? [R=301,L]
RewriteRule ^blog/2019/seo-ipuclari/?$ /blog/seo-ipuclari [R=301,L]
RewriteRule ^iletisim/?$ https://yenisite.com/iletisim [R=301,L]Test the rules on a staging environment before going live, and check for conflicts with your existing rules.
How to use it
- Put one redirect per line: old URL first, new URL second. Copying two columns from Excel or Google Sheets works as-is.
- Choose your server or platform. If you are unsure, ask your developer or hosting provider.
- Review the warnings. Keep resolve chains on so every old URL points straight to its final destination.
- Copy or download the rules, test them on a staging environment, then check a sample of old URLs after go-live.
Frequently Asked Questions
301 or 302: which should I use?
Use 301 (permanent) when a page has moved for good, as in a migration. Use 302 only for genuinely temporary moves.
Why are redirect chains a problem?
Every extra hop slows users down and makes it harder for search engines to follow the move. Pointing each old URL directly to its final target is the safest approach.
Can I redirect URLs with query strings?
Yes. The tool adds a query condition for Apache, matches the full request for Nginx and uses a has condition for Vercel and Next.js. Always test these rules after deployment.
Is my URL list stored anywhere?
No. Everything runs in your browser; nothing is sent to a server.