What Is a 301 Redirect and When Should You Use One?
301 redirects are the most important technical SEO tool for managing URL changes — but using the wrong type or setting them up incorrectly can destroy your rankings. This guide covers everything you need to know.
By Josh Ternyak
March 29, 2026
The Bridge That Preserves Your SEO When URLs Change
URLs are supposed to be permanent. That's the philosophical ideal behind web addresses — a URL should identify a specific resource reliably and persistently, like a unique ID rather than a temporary label. In practice, URLs change all the time: pages get reorganized, sites get rebuilt, businesses rebrand, content gets merged.
When a URL changes, two things are at risk: the visitors who've bookmarked or linked to the old URL, who will get a 404 error instead of what they expected, and the SEO equity — the rankings and link authority — accumulated by the old URL, which doesn't automatically transfer to the new one.
A 301 redirect solves both problems simultaneously. It automatically sends visitors from the old URL to the new one (so nobody hits a 404) and tells search engines that the old URL has permanently moved to the new one (so the new URL inherits the old URL's ranking equity). Done correctly, a 301 redirect transfers both traffic and SEO value from old to new as if the URL had never changed.
What a Redirect Is
An HTTP redirect is a server response that tells a browser (or search engine) that the requested URL has moved, and provides a new URL to visit instead. When a browser requests a redirected URL, the server responds with a 3xx HTTP status code and a Location header pointing to the new URL. The browser automatically follows the redirect and loads the new URL. The entire process is typically invisible to the user.
The number in the status code indicates the type of redirect and what browsers and search engines should do with it:
301 Moved Permanently: The URL has permanently moved to the new location. Search engines should transfer full ranking equity to the new URL and update their index to reflect the new URL as canonical. This is the most SEO-significant redirect type.
302 Found (Moved Temporarily): The URL has temporarily moved. Search engines should keep the old URL in their index and not fully transfer equity to the new destination, because the move is temporary and the old URL may resume serving the original content. Use cases: A/B testing (temporarily serving a different page to some users), maintenance pages (temporarily redirecting to a "we'll be back soon" page), seasonal promotions (temporarily redirecting a product page to a seasonal variant).
307 Temporary Redirect: Similar to 302 but with a specific technical constraint: the HTTP method (GET, POST) must be preserved. For practical website purposes, 307 and 302 are functionally similar.
308 Permanent Redirect: Like 301 but preserves HTTP method. Rarely needed for typical website URL management.
Meta refresh: An HTML-based redirect that appears in the page's <head>: <meta http-equiv="refresh" content="0;URL='new-url.html'">. Not a server-level redirect — it requires the browser to load the original page before executing the redirect. Slower, passes less SEO equity than a 301, and generally considered bad practice for anything but emergency redirects when server-level redirects aren't available.
The 301 Redirect and SEO Equity
The SEO dimension of 301 redirects is why they matter so much in technical SEO. A page with organic rankings and backlinks has accumulated value — its position in Google's index, the PageRank flowing through links pointing to it. When that page's URL changes, that value needs to follow.
Google has confirmed that 301 redirects transfer the vast majority of link equity from the old URL to the new one. The exact percentage has varied over Google's official statements over the years — it used to be "some" equity was lost, more recently Gary Illyes of Google stated that 301 redirects pass essentially all link equity. For practical purposes, a properly implemented 301 redirect transfers ranking equity as effectively as a permanent URL would have maintained it.
This transfer isn't instant — Google needs to recrawl the old URL, process the redirect, update its index to reflect the new URL, and reassign the equity. This process typically takes several days to weeks depending on how frequently Google was crawling the old URL and how competitive the keywords are. During this transition period, some fluctuation in rankings is normal.
The contrast with no redirect: a URL that simply disappears (returns 404) loses all its equity immediately and permanently. Any incoming links now point to a dead page. Any rankings the page held are gone. If the content has been recreated at a new URL, that new URL starts from zero authority — it must rebuild organic equity from scratch.
When to Use a 301 Redirect
Site Redesign or Rebuild
The most common scenario for large-scale 301 redirect implementation. When rebuilding a site — new CMS, new design, new URL structure — every URL that changes needs a 301 redirect from its old location to its new equivalent.
This is non-optional for any site with meaningful organic traffic. Skipping redirects during a site rebuild is the fastest way to destroy years of accumulated SEO equity. Within weeks of launching a rebuilt site without redirects, organic traffic can drop 30–70% as Google discovers that previously-indexed URLs now return 404 errors.
Domain Change or Rebranding
Moving from one domain to another — whether for rebranding, acquiring a better domain, or consolidating multiple domains — requires 301 redirects from every old URL to its new domain equivalent. This is a domain migration and represents the highest-risk redirect scenario because every URL on the site is simultaneously changing.
Domain migrations should be implemented with Google's Change of Address tool in Search Console alongside the redirect implementation, to formally notify Google of the domain change and accelerate equity transfer.
HTTPS Migration
Moving from HTTP to HTTPS: all HTTP URLs should 301 redirect to their HTTPS equivalent. This includes: redirecting example.com to https://example.com, and typically also consolidating www and non-www into the canonical version.
A complete HTTPS migration redirect setup:
- http://example.com → https://example.com
- http://www.example.com → https://example.com
- https://www.example.com → https://example.com
All non-canonical versions (HTTP, www when non-www is canonical) redirect to the canonical HTTPS version in a single hop — not through a chain of redirects.
URL Structure Changes
Changing URL slugs, reorganizing content hierarchy, adding or removing category prefixes — any URL structure change that affects pages with organic traffic or backlinks needs 301 redirects from old to new.
Example: Moving blog posts from /blog/post-title to /resources/post-title requires a 301 from /blog/post-title to /resources/post-title for every post. This preserves the organic rankings and backlink equity each post has accumulated under the /blog/ URL structure.
Deleting Pages with Backlinks or Traffic
When removing a page from the site, the right destination for a 301 redirect depends on the relationship to other content:
- Page merged into another page: 301 to the page it was merged into
- Page removed with a relevant equivalent: 301 to the closest thematically relevant page
- Page removed with no direct equivalent: 301 to the parent category or the homepage
- Page with no backlinks and no organic traffic: 404 is acceptable
The goal is to redirect equity somewhere useful rather than letting it dissipate into a 404. A 301 to the homepage is better than a 404 for a page with valuable backlinks, even if the thematic match is weak.
Canonicalizing www and non-www
Your site should be accessible at one canonical URL format — either www.example.com or example.com — not both. Whichever you choose as canonical should be the one in your Google Search Console property, your sitemap, and your canonical tags. The non-canonical version should 301 redirect to the canonical one.
This is simple, important, and frequently neglected. Both www and non-www versions of a site accessible without redirects creates potential duplicate content issues.
Redirect Chains: The Performance and SEO Problem
A redirect chain occurs when a URL redirects to another URL that itself redirects to a final destination: Old URL → Intermediate URL → Final URL.
Redirect chains are problematic for two reasons:
Performance: Each hop in a redirect chain adds an HTTP round trip — typically 100–300ms per hop. A single redirect adds modest latency. Multiple redirects chain into meaningful load time overhead. Users and browsers experience this as slow page loads.
SEO: Google's documentation suggests that long redirect chains may dissipate some link equity with each hop. More practically, Googlebot's crawl budget is consumed by following chains, and very long chains may cause Googlebot to stop following before reaching the final destination.
Detect redirect chains by running your site through Screaming Frog or checking specific redirects with a redirect checker tool (httpstatus.io). When you find chains (A → B → C), update A to redirect directly to C, bypassing B. Internal links that point to A should also be updated to point to C when possible.
Redirect Loops: The Crawl Killer
A redirect loop occurs when URL A redirects to URL B, and URL B redirects back to URL A — creating an infinite loop. Browsers detect this after a few hops and show an "ERR_TOO_MANY_REDIRECTS" error. Search engines can't index the content at either URL.
Common causes: incorrectly configured HTTPS redirects (http redirects to https, which redirects back to http), www/non-www redirect mistakes, and errors in redirect rules that create circular references.
Check for loops by opening the redirect-affected URL in a browser and watching for "ERR_TOO_MANY_REDIRECTS." Use an online redirect checker that shows each hop in a chain to identify where the loop occurs.
How to Implement 301 Redirects
Server Configuration (Apache)
Apache servers use .htaccess files for redirect rules. Single URL redirect:
Redirect 301 /old-page https://example.com/new-pagePattern-based redirect (moving all /blog/ URLs to /resources/):
RewriteEngine on
RewriteRule ^blog/(.*)$ /resources/$1 [R=301,L]Server Configuration (Nginx)
location /old-page {
return 301 https://example.com/new-page;
}WordPress Plugins
Yoast SEO Premium and Rank Math (free) include redirect management interfaces. Redirection (free WordPress plugin) is specifically designed for managing redirects — it provides a user interface for adding, editing, and monitoring redirects without touching server configuration files. Appropriate for WordPress site managers who aren't comfortable editing .htaccess.
Platform-Specific Settings
Most website builders have redirect management in their settings:
Webflow: Project Settings → Publishing → 301 Redirects. Provides a user interface for adding source → destination URL pairs. Applied automatically at the edge (Fastly CDN level) without server configuration.
Shopify: Online Store → Navigation → URL Redirects.
Squarespace: Settings → Advanced → URL Mappings.
For migrations from these platforms, set up redirects in the platform's redirect settings before launching the new URL structure.
Validating Your Redirects
After implementing redirects, verify they work correctly:
Browser check: Navigate to the old URL and verify you reach the correct new URL. Check the browser's address bar to confirm the final URL is correct.
DevTools network check: In Chrome DevTools (F12 → Network tab), load the old URL and inspect the network requests. The first request should show a 301 status code with a Location header pointing to the new URL.
Bulk redirect checking: For large redirect maps, use a tool like Screaming Frog (Redirect Checker mode) or httpstatus.io's bulk checker to verify hundreds of redirects efficiently.
Google Search Console URL Inspection: After redirects are live and Google has recrawled, use URL Inspection on old URLs to verify Google has processed the redirect and is recognizing the new canonical URL.
The Bottom Line
301 redirects are the technical mechanism that preserves SEO equity and user experience when URLs change permanently. Use them for: page restructuring, domain migrations, HTTPS transitions, page deletions with equity worth preserving, and canonical www/non-www consolidation. Avoid redirect chains (update to single-hop redirects). Monitor for redirect loops. Validate every redirect before considering a migration complete.
The businesses that maintain organic traffic through site rebuilds are the ones that treat redirect implementation as non-negotiable technical work, not optional cleanup. The businesses that lose traffic after site rebuilds are the ones that treated it as something to "figure out later" — which typically means after significant ranking loss.
At Scalify, redirect mapping and implementation is a standard part of every site rebuild — protecting the organic equity you've earned is as important as delivering the new site on time.
78 SW 7th St, Miami, FL 33130
