Redirection 301

Technical explanation

The server returns status code 301 with a Location header. Browsers follow the destination, and search engines generally treat the redirect as a strong signal to consolidate indexing signals at the new URL. Redirects should point directly to the closest equivalent destination.

Business relevance

301 redirects preserve user journeys and search equity during URL changes, migrations, renames, and content consolidation while reducing broken links.

Implementation example

When a glossary term is renamed, the former URL returns a 301 directly to the new canonical term page and the sitemap and internal links are updated.

Limitations and common misconceptions

Long chains, loops, irrelevant destinations, soft redirects, and conflicting canonical signals can delay crawling or cause unexpected indexing. A 301 does not repair poor migration planning automatically.

Sujets

Sources