301 vs. 302 Redirects: When to Use Each One

You changed a page's URL, but the old address still appears in Google, still earns links from other sites, and still attracts visitors. A redirect is how you move that traffic to the new address. If you choose the wrong redirect type, rankings won't transfer to the new page, crawl budget gets wasted, and users land on the wrong page.

In this guide, we walk you step by step through the difference between 301 and 302 redirects, which one to choose in each scenario, how to set up and test them, and the mistakes we see most often in the field.

What Are 301 and 302 Redirects?

When a user or Googlebot requests a URL, the server can respond with "the content you're looking for is at a different address" instead of serving the page directly. The HTTP status code behind that response defines the nature of the redirect.

• 301 (Moved Permanently): The page has moved permanently. Search engines are told to forget the old address and index the new one.
• 302 (Found): The page is temporarily at another address. The original address will return, so it makes sense to keep it in the index.

Redirects happen on the server side. JavaScript redirects and meta refresh tags work differently, and search engines may process them later or less reliably. From an SEO perspective, we recommend using server-side redirects wherever possible.

The Difference Between 301 and 302 Redirects

In practice, the biggest difference is the signal of intent you send to Google. According to Google's published documentation, a 301 is a strong signal that the target URL should be the canonical (preferred) version. A 302 sends a weaker signal in this regard and usually causes the source URL to remain in the index. According to Google's statements, the redirect type alone does not cause a decisive loss in link equity transfer. The real risk is that the wrong type leaves the wrong URL in the index.

Where Do 307 and 308 Fit In?

307 and 308 are the modern counterparts of 302 and 301 that preserve the request method (for example, POST). 308 is permanent and 307 is temporary. For ordinary page redirects, 301 and 302 are enough. You'll mostly encounter 307 and 308 with APIs, form submissions, and in-browser HTTPS redirects triggered by HSTS. Google interprets these codes as redirects too, but you shouldn't expect a separate SEO advantage on content sites.

When to Use a 301 Redirect

If the old address is never coming back, the answer is a 301. Here's a realistic example: you changed /blog/seo-nedir to /rehber/seo-nedir. To carry over the backlinks the old address earned and its history in the index, you need a permanent redirect.

Use a 301 in the following cases:

• HTTP to HTTPS migration: All HTTP addresses should be redirected to their HTTPS equivalents.
• Domain name change: After a rebrand or merger, the old domain is redirected one-to-one to the equivalent pages on the new domain. For a detailed process, take a look at our site migration SEO service.
• Consolidating www and non-www versions: Only one version of the site should be accessible.
• URL structure changes: When the category path, file extension (.html, .php), or letter-case standard changes.
• Content consolidation: When you merge two posts that compete with each other (cannibalization) into one strong page, redirect the weaker one to the stronger one.
• Permanently removed product/service: If there is a replacement or a very close alternative, redirect to that page.

The rule is simple: the new page must be a true equivalent of the old one. If topic and user intent don't match, a 301 won't pass value. Google may treat it as a soft 404.

When to Use a 302 Redirect

A 302 is the right way to say "this situation is temporary." It's chosen when you want to preserve the old URL's ranking and index entry.

• A/B testing: While you send part of the traffic to a test version, the original page should stay in the index.
• Short-term campaign: For example, if you redirect to a seasonal discount page for a few weeks.
• Maintenance and temporary announcements: When a page will be unavailable for a while and will come back.
• Temporary stock status: If a product will be back on sale shortly, you can consider redirecting to a temporary alternative instead of deleting the product page. In most cases, it's better to keep the page live and show stock information.
• User-based redirects: Automatic redirects based on language, location, or session state. On multilingual sites, plan these together with canonical and hreflang management.

The Problem of 302s Left in Place for Too Long

Google may eventually interpret a 302 that has stayed in place for a very long time as if it were permanent. However, we can't guarantee when or under what conditions this behavior will occur. If the move is permanent, don't leave it to chance; use a 301. Also plan temporary redirects with an end date and add it to your calendar.

How to Set Up and Test Redirects

The setup method depends on your infrastructure. On Apache servers you'll usually use the .htaccess file, on Nginx the server configuration, and on CMSs like WordPress a redirect plugin or panel. The examples below are only meant to illustrate the logic, so try them in a test environment before going live.

Apache: Redirect 301 /eski-sayfa https://www.ornek.com/yeni-sayfa

