# 301 vs 302 redirect: which URL does Google keep?

> 301 vs 302 redirect compared on what Google keeps as canonical, what browsers cache and what happens to a POST, with a decision table for ten cases.

- URL: https://missiongrowth.io/blog/301-vs-302-redirect
- Published: 2026-11-02 · Updated: 2026-11-15
- Author: Furkan Aktaş, Co-Founder, Mission Growth
- Publisher: Mission Growth. Company facts: https://missiongrowth.io/llms.txt

The 301 vs 302 redirect choice looks like a question about duration. Google's own video of 4 November 2026 turns it into a question about survival: after the redirect, which of the two URLs should represent the page in search?

Browser caching and request method then decide what breaks if you guess wrong. The sections below take each factor in turn and end on a winner line. A short table of temporary vs permanent redirect cases closes the post.

## 301 vs 302 redirect in one answer: who should survive

A 301 redirect tells Google the old URL is gone for good and a 302 redirect says it will be back, so the choice is which URL you want to survive in search results.

> **Short answer**
> - Moved for good: use a 301 (or a 308).
> - Temporary, and the source must stay the indexed URL: use a 302 (or a 307).
> - Form data must survive the hop: use a 307 or 308.
> - Every click must reach your server, as with tracked short links: use a 307.

A 301 is the Moved Permanently status; a 302 is Found. Google's redirect documentation recommends a permanent server-side redirect when the URL shown in results should change, and says a temporary redirect may help keep the old URL in its Search results.

RFC 9110 words the temporary half as a promise about the future: since the redirection might be altered on occasion, the client ought to continue to use the target URI for future requests.

The 307 and 308 are the newer pair with the same permanent and temporary meanings. The 308 redirect and the 307 come back below because they treat the request method differently, and the 307 vs 302 and 301 vs 308 choices hinge on that.

Google puts the deciding line plainly: the choice depends on how long you expect the redirect to be in place and what page you want Google Search to show in search results. The first half of that sentence is the textbook rule. The second half is the one that matters in practice, because a temporary redirect is the right pick only when the source URL should keep showing up.

::figure{src="/blog/figures/301-vs-302-redirect-10.svg" alt="Two columns, 301 and 302, each naming which URL survives in search results and the situations where that code fits." caption="The short answer: 301 when the target must rank, 302 when the source must stay." width="720" height="245"}

**Winner: 301 for anything final; 302 only when the source must remain the indexed URL.**

## Canonical choice: which URL Google keeps

Google puts the source and target of any redirect in one cluster and lets only a 301 make the target the representative URL, so a 302 leaves the old URL in search results.

Gary Illyes and Cherry Prommawin walked through this in Google Search Central's video "301, 302, 307, 308: Which redirect is the chosen one?" on 4 November 2026. Illyes's point, paraphrased, is that Google is happy with either code for the grouping step, and that the 301 is the way to steer which URL wins afterwards.

In his words, "Basically within a cluster, we choose one representative page. The final selection process is called canonicalization."

::video{id="vfGGiFQbb7A" thumb="https://i.ytimg.com/vi/vfGGiFQbb7A/maxresdefault.jpg" width="1280" height="720" alt="Thumbnail of the official Google Search Central YouTube video" caption="Google Search Central, 301, 302, 307, 308: Which redirect is the chosen one?" title="301, 302, 307, 308: Which redirect is the chosen one?" description="What is the actual difference between a 301 and a 302 redirect and does it affect canonicalization? Gary Illyes and Cherry Prommawin explain how each redirect status code affects search deduplication, clustering, and the canonicalization process." uploaded="2026-11-04"}

That gives a three-step flow:

1. **Redirect seen.** Googlebot requests the old URL and receives a redirect response.
2. **One cluster forms.** The old and the new URL are now treated as the same page, whichever code was used.
3. **Canonicalization picks the survivor.** A 301 points that choice at the target. For a 302, Illyes says Google "assumes you are going back eventually, keeps the old URL in the search results, and basically ignores the new URL."

