What is 301 Redirect?
A 301 redirect is a permanent server-side redirect that sends users and search engines from an old URL to a new one — transferring the majority of the original page's link equity and ranking signals to the destination URL.
Why It Matters
URLs change. Sites migrate. Products get discontinued. Pages get reorganised. Every time a URL changes, the old URL still has value — backlinks pointing to it, bookmarks, search engine rankings, and indexed pages. Without a 301 redirect, that value disappears. The old URL returns a 404 error, the backlinks point nowhere, and the rankings vanish. A 301 redirect preserves that value by telling search engines the page has permanently moved and to transfer its authority to the new location.
For site migrations — domain changes, platform moves, URL restructures — 301 redirects are the most critical technical SEO element. A migration without proper redirects can destroy years of accumulated authority in a single deployment.
How It Works
301 redirects operate at the server level:
- Server configuration — Redirects are typically implemented in the web server configuration (Apache .htaccess, Nginx conf, Cloudflare rules) or in the CMS (WordPress, Shopify). When a browser or search engine requests the old URL, the server responds with a 301 status code and the new URL.
- Equity transfer — Google passes the majority of PageRank and ranking signals through 301 redirects. The destination page inherits the authority of the redirected page, though some minor dilution occurs. This transfer is permanent — Google eventually drops the old URL from its index entirely.
- Crawl handling — When Googlebot encounters a 301, it follows the redirect to the new URL, indexes the destination, and over time removes the old URL from the index. Multiple redirects in a chain (A→B→C) are followed but waste crawl budget and dilute equity further.
Common Mistakes
Creating redirect chains instead of direct redirects. When page A redirects to B, and later B redirects to C, the chain (A→B→C) loses equity at each hop and wastes crawl budget. Every redirect should point directly to the final destination URL, even if that means updating old redirects when URLs change again.
The other mistake is using 302 (temporary) redirects when a 301 (permanent) is appropriate. A 302 tells Google the move is temporary and the old URL should remain in the index. If the move is permanent — which it almost always is — a 301 ensures Google transfers authority and updates its index. Many CMS platforms default to 302 redirects, causing agencies to lose equity without realising it.
How I Use This
My SEO automation monitors redirect health as part of ongoing technical SEO. The automated audits detect redirect chains, redirect loops, 302s that should be 301s, and orphaned redirects pointing to pages that no longer exist. For site migrations, my advanced SEO audit includes full redirect mapping — matching every old URL to its correct destination before the migration goes live.
Related Services
How BrightIQ uses 301 Redirect
This concept is central to the following services:
Related Terms
Crawl Budget
Crawl budget is the number of pages a search engine will crawl on your site within a given timeframe — determined by your server's capacity and the perceived value of your content. Managing crawl budget ensures Google spends its limited crawling resources on the pages that matter.
SEO QA Automation
SEO QA automation uses automated checks to catch SEO issues — broken links, missing meta tags, schema errors, redirect chains, indexation problems — before they reach production, acting as a quality gate that runs on every deployment or on a scheduled basis.
Technical SEO
Technical SEO is the foundation layer of search engine optimisation — the crawlability, indexability, site speed, and structural elements that determine whether search engines can find, understand, and rank your pages.