Nginx: return 301 https://www.ornek.com/yeni-sayfa;

For a temporary redirect, you write the 302 code using the same logic. A sound implementation process looks like this:

1. Prepare a mapping table: Create a list with columns for the old URL, the new URL, and the redirect type.
2. Collect the old URLs: Add all addresses from your sitemap, crawler output, Search Console, and backlink data to the list.
3. Map them one-to-one: Redirect each old page to the closest new page by topic; don't send them all to the homepage in bulk.
4. Apply the rules: Try them in a test environment first, then publish.
5. Verify the status code: Check the response code and the Location header using browser developer tools, a crawling tool, or curl -I on the command line.
6. Update internal links: Menus, in-content links, and the sitemap should point directly to the new URL.
7. Monitor: Track the coverage and crawl reports in Search Console for a few weeks.

If you want a quick look at your site's current redirect status, you can get an overall technical picture with our free SEO site analysis tool.

The Most Common Redirect Mistakes

Most of the problems we see in the field stem not from the tool or the code but from a lack of planning. The most common ones are:

• Redirect chains: If page A goes to B and B goes to C, each step adds delay and crawl cost. A should redirect directly to C. We covered the crawl-side impact in our article on crawl budget optimization.
• Redirect loops: When A goes to B and B goes back to A, the page never loads and the browser throws an error.
• Redirecting everything to the homepage: Users can't find the content they expected, and Google may treat it as a soft 404.
• Using a 302 for a permanent move: The old URL stays in the index, and the new page may not enter the rankings as quickly as you'd like.
• Using a 301 for a temporary action: Reverting becomes problematic once the campaign ends, because browsers and search engines can cache a 301 aggressively.
• Leaving redirected URLs in the sitemap: The sitemap should contain only canonical addresses that return 200.
• Removing redirects too early: The general recommendation is to keep permanent redirects for at least a year, or indefinitely if possible. The old address may still be earning links.
• Conflicting with the canonical: While a redirect points to one address, the canonical tag must not point to another.

Pre-Launch Checklist

• Is the old-to-new URL mapping consistent in terms of topic?
• Was 301 chosen for permanent moves and 302 for temporary situations?
• Are there no chains or loops, and does the final target return 200?
• Do internal links, canonical tags, and the sitemap point to the new URL?
• Have old URLs with important backlinks been included in the list?
• Are you monitoring for increases in errors in Search Console and server logs after launch?

If you're planning a major restructuring, we recommend putting these checks among the first steps of your technical SEO optimization process.

Frequently Asked Questions

Will a 301 redirect lower my rankings?

According to Google's statements, a correctly implemented 301 redirect does not prevent link equity from being passed. However, if the new page differs greatly from the old one in content or intent, rankings may fluctuate. It's also normal to see temporary fluctuations for a while after a migration.

Does a 302 redirect pass link equity?

Google ties link equity transfer more to whether the pages are equivalents of each other than to the redirect type. The real difference is which URL is kept in the index. With a 302, the old URL mostly stays in the index. That's why a 301 is the safer choice for a permanent move.

How long should I keep redirects in place?

We recommend keeping permanent redirects for at least a year, or indefinitely if possible. If external links keep pointing to the old URL or users keep arriving from bookmarks, removing the redirect means losing traffic and value. Remove temporary 302s once their purpose has been served.

Should I always redirect a deleted page?

No. If there is a replacement page that is close in topic, a 301 is appropriate. If there is no true equivalent, returning a 404 or 410 is more correct, because redirecting to an unrelated page can cause a soft 404 issue. Make the decision based on the page's traffic and backlink profile.

How much of a problem is a redirect chain?

Each additional step slows down page loading and lengthens the work for crawlers. Google follows a limited number of hops, but simplifying chains is always safer. Crawl your redirect map regularly to make sure every old URL goes directly to its final destination.

Conclusion: Plan the Right Redirect Type

Choosing between 301 and 302 redirects is more than a line of code. It tells Google and users whether a page has moved permanently or temporarily. Use a 301 for permanent changes and a 302 for short-term situations, redirect every old URL one-to-one to the closest page by topic, and monitor the results after launch.

If you're dealing with a risky process such as a site migration, a URL structure change, or a complex redirect map, we can plan it together. First, see where you stand with a free SEO site analysis, then share your needs with us through our contact page.