301 Redirect Generator
Generate server redirect rules from URL mappings — supports Apache, Nginx, Cloudflare, and WordPress
Output Settings
Generated Rules
When to Use 301 vs 302 Redirects
301 — Permanent Redirect
Use when the page has permanently moved. Search engines transfer ~90-99% of link equity to the new URL. Best for site migrations, URL structure changes, and merging duplicate content.
302 — Temporary Redirect
Use when the redirect is temporary (A/B testing, seasonal pages, maintenance). Link equity is NOT passed. The original URL stays indexed in search engines.
Common Redirect Mistakes
- ✗ Using 302 when you mean 301 — the most common mistake that wastes link equity
- ✗ Creating redirect chains (A → B → C) — each hop loses link equity, aim for direct A → C
- ✗ Redirect loops (A → B → A) — causes infinite loops and crawl errors
- ✗ Redirecting all old pages to the homepage — use specific page-to-page redirects instead
- ✗ Not updating internal links after redirects — fix internal links to point directly to new URLs
Frequently Asked Questions
How long should I keep 301 redirects active?
Google recommends keeping 301 redirects in place for at least 1 year. After that, most link equity has been transferred. However, keeping them indefinitely doesn't hurt and catches any remaining old links.
Should I use redirects or canonical tags?
Use 301 redirects when users should no longer access the old URL. Use canonical tags when both URLs need to remain accessible (e.g., print versions, filtered pages). Redirects are a stronger signal to search engines.
Do redirects affect page speed?
Each redirect adds a round-trip to the server (typically 50-100ms). Avoid redirect chains — Google follows up to 10 redirects but may stop indexing after 5. Use direct redirects whenever possible.