keepcalculator

06 Numbers and Powers

301 vs 302 Redirects: Which for SEO?

Card No. 06·79938 · Updated · Standard formula, shown below

For SEO, use a 301 redirect when a page has moved permanently, and a 302 redirect only when the move is temporary. The 301 passes nearly all link equity and tells search engines to replace the old URL with the new one; the 302 tells them to keep the old URL as the canonical source, which can split ranking signals and delay indexing. Choosing wrong can cost you rankings, so here is the full breakdown.

What a 301 Redirect Does

A 301 status code means “Moved Permanently.” When a browser or search engine crawler hits a 301, it follows the redirect to the new URL and—critically—treats the old URL as gone. Search engines transfer most of the ranking signals (backlinks, authority, page rank) from the old URL to the new one. Google has stated that 301s pass “most” link equity, not 100% in every case, but in practice it is the closest thing to a full transfer. Use a 301 when you have permanently changed a URL: a site migration, a page rename, merging two pages, or switching from HTTP to HTTPS.

What a 302 Redirect Does

A 302 means “Found” (historically “Moved Temporarily”). It tells the crawler that the current URL is still the canonical one, but the content is temporarily available elsewhere. Search engines will index the original URL, not the redirect target, and will keep looking at the original. That means any backlinks pointing to the original continue to count for the original, not the temporary destination. Use a 302 for A/B testing, seasonal promotions, temporary maintenance pages, or when you plan to revert the URL change within weeks or months.

How to Choose: 301 vs 302

The decision comes down to one question: Will the old URL come back? If the answer is no, use 301. If yes, use 302. Here are concrete examples:

  • Site migration (changing domain or CMS): 301 every old URL to its new equivalent.
  • Merging two similar pages (e.g., two blog posts about the same topic): 301 the weaker page to the stronger one.
  • Changing a product URL after a rename: 301.
  • Running a holiday landing page that will disappear in January: 302.
  • Testing a new checkout flow for a week: 302.
  • Redirecting mobile users to an app (though this is often done via JavaScript or deep links): 302 is common.

A common mistake is using 302 for permanent changes because it “feels safer.” It is not. If you leave a 302 in place for months, search engines may eventually treat it as permanent (Google has said they may “interpret” a long-standing 302 as permanent), but the signal transfer is still less reliable than a 301. Conversely, using a 301 for a temporary redirect can cause the original page to drop out of the index, which is bad if you plan to bring it back.

Common Problems and Misconceptions

“301s lose link equity.” They do not lose much. Google’s John Mueller has said that 301s pass “most” PageRank, and in practice the loss is negligible for most sites. The bigger risk is a broken redirect chain (A→B→C), which can dilute equity. Always redirect directly to the final URL.

“302s never pass equity.” That is false. Google has said that 302s can pass signals if they are treated as permanent, but it is inconsistent. Do not rely on it.

“You can use 302 for everything and it will sort itself out.” No. If you permanently move a page and use a 302, Google will keep the old URL in the index, which means the new URL may never rank. You will also see duplicate content issues if both URLs are crawlable.

Redirect chains are a frequent problem. If you have a 301 from /old to /new, and then /new itself 301s to /newer, search engines will follow the chain but may not transfer full equity. Keep chains to one hop.

Redirect loops (A→B→A) cause crawlers to give up and de-index both URLs. Always test your redirects after implementation.

How to Implement Redirects Correctly

Implementation depends on your server or CMS:

  • Apache (.htaccess): Use Redirect 301 /old-page https://example.com/new-page or Redirect 302 for temporary.
  • Nginx: Use return 301 https://example.com/new-page; in the server block.
  • WordPress: Use a plugin like Redirection, or add code to your theme’s functions.php (but a plugin is safer for non-developers).
  • JavaScript or meta refresh: These are not true redirects and should be avoided for SEO. They do not pass link equity reliably and are often ignored by crawlers.

After implementing, check that the old URL returns the correct status code using a tool like curl -I or a free redirect checker. Also verify that the new URL loads correctly and does not have a redirect loop.

Redirects and Site Migrations

Site migrations are the most common use of 301s. When you change domains, every old URL should 301 to its new counterpart. If you do not, you lose all accumulated authority. A common mistake is redirecting the entire old site to the homepage instead of mapping each old URL to a relevant new one. That is a “soft 404” in the eyes of users and search engines. Always create a full URL mapping spreadsheet before migrating.

For temporary changes, such as a site being down for maintenance, a 302 to a “be back soon” page is fine. If the downtime lasts more than a few days, consider a 503 Service Unavailable status instead, which tells crawlers to come back later without changing the index.

Frequently Asked Questions

Do 301 redirects lose PageRank? Google has said they pass most PageRank, so the loss is small. The bigger issue is redirect chains, which can dilute the signal. A single 301 is fine.

Can I use a 302 for a permanent redirect if I change my mind? You can, but it is not recommended. If you leave a 302 in place for a long time, Google may treat it as permanent, but the signal transfer is less predictable than a 301. Better to use 301 and change it later if needed.

What is the difference between 301 and 302 in Google Search Console? Search Console reports both as “Redirect,” but you can see the actual status code in the URL Inspection tool. If you see a 302 where you expected a 301, fix it.

Should I redirect HTTP to HTTPS with 301 or 302? Always 301. HTTPS is the permanent canonical version of your site. Using 302 would tell Google the HTTPS version is temporary, which can cause indexing issues.

How long does it take for Google to process a 301? It varies from days to weeks. Google must crawl the old URL, follow the redirect, and then crawl the new URL. You can speed it up by submitting the new URL in Search Console and using internal links to the new URL.

Can a 302 hurt my SEO if left for months? It can. Google may eventually treat it as permanent, but the signal transfer is less reliable than a 301. If you leave a 302 for months, you risk the new page not inheriting authority, and the old page may still be indexed. Set a reminder to change it to 301 if you decide the change is permanent.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →