technical seoredirects301 redirect

301 vs 302 vs 307 vs 308 Redirects: Which to Use for SEO

301 vs 302 redirect explained: which redirects are permanent, which keep the request method, how Google treats each, and how to avoid chains and loops.

||6 min read
301 vs 302 vs 307 vs 308 Redirects: Which to Use for SEO

A redirect sends people and crawlers from one URL to another. The status code you choose tells Google whether the move is permanent or temporary. Pick the wrong one and Google may keep indexing the old URL, or take longer to move its ranking signals to the new one.

This guide covers the four server redirects you will use, how Google treats each, and the mistakes that cause most redirect problems.

The short answer

CodeTypeKeeps request methodUse it when
301 Moved PermanentlyPermanentNot guaranteedA page or site has moved for good
308 Permanent RedirectPermanentYesA permanent move where POST data must survive (forms, APIs)
302 FoundTemporaryNot guaranteedThe old URL will come back (short promotion, test)
307 Temporary RedirectTemporaryYesA temporary move where POST data must survive

For most SEO work the choice is simple. Moved for good: 301. Coming back: 302. 307 and 308 matter when a form or API sends data. See the glossary entries for redirects and HTTP status codes for the wider family.

How Google treats each redirect

Google uses redirects as a signal for which URL to index, the canonical.

  • 301 and 308 are strong signals that the target should be canonical. Google moves its signals to the new URL and drops the old one from results over time.
  • 302 and 307 are weak signals. Google usually keeps the original URL in the index, because you told it the move is temporary.
  • PageRank is not lost through 3xx redirects. Google has said this publicly. Relevance still matters: a redirect to an unrelated page passes little value.
  • Long-lived 302s can eventually be treated as permanent. Don't rely on that. Use the code that matches your intent.

Googlebot follows up to 10 hops in a chain. Every hop still costs crawl time, so aim for one.

301 vs 308, and 302 vs 307

The older codes, 301 and 302, let browsers switch a POST request to GET on the redirect. That can drop form data. The newer codes, 308 and 307, forbid the switch.

  • Moving a normal page? Use 301. It works everywhere.
  • Moving a form endpoint or API for good? Use 308.
  • Temporarily sending a form somewhere else? Use 307.

Search engines treat 308 like 301 and 307 like 302. The method rule matters to browsers and apps, not rankings.

Meta refresh and JavaScript redirects

Some hosts don't let you set server headers, so people fall back to a meta refresh tag or a JavaScript window.location change.

  • The server returns 200, so crawlers must read or render the page to find the redirect.
  • Google can follow both. An instant meta refresh (0 seconds) is treated like a permanent redirect. Delayed refreshes are treated as temporary.
  • Crawlers that don't run JavaScript, including many AI crawlers, won't see a JavaScript redirect at all. See JavaScript rendering.

Use a server-side redirect whenever you can.

Chains, loops and HTTPS downgrades

A chain is a redirect that leads to another redirect: A to B to C. Chains build up during repeated migrations. Each hop slows users and crawlers. Fix them by pointing every old URL straight at the final page.

A loop sends A to B and B back to A. The page never loads. Loops often come from conflicting rules, such as HTTP to HTTPS on one layer and HTTPS to HTTP on another, or www and non-www fighting each other.

An HTTPS downgrade is a redirect from a secure URL to an insecure one. Browsers warn about it, and it breaks your HTTPS signals.

To check one URL, any header checker or your browser's network tab shows each hop. To find every chain, loop and downgrade across a site, crawl it. The Digispot AI SEO Spider maps every redirect in the crawl. It flags chains, loops and HTTPS downgrades, and lists the internal links that still point at redirected URLs.

Setting up redirects on WordPress

On WordPress you don't need server access. The free Digispot AI WordPress plugin creates unlimited 301, 302, 307, 308, 410 and 451 redirects, with:

  • regex matching for whole groups of URLs
  • loop prevention and hit counts
  • an automatic redirect when you change a post's slug
  • a 404 monitor that separates real missing pages from bot probes and turns a 404 into a redirect in one click

If you are moving from Yoast, Rank Math or the Redirection plugin, its importers bring your existing redirects across.

Redirects in a site migration

Migrations are where redirect mistakes cost the most. A short checklist:

  1. Map every old URL to its closest new URL. Export the old URLs from your sitemap, a crawl and Search Console before you start.
  2. Use 301s, one hop each.
  3. Update internal links, canonicals, hreflang and sitemaps to the new URLs. Don't make your own site rely on redirects.
  4. Keep redirects live for at least a year.
  5. Crawl the old URL list after launch to confirm every one returns a single 301 to a page that returns 200.
  6. Watch Search Console for spikes in 404s and redirect errors.

For the full process, see the SEO site migration checklist.

Common mistakes

  • Using 302 for a permanent move. Google keeps the old URL in the index longer.
  • Redirecting everything to the homepage. Google treats this as a soft 404. Redirect to the closest match, or return 404 or 410.
  • Leaving chains in place after several migrations.
  • Linking internally to redirected URLs. Google keeps crawling the old URLs, and Search Console lists them as "Page with redirect". That's often harmless, but it wastes crawl time. See how to fix "Page with redirect" in GSC.
  • Removing redirects too soon. Old backlinks then hit a 404.
  • Mixing redirects and canonicals that disagree. If A redirects to B, B's canonical should not point back to A.

Summary

Match the code to your intent: 301 (or 308) for permanent moves, 302 (or 307) for temporary ones. Keep every redirect to one hop, update your internal links, and crawl after every change.

Digispot AI covers both halves of the job. The SEO Spider finds redirect problems across any site, and the WordPress plugin fixes them without server access. One plan from $19/mo covers every tool, with SEO data, insights and AI credits included. See pricing.

More in the Technical SEO guide

Start with the What Is Technical SEO? A Complete Guide.

Audit any page in seconds

200+ SEO checks including Core Web Vitals, schema markup, meta tags, and AI readiness — trusted by 1,250+ SEO experts and marketers.

Questions & Answers

Frequently Asked Questions

Here are some of our most commonly asked questions. If you need more help, feel free to reach out to us.

Maya Krishnan

Written by

Maya Krishnan

SEO and AEO specialist, Digispot AI

Maya Krishnan is an SEO and AEO specialist at Digispot AI. She helps agencies and businesses across industries and countries grow organic traffic from Google and AI search, and knows the major SEO platforms well, from desktop crawlers to all-in-one suites. She checks and approves every article published under her name.

More from Maya Krishnan

Related Articles