What Is a 301 Redirect? Definition and Why It Matters
A 301 is a permanent forwarding address for a URL. Done right, backlinks pointing at the old address keep working for the new one.
A 301 redirect is an HTTP status code and response telling browsers and search engines that a page has moved permanently to a new URL. Visitors are sent there automatically and without noticing; search engines update their index over subsequent crawls to treat the new URL as the one that matters.
When to use a 301
- A page has genuinely moved to a new URL and isn’t coming back at the old one.
- You’ve merged several thin or overlapping pages into a single, stronger one (refreshing old content).
- You’ve changed domain, renamed a section, or moved the whole site to HTTPS.
- An old URL that has accumulated backlinks now returns a 404 and you want to recover that value (reclaiming 404 links).
How link value moves through a redirect
A 301 redirect is generally treated as passing the bulk of the old URL’s link signals to its destination. This is precisely why redirecting an old URL with existing backlinks — rather than simply deleting the page — recovers most of the value those links represent instead of losing it. It’s one of the most reliable ways to consolidate authority when restructuring a site that already has an established backlink profile.
Mistakes that waste this value
- Redirect chains — A redirects to B, which redirects to C. Every extra hop adds latency and risk that the value passed is less efficient than a direct redirect (redirect chains).
- Irrelevant redirects — sending every dead URL to the homepage instead of the closest relevant replacement page, which wastes the specificity of the original link’s context.
- Using a 302 (temporary redirect) for what is actually a permanent move, which can leave search engines treating the original URL as still the canonical one.
- Forgetting to update internal links to point directly at the new URL, leaving your own site relying on the redirect indefinitely.
A worked example
Say an older blog post earned a handful of backlinks over several years and is now being merged into a newer, more comprehensive guide covering the same topic. Instead of deleting the old post and letting those backlinks point at a 404, a 301 redirect from the old URL straight to the new guide preserves the relevance and value those links represent, while giving readers and search engines a single, stronger destination. Redirecting instead to the site’s homepage would technically resolve the 404, but it would waste the topical specificity the original backlinks were pointing at.
301 vs other redirect types
| Type | Meaning | Use case |
|---|---|---|
| 301 | Permanent move | Page merged, moved, or retired for good |
| 302 | Temporary move | A/B tests, short-term maintenance |
| Meta refresh | Client-side, delayed redirect | Rarely recommended for SEO purposes |
Related terms
Redirect chain, link equity, orphan pages.
Redirects during a full site migration
Large migrations — a rebrand, a platform change, a domain move — deserve a full redirect map created before the old site goes offline, matching every meaningful old URL to its closest new equivalent. Skipping this step and redirecting everything to the homepage is one of the most common causes of a sudden, unexplained traffic and ranking drop after a migration, because it wastes the specificity that search engines and existing backlinks relied on.
Testing redirects before and after launch
Always test a sample of your most important old URLs, including ones known to carry backlinks, immediately after implementing redirects, and again a few weeks later. It’s common for a redirect rule to work for most URLs but miss an edge case — a trailing slash variant, an uppercase path — that only becomes obvious once you check systematically rather than spot-checking a handful of pages.
Bulk redirects at scale
On sites with thousands of URLs changing at once, manage redirects as a structured, version-controlled mapping file rather than ad hoc rules added over time, so the full set can be reviewed, tested and rolled back if something goes wrong. This discipline matters far more as scale increases, since a handful of mistakes in a redirect map covering ten thousand URLs is far harder to spot manually than the same error rate on a site with only a few dozen pages.
Communicating redirects to stakeholders
On larger teams, a URL change often touches marketing, content and development simultaneously, and a redirect implemented correctly on the server side can still cause confusion if internal links in emails, presentations or bookmarks still point at the old address. Circulating the redirect map internally, not just implementing it technically, avoids weeks of confused reports about “broken” links that are, technically, working exactly as intended.
Where to go next
Before buying new placements, make sure your existing backlinks aren’t quietly pointing at dead URLs — see monitoring lost backlinks — and browse the marketplace for fresh placements once your redirect hygiene is solid.
Browse every term in the link building glossary.
Frequently asked questions
Do 301 redirects lose link value?
Search engines generally treat 301s as passing the bulk of a URL's signals to the destination; the bigger risks are chains and irrelevant redirect targets.
How long should I keep a 301 in place?
Ideally permanently, especially if the old URL is known to have backlinks pointing at it.
Should I redirect to the closest relevant page or the homepage?
Always the closest relevant replacement. Redirecting everything to the homepage wastes the topical relevance of the original backlinks.
Is a 301 enough on its own, or do I need to update internal links too?
Update internal links as well. Relying on the redirect indefinitely adds unnecessary hops and slows crawling.
Put it into practice
Filter 54,483 websites by DR, traffic, niche and price, and order with escrow — you pay only after the link is live.
Browse the marketplace
