If you manage a website, you’ve almost certainly run into that moment. You’re moving a page, or maybe you’re cleaning up old URLs, and someone says “just use a redirect.” But then you get into the weeds. Is it a 301 or a 302? The difference is subtle in name but massive in how Google treats your traffic and your rankings. Get it wrong, and you could tank months of SEO work. This whole thing matters more than most people think.
The short version: 301 means “moved permanently.” 302 means “moved temporarily.” But in practice, the implementation and the way search engines interpret these codes has shifted over the years, which creates a lot of confusion. You need to know exactly when to use each one, and more importantly, when not to.
This guide is going to walk you through the technical details, the SEO impact, and the decision-making process, all while keeping things grounded in real-world scenarios. By the end, you’ll be able to look at any redirect situation and know immediately which status code to fire back. And if you’re tired of manually cranking out content about technical SEO topics like this, you might want to check out a tool that automates the whole publishing workflow for you — we’ll get to that.
Understanding the Core Difference: 301 vs 302
At its most basic level, HTTP status codes tell the browser (and search engines) what happened to a request. A 301 redirect is a permanent signal. It says “this resource has moved, and it’s not coming back. Update your records.” A 302 redirect, on the other hand, is a temporary detour. It says “the resource is temporarily at this other address, but come back to the original URL later.”
In the early days of SEO, this distinction was everything. A 301 passed most of the link equity from the old URL to the new one. A 302 did not. Google treated the two codes very differently. That’s still mostly true today, but the lines have blurred a little. Google has gotten smarter about inferring intent based on behaviour. If a 302 stays up for six months, Google might start treating it as a de facto permanent redirect. But that’s a gamble you don’t want to take.
What a 301 Redirect Actually Does
When you set up a 301 redirect, you’re telling the entire internet that the old page is dead and gone. Search engines transfer the ranking power, the backlink profile, and even the historical authority to the new URL. It’s like moving your house and having your mail forwarded indefinitely.
- Link equity transfer: Most of the PageRank flows through to the new URL.
- Index update: Google will eventually replace the old URL in its index with the new one.
- User experience: Visitors are automatically sent to the correct page.
You use a 301 when you’re restructuring your site, merging domains, or permanently deprecating a piece of content. For example, if you change your blog’s URL structure from /p/123 to /blog/post-title, you’d use a 301.
What a 302 Redirect Actually Does
A 302 redirect is designed for short-term moves. Think about a seasonal page. You have a summer sale landing page that you want to redirect to the main site after the promotion ends. Or maybe you’re A/B testing a new landing page and don’t want to commit permanently.
- No link equity transfer: Historically, 302s passed little to no ranking power. This is still generally true.
- Index stays on original URL: Google keeps the original page in its index and treats the redirect as a temporary detour.
- User experience: Visitors still reach the content, but search engines don’t update their primary records.
The risk with 302s is that if you use them incorrectly, you can accidentally split your ranking signals or confuse Google about which page is canonical. It’s not a forgiving code to misuse.
When to Use 301 Redirects: The Permanent Moves
Most of your redirects should be 301s. If you’re serious about SEO, that’s the default. Here are the common scenarios where a 301 is the only correct choice.
Website Migration or Domain Change
If you’re moving from oldsite.com to newsite.com, every single URL needs a 301. This is the most critical use case. Losing traffic during a domain migration is common, but using 301s is the only way to preserve authority.
URL Restructuring
Maybe your CMS changed, or you decided to flatten your URL hierarchy. For example, you might change from /category/subcategory/product to /product. Each old URL needs a 301 to its new counterpart.
Page Deletion or Deprecation
If you delete a page that has backlinks and traffic, you don’t just want to return a 404. That’s a dead end for users and a waste of link equity. Instead, redirect the old URL (301) to the most relevant related page. This is a staple of good link maintenance.
Merging Two Pages
If you have two blog posts about the same topic and you combine them into one comprehensive guide, use a 301 from the old URLs to the new merged page. This consolidates the strength.
When to Use 302 Redirects: The Temporary Moves
302 redirects have a narrower set of legitimate uses. You should only employ them when you genuinely plan to revert to the original URL within a reasonable timeframe.
A/B Testing or Landing Page Experiments
If you’re running a multivariate test on a landing page and you want to direct traffic to a variant, a 302 is appropriate. The original URL should remain canonical because you’ll eventually choose a winner and go back.
Temporary Site Maintenance
Your site goes down for an hour or you’re updating a crucial page. You can use a 302 to shunt traffic to a holding page or a cached version. But don’t leave it up for weeks.
Seasonal Promotions
Black Friday sales, holiday specials, event registration. After the event ends, the redirect should be removed and the original URL should be the live page again. A 302 makes sense here.
Unfinished or Staged Pages
If you’re building a new page but it’s not ready for prime time, a 302 to a relevant existing page can buy you time. But again, it needs to be temporary.
The SEO Implications: Link Equity, Indexing, and User Signals
This is where things get layered. The search engines don’t just look at the status code in isolation. They weigh multiple signals to decide how to handle the redirect.
Link Equity Transfer (PageRank)
For a long time, the common knowledge was simple: 301 passes 90-99% of link equity, 302 passes none. That’s mostly still accurate, but newer research suggests Google is better at understanding intent. In some tests, a long-standing 302 started passing equity. But relying on that is like betting on a horse with a sore leg. It might work, but why risk it? Always default to 301 for equity preservation.
Indexing Behaviour
With a 301, Google will eventually de-index the old URL and index the new one in its place. With a 302, Google keeps the old URL indexed. This can be a problem if you accidentally leave a 302 up for months. Google might start ignoring the 302 and treat it as permanent, then you’ve got both URLs indexed, potentially creating a duplicate content issue.
User Experience and Bounce Rate
From a user perspective, a redirect is a redirect. They don’t see the status code. But the speed of the redirect matters. A chain of redirects (301 and 302 mixed) slows down load time and increases bounce rate. That’s a signal to Google that something is broken. Keep your redirects direct and minimised.
Real-World Examples: Getting It Wrong and Right
Let’s look at a couple of scenarios to make this concrete.
The Botched Domain Change
You migrate your blog from blog.example.com to example.com/blog. You’re in a hurry, so you set up 302 redirects for every old URL. A month later, your traffic drops by 40% because Google is still showing the old URLs in search results and not passing any authority to the new ones. Fix: switch every 302 to a 301 and resubmit your sitemap.
The Seasonal Snippet
Your ecommerce site runs a “Christmas Collection” page every year. You redirect (302) the Christmas page to a generic gift guide after the holidays. Next November, you remove the redirect and bring the Christmas page back. That’s spot-on usage.
The Accidental Permanent
You’re redesigning your product categories. You use 302s because you think you might change the structure again soon. Six months pass, and you never change back. Now you have indexed URLs with no authority, and the original URLs are orphaned. This is a common mess that requires a full audit to untangle.
How to Implement Redirects Correctly in Your CMS
Implementation varies by platform, but the principles are the same.
WordPress (with a plugin like Redirection or Yoast)
In Yoast SEO, you can set up 301 redirects from the advanced settings on individual pages. For bulk redirects, use the built-in tools or a dedicated plugin.
Apache (.htaccess)
You add lines like:
Redirect 301 /old-page https://yoursite.com/new-page
Nginx (server block)
You add a rewrite rule:
rewrite ^/old-page$ /new-page permanent;
Where permanent signals a 301, and redirect signals a 302.
Cloudflare or CDN Bypass
Many CDNs also offer redirect rules. Just be careful with the status code selection — they often default to 302.
Monitoring and Auditing Your Redirects
You can’t just set it and forget it. Redirects need to be checked regularly.
Use a Crawler
Tools like Screaming Frog or Sitebulb will identify all redirects on your site. Look for chains (URL A redirects to B which redirects to C) and loops (A redirects to B which redirects back to A). Both are bad for SEO.
Check Google Search Console
Look for “URL errors” in the index report. If you see a lot of 302 errors on pages that should be permanent, fix them.
Log File Analysis
If you have access to server logs, look at the status codes being returned. A high percentage of 302s might indicate a structural issue.
Common Mistakes and How to Avoid Them
Mistake #1: Using 302s for permanent moves. This is the most common error. Always double-check your intent.
Mistake #2: Creating redirect chains. If you redirect URL A to B, and then months later redirect B to C, you’ve created a chain. The user and search engine have to follow multiple hops. Consolidate: redirect A directly to C.
Mistake #3: Ignoring internal links. If you have internal links pointing to the old URL, update them to point to the new URL. Relying solely on redirects for internal links is lazy and adds latency.
Mistake #4: Not using relative URLs correctly. When coding redirects, always use absolute URLs (starting with https://yoursite.com/) to avoid confusion.
The Role of Content in Redirect Strategies
Here’s where we loop back to why this matters for publishing. If you’re running a blog or a content site, redirects are part of your content lifecycle. When you update a post with fresh information, you might want to redirect the old version to the new one. Or if you merge several thin articles into one authoritative guide, you need a redirect plan.
This is where having the right tools makes a difference. Manually writing all that redirect logic, checking the status codes, and updating internal links is tedious. It’s the kind of work that pulls you away from strategy. That’s exactly why people who publish for a living use a system that handles the repetitive parts. For example, SEOLetters takes you from a keyword to a published article without the copy-paste grind. You could literally write a guide on redirects and have it auto-scheduled to publish, complete with internal linking and schema. The tool doesn’t just write — it manages the whole workflow, which is handy when you’re trying to keep your site content updated around technical topics like redirects.
Advanced Considerations: Canonical Tags and Redirect Combination
Sometimes you see people using a 302 plus a rel=canonical tag. That’s a confused signal. A 302 already tells search engines to look at the temporary URL, and a canonical tells them to prefer the original. In practice, Google usually follows the redirect URL for ranking signals. But why create ambiguity? Stick to one method.
Also, never stack multiple 301s in a chain. It slows down page load and dilute link equity. For instance, if you have old-page → intermediate-page → final-page, change it to old-page → final-page directly.
Summary: Quick Decision Framework
| Scenario | Recommended Code | Why |
|---|---|---|
| Domain migration | 301 | Transfer all equity permanently |
| URL restructuring | 301 | Permanent change of address |
| Deleted page with links | 301 | Preserve authority |
| A/B test variant | 302 | Temporary detour for testing |
| Seasonal promotion | 302 | Will revert after event |
| Temporary site break | 302 | Short-term fix only |
| Unfinished new page | 302 | Buy time to finish |
Final Thought
Redirects are one of those technical SEO areas where small mistakes compound. A single 302 left in place for too long can cost you thousands of visitors. A well-executed 301 can save years of accumulated authority. If you’re unsure, test the redirect with a browser extension that shows status codes — or use a crawler to audit the whole thing. And if writing thorough, technically accurate content like this takes time away from your actual business, consider automating the content creation part with something that does the heavy lifting. SEOLetters is built exactly for that use case. It turns a keyword into a published article with headings, internal links, and even schema — all on a schedule while you focus on strategy.
Frequently Asked Questions
What happens if I use a 302 instead of a 301 on a URL migration?
Search engines will generally not transfer link equity to the new URL, and they’ll keep the old URL in their index. This means you lose ranking power and may have both URLs competing. In most cases, it’s better to use a 301 for permanent moves.
Can a 302 redirect become permanent over time?
Google may treat a persistent 302 as a permanent redirect if it’s been in place for months. But this isn’t guaranteed and can lead to unpredictable indexing behaviour. It’s safer to change it to a 301 manually.
Do 301 redirects lose PageRank?
Early on, it was believed that 301s lost some link equity. Google has stated that 301 redirects pass the same amount of equity as a direct link, provided the redirect is valid and not part of a chain. However, chain redirects can dilute the value.
Should I use 301 or 302 for redirecting users to a mobile version?
For mobile redirects, use a 302 if the same content is served on different URLs (like m. example.com). Google recommends using a rel=canonical and a proper Vary: User-Agent header instead of relying solely on redirects.
How long should I keep a 302 redirect in place?
Ideally, no longer than a few weeks. If the redirect needs to stay for an extended period, you should evaluate whether it’s actually permanent and switch to a 301.
Leave a Reply