What is a 301 Redirect in SEO?
7 min read
A 301 redirect (formally 301 Moved Permanently in IETF RFC 9110, Section 15.4.2) is an HTTP redirection status code indicating that the requested resource has been permanently assigned a new target URI specified in the response Location header. In technical SEO, a 301 redirect acts as Google’s strongest server-side canonicalization signal: it instructs search crawlers to de-index the legacy URL, index the destination URL, and consolidate 100% of historical link equity (PageRank) and ranking signals at the new address.
What is a 301 Redirect? (Technical Definition & HTTP Location Header)
When a browser, AI scraper, or search engine crawler (Googlebot) requests a URL that has been permanently moved, the web server responds with an HTTP 301 status code accompanied by a Location response header:
Raw HTTP 301 Response Header Example
HTTP/2 301 Moved Permanently
location: https://b2bsaasseo.agency/saas-link-building
cache-control: public, max-age=31536000
Upon reading the Location header, the client immediately initiates a second HTTP request to the new destination URL. Unlike client-side meta refresh redirects or JavaScript window.location redirects (which require downloading and rendering the HTML DOM first), an HTTP 301 executes at the server or edge CDN layer (configured via Apache/LiteSpeed .htaccess, Nginx server blocks, or Cloudflare Edge Rules).
Do 301 Redirects Lose PageRank? (The Verified Fact vs. Outdated Myth)
One of the most common misconceptions in SEO is that a 301 redirect loses 10% to 15% of its PageRank. Here is the verified chronological record:
- Pre-2016 Era (The 15% Decay Rule): In the early 2010s, Matt Cutts (then head of Google’s Webspam team) stated that a 301 redirect lost roughly the same amount of PageRank as a standard link (around 10% to 15% due to the original PageRank damping factor).
- Post-July 2016 Official Update (Zero PageRank Loss): In July 2016, Google Search Analyst Gary Illyes officially confirmed on the record that 301, 302, and all 3xx redirects no longer lose any PageRank at all.
- The Relevance Caveat (Why Traffic Can Still Drop): While the mathematical PageRank score transfers without decay, Google’s John Mueller has clarified that if you redirect a specific deep topic page to a generic page (such as redirecting an old feature guide to your root homepage), the destination page does not match the original search intent or anchor text context. In those cases, Google treats the irrelevant 301 as a Soft 404 and drops the ranking signals.
301 vs. 308 vs. 302 vs. 307: Complete Redirection Matrix
Modern web frameworks (such as Next.js and Vercel) and HTTP/2+ servers utilize four distinct 3xx redirect codes. Choosing the right one is critical for both SEO canonicalization and application behavior:
| Status Code | Persistence | HTTP Method Handling (POST/GET) | Google Canonical & SEO Action |
|---|---|---|---|
| 301 Moved Permanently | Permanent | May change POST requests to GET on redirect. |
Strongest signal to index target URL and transfer full link equity. |
| 308 Permanent Redirect | Permanent (RFC 9110) | Strictly preserves HTTP method (POST stays POST). |
Treated identically to 301 by Googlebot; transfers full PageRank. |
| 302 Found | Temporary | May change POST to GET historically. |
Weak signal; keeps original URL indexed in the short term. |
| 307 Temporary Redirect | Temporary (RFC 9110) | Strictly preserves HTTP method (POST stays POST). |
Treated identically to 302 by Googlebot; keeps original URL indexed. |
| rel="canonical" | HTML / HTTP Hint | Not a redirect; both URLs return 200 OK. | Consolidates duplicate signals when both URLs must remain accessible. |
Redirect Chains, Loops & Googlebot’s 10-Hop Limit
Even though a single 301 redirect preserves PageRank, poorly maintained redirect rules degrade technical performance:
- Googlebot’s 10-Hop Ceiling: According to official Google Search Central documentation ("Redirects and Google Search"), Googlebot follows a maximum of 10 redirect hops in a chain (typically 5 hops in a single crawl pass before deferring the rest). If a chain exceeds 10 hops, Googlebot aborts the request and logs a Redirect error in Google Search Console.
- Latency & Core Web Vitals Penalty: Every redirect hop adds DNS, TCP, TLS, and server round-trip latency (often 100ms to 400ms per hop), directly degrading Time to First Byte (TTFB) and Largest Contentful Paint (LCP) in Core Web Vitals.
- Internal Link Dilution: Linking internally to URLs that 301 redirect forces both users and crawlers through unnecessary hops. Always update internal links to point directly to the final 200 OK destination.
Enterprise B2B SaaS 301 Migration Playbook
Zero-Loss SaaS Domain & URL Migration Checklist
1. Build a Strict 1-to-1 Semantic Mapping Matrix: Before launching a domain migration or CMS overhaul, export all historical URLs from Google Search Console, Ahrefs (backlink targets), and server logs. Map every legacy URL to its exact semantic counterpart, never to the root homepage.
2. Flatten All Legacy Redirect Chains (A → C): If /v1/pricing redirected to /v2/pricing in 2024, and you are launching /pricing-plans today, rewrite both /v1/pricing and /v2/pricing to point directly to /pricing-plans in a single hop.
3. Update Sitemaps, Canonicals & Internal Links: Purge all 301-redirecting URLs from your XML sitemaps and ensure self-referencing canonical tags point exclusively to the new destination URLs.
4. Maintain 301 Rules for at Least 12 Months: Google’s John Mueller recommends keeping 301 redirects live for a minimum of one full year so Googlebot can recrawl every legacy URL multiple times. For URLs with high-authority external backlinks, keep the 301 rules active indefinitely.
Frequently Asked Questions
Do 301 redirects pass 100% of PageRank?
Yes. In July 2016, Google confirmed that 301 redirects pass 100% of PageRank without the historical 15% damping loss, provided the destination page is topically relevant and satisfies the same search intent as the original URL.
What is the difference between a 301 redirect and a 308 redirect for SEO?
Both 301 and 308 are permanent redirects, and Google treats them identically for indexing and PageRank transfer. The only technical difference is that HTTP 308 (defined in RFC 9110) strictly forbids the browser from changing the request method from POST to GET.
How many 301 redirect hops will Googlebot follow in a chain?
According to Google Search Central documentation, Googlebot will follow up to 10 redirect hops before aborting and reporting a Redirect Error in Search Console. However, best practice is to flatten all chains to a single 1-hop redirect.
How long must I keep 301 redirects active after a website migration?
Google officially recommends maintaining 301 redirects for at least 1 year after a site move so crawlers can process every legacy URL. If third-party websites still link to the old URLs, you should keep those 301 redirects active permanently.