301 vs 302 Redirect: Permanent or Temporary, and Where 307 and 308 Fit
Both send the visitor to the same place. The difference is what they promise. A 301 says the old URL is gone for good and the new one should take its place in search. A 302 says the move is temporary and the old URL should stay. Pick the wrong one and Google keeps showing the address you meant to retire, or drops the one you meant to keep.
301 vs 302 vs 307 vs 308 at a Glance
| Code | Type | Keeps POST | Google shows | Cached by default | Use for |
|---|---|---|---|---|---|
| 301 | Permanent | ◐ | New URL | ✓ | Moves, merges, https |
| 308 | Permanent | ✓ | New URL | ✓ | Moves, forms, APIs |
| 302 | Temporary | ◐ | Old URL | – | Short changes, tests |
| 307 | Temporary | ✓ | Old URL | – | Short changes, APIs |
| 303 | Temporary | – becomes GET | Old URL | – | After a form post |
Sources: Google's redirects and Google Search for what Google shows, and RFC 9110, section 15.4 for methods and caching. "Keeps POST" partly means the RFC lets a browser change a POST into a GET for 301 and 302, for historical reasons; 307 and 308 forbid it. For ordinary page links, which are GET requests, 301 and 308 behave the same, and so do 302 and 307.
What Google Does With a 301 and a 302
Google follows both. What changes is the signal. Its page on HTTP status codes calls a 301 or 308 a strong signal that the redirect target should be canonical, and a 302, 303 or 307 a weak one. Its redirects guide puts it in terms of results:
| Redirect | Signal | In search results |
|---|---|---|
| 301, 308 | Strong | Shows the new target |
| 302, 303, 307 | Weak | Shows the source page |
| Meta refresh, 0 seconds | Permanent | Shows the new target |
| Meta refresh, delayed | Temporary | Shows the source page |
| JavaScript location | Permanent, if rendered | Shows the new target |
A weak signal is still a signal. Canonicalization weighs redirects with internal links, sitemaps and canonical tags, so a 302 that stays in place while everything else points at the target can still end with the target chosen. Do not rely on that: send the code that says what you mean.
When to Use a 301 (or 308)
Use a permanent redirect when you are sure it will not be reverted:
- Moving to a new domain, or from http to https.
- Changing a URL structure, a slug or a folder name.
- Merging two pages on the same topic into one.
- Settling one version of a URL: www or not, trailing slash or not, letter case.
- Retiring a product with a direct successor.
Google's site move guide says to keep redirects as long as possible, generally at least 1 year. It also warns against sending many old URLs to one irrelevant page such as the home page, which may be treated as a soft 404. SEO ProCheck shows how to set up 301 redirects on common servers.
When to Use a 302 (or 307)
- A/B tests that send some visitors to a variant URL. Google's website testing guide asks for a 302, not a 301.
- Short promotions, such as a seasonal page that stands in for a category for a few weeks.
- Logins. Sending a signed out visitor to the sign in page and back.
- Stock or availability swaps that will be undone soon.
Not for maintenance: a site that is down should answer 503 with a Retry-After header, not redirect everything to a notice page. The HTTP status code checker guide has the full table of which code to send when.
Common Redirect Mistakes
| Mistake | Effect | Fix |
|---|---|---|
| 302 for a permanent move | Old URL stays in results | Change to 301 |
| 301 for a short change | Browsers cache it | Use 302 or 307 |
| Deleted pages sent home | May count as soft 404 | Closest page or 404 |
| Redirect chains | Extra hops, slower | One hop to final URL |
| Internal links to redirects | Every visit takes a hop | Link to final URL |
| http answers 200 | Every page twice | 301 to https |
| Delayed meta refresh | Read as temporary | Server side 301 |
The second row bites during launches. Browsers keep a 301 in their cache, so even after you remove it, people who already followed it keep landing on the target until their cache clears. The sixth one we found on our own site: in our SEO pass on November 20, 2026, http://neova.app answered 200 instead of a 301 to https, so every page existed twice. One server rule fixed it. Chains are covered in redirect chains.
How to Check Which Redirect a URL Uses
Ask for the headers and follow every hop:
curl -sIL https://example.com/old-page | grep -iE '^(HTTP|location)'
HTTP/2 301
location: https://example.com/new-page
HTTP/2 200
Each HTTP line is one response, so the first number is the redirect type. In a browser, use the Network tab with Preserve log on, and a private window, since a cached 301 never reaches the server. SEO ProCheck's case study Night of the Living 302s looks at how crawlers and Search Console report temporary redirects.
301, 302, 307 and 308 on Apache and nginx
# Apache, .htaccess
Redirect 301 /old/ https://www.example.com/new/
Redirect 302 /sale/ https://www.example.com/winter-sale/
Redirect 308 /api/v1/ https://www.example.com/api/v2/
# nginx
location = /old/ { return 301 https://www.example.com/new/; }
location = /sale/ { return 302 https://www.example.com/winter-sale/; }
location = /form/ { return 307 https://www.example.com/form-v2/; }
On Apache, a bare Redirect with no code sends a 302, so write the number every time. In a CMS or on a CDN, look for the redirect type next to each rule; many default to 301, some to 302.
Check Your Redirects With Neova
Neova's Redirects category shows where redirects go, how many hops they take, loops, temporary redirects, meta refresh and JavaScript redirects, and the links that point at them. For a migration, Redirect Map matches every URL of the old site crawl to the new one with a confidence, and Live Redirect Check tests each old URL's live redirect against the map and flags the wrong or missing ones.
The checks behind it include:
- Internal URL Uses a Temporary Redirect, for 302, 303 and 307, leaving login and sign in targets alone
- Internally Linked URL Redirects, with the links to update
- Internal URL Is in a Redirect Chain and Internal URL Is in a Redirect Loop
- Internal Redirect Ends on a 4xx or 5xx
- Meta Refresh Is Used as a Redirect and HTML Page Redirects Through JavaScript
- HTTP URL Lacks a 301 to HTTPS or Receives Internal Links
- HTTPS URL Redirects to HTTP
- Redirecting URL Is Listed in an XML Sitemap
- Redirected URL Received Clicks in Search Console
The Free plan crawls 1,000 URLs a crawl with every check, on Mac, Windows and Linux. Download Neova.
Questions
What is the difference between a 301 and a 302 redirect?
A 301 is permanent: Google treats it as a strong signal to show the new URL. A 302 is temporary: Google treats it as a weak signal and keeps showing the old URL. Browsers also cache a 301 by default and not a 302.
Is a 302 redirect bad for SEO?
Not when the change is temporary, which is what it is for. It becomes a problem when a permanent move uses a 302, because Google may keep the old URL in results.
What is the difference between 301 and 308?
Both are permanent and Google treats them the same. A 308 also requires the browser to repeat the same method, so a POST stays a POST. For ordinary pages, either works; 301 is more common.
When should I use a 307 redirect?
For a temporary redirect where the request method must not change, such as a form or an API call. For search, Google treats a 307 like a 302. Note that browsers also show a 307 internally when HSTS upgrades http to https.
How long should I keep a 301 redirect?
Google's site move guide says as long as possible, generally at least 1 year. Many sites keep them for good, since old links on other sites never stop pointing at the old URLs.