::figure{src="/blog/figures/301-vs-302-redirect-1.svg" alt="Flow from a redirect to a cluster of two URLs to the canonical choice, with the 301 branch ending on the target URL and the 302 branch ending on the source URL." caption="A redirect puts both URLs in one cluster; only a 301 then makes the target the representative URL." width="720" height="261"}

Search Console shows the result of step three. Its "Page with redirect" status describes a non-canonical URL that redirects to another page, and Google says such a URL will not be indexed; the target might or might not be indexed, depending on what Google thinks about it. Seeing that label on a URL you wanted to rank means Google did not choose it as the representative URL.

The wider comparison of redirects with other duplicate-handling methods lives in our guide to [canonical tag vs redirect](https://missiongrowth.io/blog/canonical-tag) trade-offs.

Prommawin adds the reassurance that keeps this from being alarming: "There are technically correct choices, but getting it wrong is not the end of the world. Google will still index the page." A wrong code changes which URL shows, and it does not remove the content from the index.

**Winner: 301 when the target must rank; 302 when the source must keep ranking.**

## Link equity: what each redirect passes

Whether a 302 passes PageRank is the wrong question, because both codes put the two URLs in one cluster and the status code only decides which URL the canonicalization step picks.

The amount passed is where third-party advice goes wrong: some comparison tables print a percentage for a 301 and say a 302 passes nothing permanent. Google's own remarks, taken in date order, give no percentage, so we state none.

In February 2016 John Mueller answered the old claim directly: "That's a myth." In August 2016 Illyes tweeted: "redirects pass same, but 301 helps with canonicalization".

Ten years later, the Google video says a 301 means Google "takes all the ranking signals of the old page and hands them to the new page", and a 302 keeps the old URL and basically ignores the new one.

::figure{src="/blog/figures/301-vs-302-redirect-4.svg" alt="Timeline with three dated Google statements: Mueller February 2016, Illyes August 2016, Illyes and Prommawin November 2026." caption="Google's statements on redirects, 2016 to 2026 (the last from the 4 November 2026 Google video), and what each says about PageRank and the surviving URL." width="720" height="198"}

Read together, the 2016 and 2026 statements describe two steps. Grouping the URLs is the same for both codes, which is what the 2016 statements say. The canonicalization step is where they differ, which is what the 2026 video adds. The code picks the survivor and the amount is a side effect of who survives.

So does a 302 pass link equity? Per Mueller in 2016, yes; what it does not do is make the target the survivor.

Two practical corollaries follow. Removing 302 redirects lifts nothing by itself: by the mechanism, it matters only if the 302 was meant to be permanent. And don't plan on a 302 left in place for months turning into a 301: Google has no documented threshold for it.

**Winner: 301 when the signals should end on the target; 302 when they should stay on the source.**

## Browser caching: which redirect is harder to undo

A 301 or 308 response may be stored by a browser without asking the server again, while a 302 or 307 is stored only when the server sends explicit freshness information.

The rule comes from RFC 9110, which lists the status codes that can be reused by a cache with heuristic expiration. The list includes 301 and 308 and leaves out 302 and 307. RFC 9111 adds the exception: a response carrying an Expires header or a max-age directive can be stored by a cache whatever its status.

::dataset{key="redirect-cacheability" name="Which redirect codes a cache may store, per RFC 9110 and RFC 9111"}

| Status | Heuristically cacheable | With explicit freshness (max-age or Expires) |
|---|---|---|
| 301 | Yes | Yes |
| 308 | Yes | Yes |
| 302 | No | Yes |
| 307 | No | Yes |

::figure{src="/blog/figures/301-vs-302-redirect-5.svg" alt="Matrix of 301, 302, 307, 308 against heuristically cacheable and cacheable with explicit freshness." caption="Which status codes a browser may store without asking the server, and how explicit max-age changes it." width="720" height="325"}

The consequence is asymmetric.

A mistaken 301 can outlive the fix, because a browser that stored it may send visitors to the old destination without contacting your server, and no server-side change reaches that browser until the stored copy expires or is cleared. A 302 with a long `Cache-Control: max-age` is just as sticky as a 301, so "302 is safe to cache-bust" holds only while you leave caching headers alone.

::figure{src="/blog/figures/301-vs-302-redirect-6.svg" alt="Two flows: repeat visit after a 301 goes straight to the new URL, repeat visit after a 302 asks the server first." caption="What a browser does on a repeat visit after a 301 versus a 302." width="720" height="219"}

This is also why "301 is cached, 302 probably not" is the right summary with the wrong confidence. The accurate version is that a 301 is heuristically cacheable, a 302 is not, and any of them becomes cacheable the moment the server sends explicit freshness.

How long can a heuristic copy last? RFC 9111 lets a cache reuse a response for a fraction of the time since its Last-Modified date, and calls 10% a typical setting. For a redirect last modified a year ago, that's about 36 days of reuse with no max-age at all.

An explicit header sets the clock instead. MDN's own 301 reference shows an example response with `cache-control: max-age=2592000`, which is 30 days, so a browser that stored it keeps that redirect for a month after you change the server.

So send an explicit, short Cache-Control on any redirect you might reverse, and a long one only on redirects you'll never undo.

**Winner: 302 for reversibility, unless you set Cache-Control yourself.**

## Request method: what happens to a POST

After a 301 or 302 a client may turn a POST into a GET, which drops the submitted form data, whereas a 307 or 308 forbids changing the method.

Take a checkout form that posts card details to a payment host, which fails over to a backup host and answers with a redirect. The trace with a 302 looks like this:

```
POST /pay            -> 302 Location: /pay-backup
GET  /pay-backup     -> (no form body, no card data)
```

The browser followed the redirect and silently replaced the POST with a GET, so the backup host receives an empty request. With a 307 the trace changes:

```
POST /pay            -> 307 Location: /pay-backup
POST /pay-backup     -> (same body resent)
```

RFC 9110 is explicit that with a 307 the user agent MUST NOT change the request method, so the 307 resends the same body to the new location. The 302 behavior predates the method-preserving codes, and curl's documentation describes it: the non-RFC behavior is ubiquitous in web browsers, so curl does the conversion by default to maintain consistency.

You can reproduce both on the command line. Plain `curl -i -L -d 'a=b' https://example.com/pay` converts the POST into a GET after a 302. Adding `--post302` keeps it a POST. A 303 is the redirect that always switches to GET by design, which is useful after a successful form submission and wrong for failover.

::figure{src="/blog/figures/301-vs-302-redirect-2.svg" alt="Two paths for one form submission: a 302 path ending in a GET with no form data, a 307 path ending in a POST with the same data." caption="The same checkout POST after a 302 arrives as a GET; after a 307 it arrives as a POST with its body." width="720" height="295"}

None of this changes how Google treats the page, since Googlebot does not submit your forms. It matters for real users and for APIs.

**Winner: 307 or 308 whenever the request is not a GET.**

## 307 and 308: when the modern pair replaces 302 and 301

A 307 is the modern temporary redirect and a 308 the modern permanent one, and Google's redirect documentation lists 308 beside 301 as permanent and 307 beside 302 as temporary.

Illyes describes the 308 Permanent Redirect in the video as "A 308 is the more modern version of a permanent 301." The pairs differ on three points:

| | 301 / 308 | 302 / 307 |
|---|---|---|
| Google treatment | Permanent | Temporary |
| Caching per RFC 9110 | Heuristically cacheable | Not heuristically cacheable |
| Request method | 301 may change POST to GET; 308 keeps the method | 302 may change POST to GET; 307 must not change it |

Google lists each pair under one treatment, permanent or temporary, so the choice inside a pair is not a ranking choice.

Google treats 301 and 308 as permanent and 302 and 307 as temporary, so the SEO choice between them rests on request method and on what your stack emits by default. A framework that sends a 301 for a page move is fine for a GET page. An API endpoint or a form handler wants the 308 or 307, because only those keep the method.

::figure{src="/blog/figures/301-vs-302-redirect-7.svg" alt="Quadrant with permanence on one axis and method handling on the other, placing 301, 302, 307 and 308." caption="The four codes placed on permanence against method handling." width="720" height="440"}

The practical rule is short. If the request method can change without harm, which is every plain page move, pick whichever code your server already emits and confirm its permanence matches your intent. If the method cannot change, pick the member of the pair that preserves it.

**Winner: 308 and 307 for non-GET traffic; 301 and 302 for plain page moves where your stack already emits them.**

## Site moves, HTTPS and www: use a permanent redirect

A permanent redirect is the right choice when the old URL will never serve its content again, such as a domain move, an HTTP to HTTPS upgrade or a www to non-www canonical host.

Google's guidance is to use a permanent server-side redirect whenever the URL shown in results should change, and these four cases all qualify:

- **Domain move.** The old domain is retired, so the target must replace it in the index.
- **HTTP to HTTPS.** The insecure version should never be the representative URL; the secure one takes over.
- **www to non-www (or the reverse).** One host becomes the canonical one, and the other points at it for good.
- **Merged or renamed pages.** The old path has no content left, so the new path should carry the page.

In every case the old URL is not coming back, which is precisely what a 301 says. A 302 here would keep telling Google you may return, and the canonicalization step would keep favouring the URL you abandoned.

Sequencing a move (redirect maps, launch order) is its own subject, covered in our [site migration seo](https://missiongrowth.io/blog/site-migration-seo) guide. The status-code choice is the easy part of a migration; the order of operations is where moves go wrong.

The status code also has to stay in place long enough. Google's site-move guide says to keep the redirects generally at least 1 year, so Google can transfer all signals and recrawl links on other sites. The Change of Address tool's help asks for at least 180 days, and longer while Google Search still sends traffic through them.

Treat the year as the floor, and check traffic to the old URLs before you remove a rule.

**Winner: 301 (or 308).**

## Campaigns, A/B tests and maintenance: use a temporary redirect

A temporary redirect fits any change that will be reversed, because Google keeps the old URL in results and does not treat the redirect as a canonical signal.

Three cases come up most:

- **A/B test.** Google's website-testing guidance is direct: "If you're running a test that redirects users from the original URL to a variation URL, use a 302 (temporary) redirect, not a 301 (permanent) redirect." A 301 would tell Google the original is gone and the variation is the page, which is the opposite of what a test means.
- **Temporary outage.** A temporary redirect to an explanation page keeps the original URL in Search, so the page is still there when the outage ends. A permanent redirect to a status page would risk replacing it.
- **Time-limited promotion.** A seasonal landing page that takes over a path for a few weeks should hand the path back afterwards. With a 301, the path's history stays attached to a page you are about to retire.

The failure mode is the same in all three: a 301 invites Google to make the temporary destination the representative URL, and an undo then has to fight browser caches as well, which the caching section covered.

So give a campaign redirect a short Cache-Control of its own. A 302 is stored only when the server sends freshness, and a max-age of 2592000, the value in MDN's own 301 example, would keep returning visitors on the promotion for 30 days after it ends. Set max-age shorter than the campaign's remaining run, or send no-store.

A redirect that depends on the visitor (language, country) is a different problem from a campaign. Its status code sits in the language row of the summary table below.

**Winner: 302 (or 307 for non-GET).**

## Short links: why click counts favour 307

URL shorteners that need every click to reach their server avoid 301 because browsers and caches may store the destination, which makes click counts inaccurate.

BL.INK short links are the vendor example. Its help page says that by default BL.INK short links are 307 redirects.

The reason it gives: proxy and caching servers, including most browsers, may cache the destination URL, which may not give accurate click counts. 

The mechanism is the RFC 9110 caching rule from earlier. A heuristically cacheable 301 lets a browser skip the shortener on a repeat click, so the shortener never sees it. A 307 is not on that list, so the browser asks again.

::figure{src="/blog/figures/301-vs-302-redirect-8.svg" alt="Two paths for a repeated click on a short link, one stopping in the browser cache, one reaching the shortener." caption="A cached 301 skips the shortener on repeat clicks; a 307 reaches it every time." width="720" height="295"}

Does the extra hop hurt SEO?

That depends on what the link is for, not on the hop itself: the cost of a 301 is the repeat clicks it can hide, and its benefit is the permanent signal Google reads.

For a campaign link you want to measure, take the 307. For a permanent vanity link whose job is to be the stable address of a page, take the 301 and accept that repeat clicks may go uncounted.

**Winner: 307 (or 302) for tracked short links; 301 for permanent vanity links where SEO matters.**

## How to undo a wrong redirect

A wrong 302 is fixed by changing the status code on the server, while a wrong 301 also has to expire in browsers that stored it.

To turn a 302 that should have been permanent into a 301:

1. Change the status code on the server and keep the redirect target live.
2. Re-test in a private window, which starts without stored redirects.
3. Run URL Inspection in Search Console on the old URL and read the result.

To undo a 301 that should have been a 302, or should not exist at all:

1. Change the response to a 302 or remove the redirect, and keep the old destination live in the meantime.
2. Clear the cache in your own browser and re-test; visitors' browsers hold stored copies you cannot reach, so those clear only on expiry or when the visitor clears them.
3. Check Search Console. If "Page with redirect" still appears for a URL you now want indexed, the redirect is still being served somewhere, or Google has not recrawled yet.
4. If the old 301 had no explicit freshness, remember that RFC 9110 lets caches store it heuristically, which is why the fix may not reach every visitor at once.

The reason for the extra steps is the asymmetry in the caching section: the server is under your control, the browser cache is not. When you are unsure which direction a change will take, send a 302 first. It is cheaper to promote a temporary redirect to a permanent one than to retract a permanent one.

## How to check which redirect a URL returns

Three tools show the status code and Location header of a URL: curl with headers only, the browser's network panel with preserved log, and Search Console's URL Inspection.

Read the same three fields in each: the status line, the Location header and Cache-Control.

- **curl.** `curl -sI https://example.com/old` prints the status code and the Location header without following the redirect, and it ignores the browser cache. Add `-L` to follow the chain and see each hop.
- **Browser network panel.** Turn on preserved logs so the redirect row survives navigation. It can miss the first hop, because a browser may serve a stored 301 without asking the server at all.
- **Search Console URL Inspection.** It shows what Google saw on its last crawl, which can differ from what your server returns now.

One blind spot: curl shows only server responses. A redirect that a script performs in the browser leaves no Location header, which is why client-side redirects belong in a [javascript seo](https://missiongrowth.io/blog/javascript-seo) review.

To check many URLs at once, server logs show what Googlebot actually requested and which codes it received; the [crawl budget](https://missiongrowth.io/blog/crawl-budget) guide covers that side.

**Winner: curl, because it ignores the browser cache.**

## Redirect chains: one hop is the target

Google advises redirecting straight to the final destination and keeping any redirect chain ideally to no more than 3 redirects. Its crawlers follow up to 10 hops by default, so a longer chain can stop before the page.

The wording on Google's site-move page is: "we advise redirecting to the final destination directly. If this is not possible, keep the number of redirects in the chain low, ideally no more than 3 and fewer than 5."

Other clients stop at different depths, which is why a chain that loads in your browser can still fail elsewhere:

- **robots.txt.** Google follows at least five redirect hops for the robots.txt file, then treats it as a 404, which reads as no robots.txt at all.
- **Googlebot on pages.** Google's crawlers follow up to 10 hops.
- **Browsers.** The Fetch standard returns a network error once a request's redirect count reaches 20, which is the error page a redirect loop ends on.
- **curl.** With `-L`, curl follows up to 50 redirects by default.

::figure{src="/blog/figures/301-vs-302-redirect-11.svg" alt="Redirect hop limits compared: Google advises 3, Googlebot follows 10, browsers stop at 20 and curl at 50." caption="How many redirect hops each client follows before it gives up; Google’s advice is 3 at most." width="720" height="263"}

So a check that only asks whether the page loads will pass chains Google dislikes. Add `--max-redirs 3` to your curl check, and it fails exactly where Google's advice says to stop.

```
A -> B -> C     chain: two hops, two chances for a different code
A -> C          one hop: the code on A is the code Google reads
```

Collapsing the chain also removes a quieter risk, mixed codes. A 301 followed by a 302 leaves the last hop temporary, and the canonicalization step has to work out what you meant. Check the final status of a chain, and keep the same code type end to end.

A chain of 301s is not an error in itself, but each extra hop is a place for a mistake, so flatten it.

An inherited long chain gets one fix: point the first URL at the last destination and update whatever linked to the middle ones. Each hop is also another request, and our crawl budget guide covers when that matters.

**Winner: one hop, same code type end to end.**

## Update internal links and the sitemap after a 301

After a permanent redirect you change internal links and the sitemap to the new URL, while after a temporary redirect the source stays the indexed URL and its links stay as they are.

For a 301, Google's site-move instruction is to change the internal links on the new site from the old URLs to the new URLs. The same logic covers the sitemap: it should list the URL you want to be the representative one, which after a 301 is the target.

Links and the sitemap aren't the only places that still name the old URL, and they aren't the ones Google weighs most. Google's canonicalization guide rates the redirect and a rel="canonical" link as strong signals and sitemap inclusion as a weak one. So check the target page's own tags first:

- **Canonical tag.** Google's site-move guide asks for a self-referencing canonical on each new URL. A template that still points the new page's canonical at the old URL sets one strong signal against the other.
- **Hreflang.** If the moved pages have language or country alternates, update those annotations to the new URLs as well.
- **Sitemap.** Submit the new sitemap in Search Console; at that point Google says you can remove the old one. A stale entry is the weakest of the three, so fix it last, not never.

Leaving old URLs in your links or the sitemap sends every crawl and every visitor through a redirect you already resolved. Our [internal linking strategy](https://missiongrowth.io/blog/internal-linking-strategy) guide covers how to find and update those links.

Redirected URLs are also rare in AI answers. SE Ranking's December 2025 study collected the URLs ChatGPT cited across 100,000 prompts and compared them with Google's results.

Only 0.79% of the 145,463 URLs ChatGPT cited were redirects, against 5.75% of 422,814 organic results, 5.45% of 485,400 AI Mode citations and 2.85% of 438,903 AI Overview citations.

The study counts citations, so it shows a pattern, not a cause. The practical reading still matches Google's site-move rule: link to and list the final URL, so no engine has to resolve a redirect to reach your page.

For a 302 the reasoning runs from the canonical mechanism: the source URL remains the representative URL, so its internal links and its sitemap entry are correct as they stand. Rewriting them to the temporary destination would point your own site at the URL Google is least likely to keep.

| | After a 301 | After a 302 |
|---|---|---|
| Internal links | Change to the new URL | Leave on the source URL |
| The sitemap | List the new URL | Keep the source URL |
| Why | The target is the representative URL | The source stays the representative URL |

**Winner: update after a 301, leave after a 302.**

## 301 vs 302 summary table

The summary table puts 301, 302, 307 and 308 side by side on Google treatment, caching and method, followed by a by-situation table with one status code per case.

::dataset{key="redirect-codes-compared" name="301, 302, 307 and 308 compared on Google treatment, caching and method"}

| Code | Google treatment | Canonical effect | Caching | Method | Use when | Do not use when |
|---|---|---|---|---|---|---|
| 301 | Permanent | Target becomes the representative URL | Heuristically cacheable | May change POST to GET | A page moved for good | The source must stay indexed |
| 302 | Temporary | Source stays in results | Not heuristically cacheable | May change POST to GET | A change will be reversed | The move is final |
| 307 | Temporary | Same as 302 | Not heuristically cacheable | Must not change | Temporary, non-GET traffic | You want a permanent signal |
| 308 | Permanent | Same as 301 | Heuristically cacheable | Keeps the method | Permanent, non-GET traffic | The change is temporary |

::figure{src="/blog/figures/301-vs-302-redirect-3.svg" alt="Matrix of four redirect status codes against Google treatment, browser caching and request method." caption="Google treatment, caching and method handling for 301, 302, 307 and 308." width="720" height="297"}

### Which redirect for each situation

Find your case in the first column, then read the status code and the reason beside it.

::dataset{key="redirect-by-situation" name="Which redirect status to use in ten common situations"}

| Situation | Status | Reason |
|---|---|---|
| Domain move | 301 (or 308) | The old domain never serves content again |
| HTTP to HTTPS | 301 (or 308) | The secure URL should be the representative one |
| www to non-www | 301 (or 308) | One host becomes canonical for good |
| A/B test | 302 | Google says use a 302 for test redirects, not a 301 |
| Maintenance page | 302 | The original URL stays in Search |
| Time-limited promotion | 302 | The path is handed back afterwards |
| Form failover | 307 | The POST body must be resent |
| Tracked short link | 307 | Every click must reach the shortener |
| Permanent vanity short link | 301 | SEO matters more than click counts |
| Language redirect | 302, where unavoidable | See below |

The language redirect row needs one more sentence. A redirect that depends on the visitor is temporary by nature: RFC 9110 says a 302 means the client keeps using the original URI, and the same URL serves different people differently. 

Google also advises against automatically redirecting users from one language version of a site to another. Use a 302 only where such a redirect is unavoidable, and read our [multilingual seo](https://missiongrowth.io/blog/multilingual-seo) guide for the trap that sits behind it.

**Winner: if you are unsure which row applies, the code that matches who should survive.** A 301 or 308 makes the target the survivor; a 302 or 307 keeps the source.

This is the whole argument in one line: both codes link the two URLs, and the status code only chooses the representative one. Before you ship your next redirect, run `curl -sI` on the old URL and confirm that the status code you see is the one you meant.

## FAQ

### Is a 301 a permanent redirect?

A 301 is the Moved Permanently status, and Google treats it as a permanent redirect. It tells Google that the target should replace the old URL in search results.

### Is a 301 an error?

A 301 is a normal response, and it signals no failure. It becomes a problem only when it points the wrong way or sits in a long chain.

### Should I use 301 or 308?

A 301 or 308 gets the same permanent treatment from Google, as the video and the documentation list both. Choose 308 when the request method must be preserved, and 301 for plain page moves.

### Does a 302 pass link equity?

A 302 does pass it, per Mueller in 2016, who called the opposite claim a myth. What a 302 does not do is make the new URL the representative one, so the old URL stays in results.

### What does "Page with redirect" mean in Search Console?

"Page with redirect" marks a non-canonical URL that redirects to another page. Google will not index that URL, while the target might or might not be indexed.

### How long does a 301 take to work?

A 301 takes effect when Google next recrawls the old URL, so it has no fixed duration. Recovery timescales are covered in our site migration seo guide.

### Can a browser cache a 302?

A browser can cache a 302 only when the response carries explicit freshness, such as max-age or Expires. Without it, a 302 is not heuristically cacheable, unlike a 301.

### Should I use 307 or 302 for a temporary redirect on a POST endpoint?

A 307 is the right choice for a POST endpoint, because RFC 9110 says the user agent must not change the request method. A 302 lets a client turn the POST into a GET and drop the body.
