What is a URL Redirect? 301 vs 302 Redirect Guide
TL;DR: A redirect automatically sends users and search engines from one URL to another. The 301 redirect (permanent) passes nearly all SEO value to the new URL and is used for permanent moves. The 302/307 redirect (temporary) preserves the original URL’s SEO value and is used for temporary changes. Proper redirects prevent 404 errors, maintain link equity, and ensure users find the content they’re looking for.
What is a URL Redirect?
A URL redirect (or URL forwarding) is a technique that sends both users and search engines from one web address (URL) to another. When someone attempts to visit a specific page, the server automatically routes them to a different destination.
Redirects are essential for website management, helping maintain user experience and SEO during site changes. Without proper redirects, users encounter 404 errors, and search engines lose the ability to find and index your content.
Why Redirects Matter
1. Preserve SEO Value
When you move or delete a page, any backlinks pointing to that URL would normally be lost. Redirects pass “link equity” (ranking power) to the new destination, preserving your search rankings. Use an SEO audit tool to identify broken links and redirect opportunities across your site.
2. Maintain User Experience
Visitors following old bookmarks, external links, or search results are seamlessly directed to the correct content rather than hitting dead ends.
3. Consolidate Duplicate Content
Multiple URLs showing the same content (common with www vs. non-www, HTTP vs. HTTPS, or trailing slashes) can be consolidated via redirects to strengthen SEO signals.
4. Enable Site Restructuring
Website redesigns, platform migrations, and content reorganizations become possible without losing existing traffic or search visibility.
5. Fix Broken Links
Redirects can repair internal and external broken links pointing to moved or renamed pages.
Types of Redirects
301 Redirect (Permanent)
Status Code: 301 Moved Permanently
What it does: Tells browsers and search engines that the original URL has permanently moved to a new location. The old URL should be removed from indexes and replaced with the new one.
SEO Impact: Passes approximately 90-99% of link equity (ranking power) to the destination URL. This is the recommended redirect for permanent moves.
When to use:
- Permanently moving a page to a new URL
- Merging duplicate pages
- Switching from HTTP to HTTPS
- Changing domain names
- Restructuring site architecture
- Consolidating www and non-www versions
Implementation Example (Apache .htaccess):
Redirect 301 /old-page.html https://example.com/new-page.html
302 Redirect (Temporary)
Status Code: 302 Found (historically “Moved Temporarily”)
What it does: Indicates the resource is temporarily located at a different URL. The original URL remains valid and should continue to be indexed.
SEO Impact: Does not pass link equity to the destination. Search engines continue to index and rank the original URL.
When to use:
- A/B testing different page versions
- Temporary maintenance pages
- Geographic or device-based redirects
- Short-term promotional landing pages
- Out-of-stock product redirects
Warning: 302 redirects are often misused when 301s should be applied, causing SEO issues when permanent moves are treated as temporary.
307 Redirect (Temporary - HTTP/1.1)
Status Code: 307 Temporary Redirect
What it does: The HTTP/1.1 successor to 302, explicitly guaranteeing that the request method and body will not change during the redirect.
SEO Impact: Same as 302—no link equity passed.
When to use: Modern temporary redirects where you want to ensure POST data is preserved.
308 Redirect (Permanent - HTTP/1.1)
Status Code: 308 Permanent Redirect
What it does: The permanent equivalent of 307, guaranteeing the request method doesn’t change.
SEO Impact: Same as 301—passes link equity.
When to use: Permanent redirects in modern web applications where method preservation matters.
Meta Refresh
What it does: An HTML-based redirect using a meta tag:
<meta http-equiv="refresh" content="0; url=https://example.com/new-page">
SEO Impact: Generally treated as a 302 (temporary). Slower than server-side redirects because the page must load first.
When to use: Only when server-side redirects aren’t possible. Not recommended for SEO-critical situations.
JavaScript Redirects
What it does: Uses JavaScript to change the window location:
window.location.href = "https://example.com/new-page";
SEO Impact: Search engines may or may not execute and follow JavaScript redirects. Unreliable for SEO.
When to use: Client-side navigation in web applications, not for permanent URL changes.
Redirect Comparison Table
| Redirect Type | Permanent? | Passes Link Equity | SEO Recommendation |
|---|---|---|---|
| 301 | Yes | Yes (90-99%) | Standard for permanent moves |
| 302 | No | No | Temporary situations only |
| 307 | No | No | Modern temporary alternative |
| 308 | Yes | Yes | Modern permanent alternative |
| Meta Refresh | Debatable | Minimal | Avoid for SEO |
| JavaScript | No | Unreliable | Avoid for critical redirects |
When to Use Redirects
Common Use Cases
| Scenario | Recommended Redirect | Notes |
|---|---|---|
| HTTP to HTTPS | 301 | Site-wide security upgrade |
| WWW to Non-WWW | 301 | Consolidate domain versions |
| URL Structure Change | 301 | Site redesign or reorganization |
| Content Consolidation | 301 | Merge similar pages |
| Out of Stock Products | 302 | Temporary redirect to category |
| A/B Testing | 302 | Temporary variation testing |
| Geographic Targeting | 302 | Location-based content |
| Domain Migration | 301 | Complete site move |
How to Implement Redirects
Apache (.htaccess)
Single redirect:
Redirect 301 /old-page https://example.com/new-page
Redirect entire directories:
RedirectMatch 301 ^/blog/(.*)$ https://example.com/news/$1
Force HTTPS:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Nginx
server {
listen 80;
server_name example.com;
return 301 https://$server_name$request_uri;
}
location /old-page {
return 301 https://example.com/new-page;
}
WordPress
- Use plugins like Redirection or Yoast SEO Premium
- Simple interface for creating and managing 301 redirects
- Automatic 404 monitoring and redirect suggestions
Cloudflare
- Use Page Rules for simple redirects
- Bulk redirect functionality available
- Good for domain-level redirects
Programming Languages
PHP:
header("HTTP/1.1 301 Moved Permanently");
header("Location: https://example.com/new-page");
exit();
JavaScript (Node.js/Express):
res.redirect(301, '/new-page');
Redirect Best Practices
1. Use 301 for Permanent Changes
When content moves permanently, always use 301 redirects. This consolidates ranking signals and prevents search engines from treating the change as temporary.
2. Avoid Redirect Chains
Chains occur when URL A redirects to B, which redirects to C. This dilutes link equity and slows page loading.
Bad: Page A → 301 → Page B → 301 → Page C Good: Page A → 301 → Page C
Limit chains to maximum 2 hops; ideally update old redirects to point directly to final destinations.
3. Avoid Redirect Loops
Loops occur when pages redirect to each other infinitely:
- Page A → Page B → Page A
This breaks the site completely. Always test redirects thoroughly.
4. Redirect to Relevant Content
When possible, redirect to the most relevant equivalent page rather than the homepage. Sending all redirects to the homepage frustrates users and wastes link equity.
Good: /old-product → 301 → /similar-product
Bad: /old-product → 301 → /homepage
5. Update Internal Links
While redirects handle external links and bookmarks, update your internal links to point directly to new URLs. This reduces server load and improves page speed.
6. Monitor 404 Errors
Use Google Search Console to identify 404 errors and create appropriate redirects. Regular audits prevent link equity loss.
Common Redirect Mistakes
1. Using 302 Instead of 301
Accidentally using temporary redirects for permanent moves prevents link equity transfer. Audit your redirects periodically to catch these errors.
2. Redirecting All 404s to Homepage
This creates poor user experience and soft 404s. Either redirect to relevant content or allow genuine 404s with helpful error pages.
3. Forgetting Mobile-Desktop Redirects
If you maintain separate mobile sites, ensure redirects work properly across all device types.
4. Ignoring Query Parameters
Redirects should preserve or properly handle query strings based on your analytics needs.
5. Too Many Redirects
Excessive redirects slow down your site and create maintenance headaches. Simplify your URL structure when possible.
Testing and Monitoring Redirects
Tools for Checking Redirects
| Tool | Purpose |
|---|---|
| Redirect Checker (httpstatus.io) | Test redirect chains and status codes |
| Screaming Frog | Bulk redirect checking |
| Google Search Console | Monitor crawl errors |
| Browser DevTools | Check response headers |
What to Test
- Status code returned (should be 301/302 as intended)
- Final destination URL
- Number of hops in redirect chains
- HTTPS enforcement
- WWW vs. non-WWW consistency
- Mobile redirect behavior
Frequently Asked Questions
Do redirects hurt SEO?
Properly implemented 301 redirects don’t hurt SEO—they preserve it. However, redirect chains, loops, or using 302s for permanent moves can dilute link equity and cause ranking drops.
How long should I keep 301 redirects in place?
Ideally, keep them forever. Even after search engines update their indexes, external links, bookmarks, and referral traffic may continue to arrive at old URLs. Removing redirects causes 404 errors and lost traffic.
Can I redirect without losing rankings?
301 redirects preserve 90-99% of link equity, so ranking loss should be minimal and temporary. However, major site restructuring may cause some fluctuation as search engines reprocess the site.
What’s the difference between a redirect and a canonical tag?
- Redirect: Sends users and bots to a different URL entirely
- Canonical Tag: Indicates the preferred version of a page while keeping multiple versions accessible
Use redirects when you want to eliminate the old URL; use canonicals when both URLs should remain accessible but you want search engines to consolidate ranking signals.
How many redirects are too many?
Ideally, zero hops between a requested URL and final destination. One redirect is acceptable. Two redirects create problems. Three or more indicate serious structural issues that need fixing.
Conclusion
Redirects are essential tools for website management and SEO. Understanding when to use 301 vs. 302 redirects—and implementing them correctly—protects your search rankings, maintains user experience, and enables necessary site changes.
The key principles are simple: use 301s for permanent changes, 302s (or 307s) for temporary situations, avoid chains and loops, and always redirect to relevant content rather than generic homepages. Regular audits ensure your redirect strategy continues supporting both users and search engines effectively.
Related Resources: