# 301 redirect: how do you move a page without losing visitors?

> A 301 redirect tells browsers and Google a page has moved for good. When to use it, 301 vs 302, chains to avoid, how long to keep it, and a redesign example.

Updated on October 15, 2026 · https://app.pilotiko.com/en/glossary/301-redirect

A 301 redirect is an HTTP “Moved Permanently” response saying a resource has moved for good to the address given in the Location header. Browsers follow the new address automatically, and Google treats the target as the version to show in its results. It is the standard tool for a site redesign or a domain change.

## In short
- 301 and 308 signal a permanent move; 302, 303 and 307 a temporary one.
- Google treats a 301 as a strong signal that the target should be used.
- Googlebot follows up to 10 redirect hops, but Google advises keeping chains short.
- During a site move, Google recommends keeping redirects for at least a year.
- A server-side redirect is the most dependable method.

## What exactly happens during a 301 redirect?

The server answers with status 301 and a Location header holding the new address; the browser requests it straight away and the visitor lands on the right page without noticing [2]. MDN adds that search engines receiving this response attribute links from the old URL to the redirected one [2].

On Google's side, the crawler follows the redirect and the indexing pipeline treats it as a signal that the target is [canonical](https://app.pilotiko.com/en/glossary/canonical-tag) [1]. Google's status-code documentation describes a 301 as a strong signal and a 302 as only a weak one [4]. That is why the [backlinks](https://app.pilotiko.com/en/glossary/backlink) the old page earned keep working for you.

## 301, 302, 307 or 308: which one should you pick?

Google's rule of thumb: use a permanent redirect when you are sure it won't be reversed, and a temporary one if you want the old URL to stay in results, for instance while a service is paused [1]. MDN flags one technical wrinkle: after a 301, a browser may turn a POST form submission into a GET, whereas a 308 forbids that change [2]. For an ordinary business website page, a 301 is nearly always the right call.

| Code | Type | What Google shows |
|---|---|---|
| 301 Moved Permanently | Permanent | The new address (the target) |
| 308 Permanent Redirect | Permanent, request method kept | The new address |
| 302 Found | Temporary | Usually the original address |
| 307 Temporary Redirect | Temporary | Usually the original address |
| meta refresh at 0 seconds | Read as permanent | The target, though the method is less reliable |

Sources: Google Search Central [1] and MDN [2].

## How do you plan the redirects for a redesign?

**Example: a fictional bathroom-renovation company in Gatineau switches platforms**

“Outaouais Renovations Sample” is moving from an old site to a new one. The old site had 42 indexed URLs; the new one has 26, because several thin pages were merged. Each old URL gets a destination in a mapping spreadsheet.

The rules also cover technical variants: http to https, and the bare domain to the www version. Hypothetical figures.

- Old indexed URLs : 42
- 301-redirected to an equivalent page : 35
- Merged pages (several old → one new) : of which 12
- Removed with no equivalent (410 response) : 7
- Chained redirects left after testing : 0
- **= No old address lands on an error; anyone following an old link reaches the replacement page in a single hop.**

## How long should you keep a 301 redirect?

In its site-move guidance, Google recommends keeping redirects for as long as possible, generally at least one year, so it can transfer all signals to the new URLs [3]. From the visitor's point of view, it even suggests keeping them indefinitely, while updating your own links and high-traffic external links, since every redirect slows loading a little [3].

Google also warns that rankings may fluctuate during a migration, and that for a medium-sized site it can take a few weeks or more before new URLs replace the old ones in results [3].

## Which 301 redirect mistakes should you avoid?

- Chaining A → B → C; Google advises redirecting straight to the final destination, ideally with no more than 3 hops and fewer than 5 at worst [3].
- Sending every old page to the home page, so visitors can't find what they came for.
- Using a 302 for a permanent move, which may keep the old URL in Google's results [1].
- Leaving internal links pointing at old URLs; update your [internal linking](https://app.pilotiko.com/en/glossary/internal-linking) and your [XML sitemap](https://app.pilotiko.com/en/glossary/xml-sitemap).
- Removing redirects a few weeks after launch, so old links fall back onto a [404 error](https://app.pilotiko.com/en/glossary/404-error).
- Relying on a JavaScript redirect when the server could do it; Google lists that as a last resort [1].

## Should http redirect to https?

Yes. Google gives the example of a home page reachable through several addresses: pick one as the preferred destination and redirect the others to it [1]. The http-to-https switch is one of those variants, as are the www and non-www versions. Once the redirect is in place, an [HSTS](https://app.pilotiko.com/en/glossary/https-hsts) header can tell browsers to go straight to HTTPS on later visits.

## What does Pilotiko do with 301 redirects?

The [site Pilotiko hosts](https://app.pilotiko.com/en/product/website) keeps a redirect list: an old URL can be sent with a 301 to its replacement or marked as removed with a 410 response. The www and non-www variants are brought back to the main hostname with a 301, and an address missing its trailing slash is redirected to the matching page. Validated campaign (utm) parameters are carried through the redirect. For your current site, the audit flags pages reached through several successive redirects.

## Frequently asked questions

### Does a 301 redirect cost rankings?

Google describes a 301 as a strong signal that the target should replace the old URL, and MDN notes that search engines carry links over to the new address. Rankings can wobble during a migration while Google recrawls everything.

### How long should I keep a 301?

Google recommends at least a year after a site move and suggests keeping it indefinitely for visitors. Update your own links to point at the new URL as well.

### What is the difference between a 301 and a 302?

A 301 announces a permanent move, so Google shows the new address. A 302 announces a temporary one, so Google tends to keep the original address in its results.

### Can I set up a 301 without server access?

Most website platforms have a redirects module. Failing that, a meta refresh at 0 seconds is read by Google as permanent, though it is less reliable than a server-side redirect.

### Should a deleted page redirect to the home page?

Only if the home page genuinely answers what the visitor wanted. Otherwise redirect to the closest page, or return a 404 or 410 with a helpful error page.

## Sources

1. Google Search Central, « Redirects and Google Search », https://developers.google.com/search/docs/crawling-indexing/301-redirects (accessed on 2026-10-15)
2. MDN Web Docs, « 301 Moved Permanently », https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/301 (accessed on 2026-10-15)
3. Google Search Central, « Site moves and migrations », https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes (accessed on 2026-10-15)
4. Google (crawling documentation), « How HTTP status codes affect Google's crawlers », https://developers.google.com/crawling/docs/troubleshooting/http-status-codes (accessed on 2026-10-15)
