A 301 redirect permanently moves one URL to another. Bryan Collins explains what 301 redirects do, when to use them, and how they affect SEO rankings.
A 301 redirect is a permanent redirect that tells both browsers and search engines that a URL has permanently moved to a new location. It’s one of the most critical technical SEO tools for managing URL changes without losing rankings.
After 30 years in SEO, 301 redirects are among the most consequential and most frequently misimplemented technical elements I see. Here’s everything you need to know.
What the “301” Means
HTTP status codes are standardized responses that web servers send when a browser or crawler requests a URL. The 301 code specifically means “Moved Permanently.”
When a browser or Googlebot requests a URL with a 301 redirect, the server responds with:
- Status code 301
- A new “Location” header pointing to the destination URL
Both the browser and Google automatically follow this to the new URL. Google also:
- Updates its index to replace the old URL with the new one
- Transfers the ranking signals (PageRank/link equity) of the old URL to the new URL
301 vs. 302: The Critical Difference
| 301 | 302 | |
|---|---|---|
| Meaning | Moved Permanently | Found (Temporary Move) |
| Google behavior | Update index to new URL | Keep old URL in index |
| Link equity transfer | Yes | Not guaranteed |
| Use case | Permanent URL changes | Genuinely temporary redirects |
The most common mistake: Using 302 (temporary) when 301 (permanent) is intended. When Google sees a 302, it maintains the old URL in its index and may not transfer link equity because it expects the original URL to return.
Rule of thumb: Unless a page is genuinely coming back (maintenance, A/B test, regional redirect that varies by user), use 301.
When to Use 301 Redirects
Changing URL Structure
If you change a page’s URL — moving from /old-page-name/ to /better-page-name/ — a 301 redirect preserves any backlinks and ranking signals built on the old URL.
Without the 301, anyone visiting the old URL gets a 404 error, and any links pointing to the old URL no longer benefit your site.
HTTP to HTTPS Migration
When adding an SSL certificate and moving from http:// to https://, 301 redirects from every HTTP URL to the HTTPS version preserve ranking signals. This is typically implemented at the server level as a blanket redirect.
www to Non-www (or Vice Versa)
Your site should canonically serve from one version — www.example.com or example.com — with 301 redirects from the other. Without this, both versions exist as separate sites splitting link equity.
Page Consolidation
When merging two pages (e.g., two thin content pages combined into one comprehensive page), 301 redirect the page being eliminated to the surviving page.
Deleting a Page
When permanently removing a page, don’t leave users with a 404 error. If there’s a relevant alternative, 301 redirect to it. If no close alternative exists, redirect to the parent category page or homepage.
Full Site Migration
When redesigning a website with new URL structure, every changed URL needs a 301 redirect from the old URL to the corresponding new URL. This is one of the most important technical steps in a site migration — missing redirects during a migration can cause significant ranking losses.
How 301 Redirects Affect SEO
Link Equity Transfer
External backlinks pointing to the old URL pass their authority to the new URL through the 301. Google has confirmed that 301 redirects pass full link equity (previously there was a small loss, but Google updated this position). For practical purposes, treat 301 redirects as passing full link equity.
Index Update Timeline
After a 301 redirect is in place, Google will update its index from the old URL to the new URL on its next crawl. This typically takes days to weeks. You can accelerate this by submitting the new URL to Google Search Console’s URL Inspection tool.
Ranking Transfer
Rankings that existed on the old URL typically transfer to the new URL through the 301, though there may be a temporary fluctuation during the index update period.
Redirect Chains: The Silent Ranking Problem
A redirect chain occurs when multiple hops are needed to reach the final URL:
/page-a → 301 → /page-b → 301 → /page-c
This creates two problems:
- Crawl budget waste: Google follows each hop, consuming crawl budget
- Potential link equity loss: While each individual hop passes full equity, long chains may reduce the signal that ultimately reaches the final URL
Best practice: Always redirect directly to the final destination:
/page-a → 301 → /page-c (skip /page-b)
I use Screaming Frog to detect and flatten all redirect chains after every site migration I work on. Any chain of two or more hops should be collapsed into a single direct redirect.
Redirect Loops: The Critical Error
A redirect loop occurs when URLs redirect to each other in a circle:
/page-a → 301 → /page-b → 301 → /page-a
Browsers display “Too Many Redirects” errors. Google gives up and doesn’t index either URL. Loops are catastrophic — detect and fix them immediately.
How to Implement 301 Redirects
WordPress: The free Redirection plugin provides a UI-based interface for managing redirects without touching server files. It also logs 404 errors, helping identify which broken URLs need redirects.
.htaccess (Apache servers):
Redirect 301 /old-url/ https://example.com/new-url/
nginx configuration:
return 301 https://example.com$request_uri;
Cloudflare Rules: For sites using Cloudflare, redirect rules can be configured in the dashboard without server access.
CMS platforms: Shopify, Squarespace, and Webflow all have built-in redirect managers.
Checking for Redirect Issues
Screaming Frog: Crawl your site and check the “Response Codes” tab for 301s. The “Redirect Chains” report specifically identifies chains that should be flattened.
Google Search Console: The Coverage report shows “Redirect error” for URLs with problematic redirects.
Manual testing: Enter a URL in your browser — the address bar shows the final URL after all redirects. For more detail, use the browser developer tools (Network tab) or curl to see the full redirect chain.
Frequently Asked Questions
What is a 301 redirect? A 301 redirect is a permanent redirect that tells browsers and search engines that a URL has permanently moved to a new location. The ‘301’ is the HTTP status code for ‘Moved Permanently.’ It passes the majority of the original URL’s link equity (ranking authority) to the destination URL and signals Google to update its index to the new URL.
What is the difference between a 301 and 302 redirect? A 301 redirect is permanent — it tells Google the move is final and to transfer ranking signals to the new URL. A 302 redirect is temporary — it tells Google the original URL will return and to maintain the original URL in its index. For SEO, always use 301 for permanent URL changes. Using 302 when 301 is intended can cause Google to not transfer link equity or update its index.
Do 301 redirects lose PageRank? Google has confirmed that 301 redirects pass ‘full’ PageRank — though historically there was some loss. Google’s current guidance (confirmed in 2016 and after) is that 301 and 302 redirects pass the same amount of link equity. However, redirect chains (A→B→C instead of A→C) do waste some crawl budget and should be flattened to single hops.
When should I use a 301 redirect? Use 301 redirects when: permanently changing a URL slug, moving from HTTP to HTTPS, merging two pages, redirecting www to non-www (or vice versa), consolidating duplicate content, deleting a page that should redirect visitors somewhere relevant, and during a full site migration when all URLs are changing.
What is a redirect chain? A redirect chain occurs when multiple redirects are chained together — URL A redirects to URL B, which redirects to URL C. Chains waste crawl budget (Google follows each hop) and may dilute link equity. Best practice is single-hop redirects: URL A redirects directly to the final URL C, skipping the intermediate step.
How do I implement a 301 redirect? The method depends on your platform: WordPress with Redirection plugin (free, UI-based), .htaccess file edits (Apache servers), nginx configuration (nginx servers), Cloudflare Rules (if using Cloudflare), or your CMS’s built-in redirect manager (Shopify, Squarespace, Webflow all have redirect tools). Always test redirects after implementation using a browser or curl.
How do I check for redirect issues on my site? Screaming Frog crawl detects all redirect chains, redirect loops, and broken redirects. Google Search Console Coverage report shows redirect errors. Ahrefs and Semrush site audits flag redirect issues. For manual checking, enter a URL in your browser — the final URL in the address bar shows where the redirect leads.
Bryan Collins is an SEO consultant based in Piscataway, NJ, with 30+ years of experience helping small businesses grow through content and search. He is a U.S. Marine Corps veteran and the author of Why Your Website Isn’t Ringing.