A 301 redirect is an HTTP response that tells a client a resource has moved permanently. The response normally includes a Location header pointing to the new URL. Browsers can follow that address, and Google uses a permanent redirect as a signal to prefer the destination URL.

What is a 301 redirect?

301 Moved Permanently is a server response, not an HTML link. A person can request the old address and reach its replacement without having to find the new URL. The HTTP standard defines the status and the Location header used to identify the destination.

Configure the response in your hosting settings, CDN, web server or application. The right place depends on who controls the URL. An application can issue a proper HTTP redirect; it does not have to use JavaScript in a page.

What it changes for search and visitors

For search, the redirect connects an old address with a new one. Google’s redirect guidance treats 301 and 308 as permanent moves and 302 and 307 as temporary moves. A permanent redirect signals that Google should prefer the destination; it does not guarantee a particular ranking or immediate replacement in results.

For visitors, the useful test is simpler: does the replacement answer the same need? A moved installation guide should open the replacement guide, not an unrelated sales page.

Request and response example

This illustrative exchange shows a normal page request. The old address returns a redirect; the browser requests the destination, which returns the page.

GET /old-guide/ HTTP/1.1
Host: example.com

HTTP/1.1 301 Moved Permanently
Location: https://example.com/new-guide/

GET /new-guide/ HTTP/1.1
Host: example.com

HTTP/1.1 200 OK

The status and destination are separate checks. A response can return 301 while pointing to the wrong page, a missing page or another redirect.

301, 302, 307 and 308 compared

Choose by whether the move is permanent and whether the client must preserve the request method. This matters for POST requests, such as form or API submissions.

Redirect status and request-method handling
StatusMoveRequest methodTypical choice
301PermanentA client may change POST to GET.A permanently moved content page.
302TemporaryA client may change POST to GET.A temporary alternate page.
307TemporaryThe client must preserve the method.A temporary endpoint move that retains the request method.
308PermanentThe client must preserve the method.A permanent endpoint move that retains the request method.

Source: RFC 9110, sections 15.4.2, 15.4.3, 15.4.8 and 15.4.9. Google groups 301 with 308 for permanent redirect handling, but other clients still need the correct HTTP semantics.

When a permanent redirect fits

  • A renamed page: map the old slug to the current version of the same content.
  • Merged articles: send retired URLs to a consolidated page that retains the relevant information.
  • A preferred hostname: send alternate hostnames to the corresponding page on the chosen hostname.
  • A move to HTTPS: send the HTTP address to its secure counterpart.

These are URL-mapping examples, not evidence that a website migration will leave traffic unchanged. Keep the mapping so you can trace each old address to its intended replacement.

Use a 301 when visitors should leave the old URL. Use a canonical URL annotation when duplicate or similar versions must remain accessible, but you want to identify the preferred version for search.

Google describes both redirects and rel="canonical" as strong canonicalization signals. Calling one a guaranteed instruction and the other a weak hint misstates that distinction. Neither removes the need for consistent internal links, sitemap URLs and destination content.

Implementation checklist

  1. Map the destination. Record the old URL, its replacement and the reason for the change. Check that the new page answers the old page’s purpose.
  2. Check the replacement first. Open it, inspect its status and verify its content. Confirm that it is crawlable and indexable if it should appear in search.
  3. Issue the intended response. Check the old URL’s status and Location header, then follow the route to confirm the final destination.
  4. Update references. Point internal links, sitemap entries and canonical annotations to the new URLs.
  5. Monitor actual requests. Keep a record of broken destinations, unexpected routes and search changes after release.

A useful command-line check is curl -sS -D - -o /dev/null https://example.com/old-guide/. Add -L to follow redirects and inspect the full response chain. Replace the example address with your own page; headers alone cannot prove that the destination is relevant.

Common mistakes

An irrelevant destination does not solve a missing page

Google warns that unrelated redirects, such as sending many retired pages to a homepage, may be treated as soft 404s. If no replacement exists, return a genuine 404 or 410 rather than redirecting simply to avoid an error. See Google’s site-move guidance.

A redirect chain adds requests before the visitor reaches the page. A loop sends requests back to an earlier URL. Test alternate hostnames, protocol variants and trailing-slash rules together so one rule does not undo another.

Prefer HTTP redirects where possible. Instant meta refresh can also signal a permanent move, so it should not be dismissed as necessarily passing no search value. JavaScript redirects depend on successful rendering, so Google recommends using them only when the other methods are unavailable.

Frequently asked questions

Does a 301 redirect preserve SEO value?

Google says permanent redirects do not cause PageRank loss. This is not a promise that every ranking will stay unchanged: the replacement page, crawl access and other changes still matter.

How long does Google take to process a 301 redirect?

There is no fixed processing deadline. Google must discover and process the moved URLs; crawl frequency, site size and server capacity affect the timing. Check the old and new URLs in Search Console rather than relying on a 24-hour promise.

Can I chain multiple 301 redirects?

A redirect chain can work, but a direct route to the final destination is easier to maintain and avoids extra requests. Googlebot generally follows up to 10 hops for web content; other Google crawlers and tools can behave differently.

How long should I keep a 301 redirect?

For a site move, Google recommends keeping redirects as long as possible, generally at least one year. Keep useful old addresses working longer when bookmarks or external links still send people to them.

Sources for these answers: Google’s site-move guidance and crawler HTTP-status guidance. The hop limit describes general web crawling, not every Google tool or a recommended chain length.

Sources and editorial note

This entry was revised with AI assistance against the primary references above. It explains redirect semantics and editorial checks; it does not report a migration test or claim named expert approval. The original publication date remains unchanged.