301 redirect

A 301 redirect is a permanent redirect from one URL to another, telling browsers and search engines that a resource has moved for good. The HTTP 301 status code ('Moved Permanently') is the standard way to handle an address change while preserving hard-won SEO value and giving users a smooth path to the correct content.

How a 301 redirect works

When a browser or search engine crawler requests the old address, the server responds with a 301 status and points to the new URL, to which the redirect happens immediately. Unlike a temporary redirect, a 301 signal instructs search engines to permanently update their index. Its key characteristics are:

• Permanence — an unambiguous signal that the address change is final.
• Link equity transfer — near-full transfer of backlink value to the new address.
• Index update — replacing the old URL with the new one in search results.
• Caching — browsers remember the redirect, speeding up subsequent visits.

301 redirects in practice

301 redirects are indispensable during many site operations:

1. URL restructuring — moving to friendly URLs without losing rankings.
2. Domain migration — moving an entire site to a new address.
3. Content consolidation — merging duplicate pages and eliminating duplicate content.

On Apache servers, 301 redirects are most often configured in the .htaccess file. To avoid losing link equity, it is best to point the old address straight to its final destination, avoiding chains of multiple consecutive redirects.

Common mistakes when implementing 301s

The most frequent mistake is mass-redirecting all old addresses to the home page instead of to their real equivalents — the user then loses context and the search engine treats such a redirect as a soft 404. Another problem is redirect chains (A→B→C), which slow loading and dilute link equity. It is also worth keeping the protocol and domain version consistent: redirects from HTTP to HTTPS and from the 'www' version to its non-'www' counterpart (or vice versa) should be set once and consistently, to avoid duplicate addresses. After every larger change it is worth verifying the response codes with a site-crawling tool.