301 Redirect

A 301 Moved Permanently status code tells browsers and search engines that the original URL will never be used again. Unlike a 302 Found (temporary) redirect, a 301 instructs crawlers to index the target URL and transfer all ranking signals. Search engines eventually de-index the source URL entirely. Use 301s for permanent domain migrations, URL restructuring, or retiring legacy pages. Use 302s for A/B tests or temporary maintenance.

A 301 redirect passes approximately 90-99% of PageRank and other link-based authority signals from the source URL to the destination. This makes it the primary tool for consolidating backlink profiles when merging sites or migrating domains. Without a 301, inbound links pointing to the old URL contribute zero value to the new location. Note that redirects across different domains may experience slightly higher equity dilution than same-domain redirects.

301 redirects can be configured at multiple layers of the stack:

• Apache: Use Redirect 301 or RewriteRule in .htaccess
• Nginx: return 301 directive in server blocks
• Cloudflare: Page Rules or Bulk Redirects
• Application level: Framework-specific middleware (Express, Django, Rails)
• Edge functions: Workers or Lambda@Edge for dynamic logic Server-level redirects are preferred over client-side meta refresh or JavaScript redirects, which search engines may not reliably process.

A redirect chain occurs when URL A → URL B → URL C, requiring multiple hops to reach the final destination. Each hop:

• Wastes crawl budget as bots follow intermediate URLs
• Dilutes link equity incrementally at each step
• Increases latency for users Best practice is to maintain a one-to-one redirect map directly from the original URL to the final canonical. A redirect loop (A → B → A) causes browser errors and must be resolved immediately.

Search engines allocate a finite crawl budget per site—the number of URLs crawled within a given timeframe. 301 redirects consume this budget because bots must request the source URL before discovering the redirect. Excessive redirects on large sites can starve important pages of crawl attention. After processing a 301, search engines eventually remove the source URL from their index, replacing it with the destination. This process can take days to weeks depending on crawl frequency.

A 301 redirect works alongside other canonical signals to create a definitive URL preference. For maximum effectiveness, align these signals:

• 301 redirect points to the canonical URL
• rel=canonical tag on the destination self-references its own URL
• Internal links consistently point to the canonical version
• XML sitemap includes only the canonical URL Conflicting signals—such as a 301 to URL A but a canonical tag pointing to URL B—create ambiguity that search engines may resolve unpredictably.