A 301 redirect is one of the most powerful tools I have for protecting a site's rankings, and also one of the easiest to get wrong. Used well, a 301 redirect quietly moves both visitors and search engines from an old URL to a new one while carrying the ranking signals across. Used carelessly, it can bleed away traffic you spent years earning. In this guide I will show you exactly what a 301 redirect is, when to use one, and how to implement redirects without losing rankings in 2026.
I have run these redirects during dozens of site migrations, domain moves, and content consolidations. The pattern is always the same: the technical setup is simple, but the decisions around it (which URL points where, whether a 301 is even the right choice, how to catch chains and loops) are where sites win or lose. So this is less a "here is the code" post and more a "here is how to think about it" playbook, with the code included.
By the end you will understand how link equity flows through a redirect, how a 301 differs from a 302 or a canonical tag, and how to monitor the whole thing in Google Search Console so a broken redirect never silently costs you money.
What Is a 301 Redirect?
A 301 redirect is a server response that tells a browser and a search engine "this page has permanently moved to a new address." The "301" is an HTTP status code, and the word that matters is permanent. When Google sees a 301, it eventually drops the old URL from its index, indexes the destination instead, and passes the old page's ranking signals forward.
Think of it like a change-of-address form with the post office. Someone sends mail to your old house, and it gets forwarded automatically to your new one. Visitors never see a dead page, and the "reputation" the old URL built (its backlinks, its history, its authority) follows it to the new location. That forwarding of authority is the entire reason 301 redirects matter for SEO rather than just user experience.
301 vs 302 and Other Redirect Status Codes
Not every redirect is a 301, and choosing the wrong one is a common way to lose rankings by accident. The status code you return tells search engines whether the move is permanent or temporary, and that changes how they treat your indexing. Google's own documentation is explicit that a permanent redirect should return a 301 or 308 status. Here is how the main options compare.
Redirect Status Codes at a Glance
| Code | Meaning | Passes ranking signals? | Use it for |
|---|---|---|---|
| 301 | Moved permanently | Yes | Permanent URL changes, migrations, consolidation |
| 302 | Found (temporary) | Yes, but old URL stays indexed | Short-term detours, A/B tests, temporary offers |
| 307 | Temporary redirect | Same as 302, method preserved | Temporary moves that must keep the request method |
| 308 | Permanent redirect | Yes | Permanent moves that must keep the request method |
| Meta refresh | Client-side delay redirect | Weak, slow, avoid | Almost never for SEO |
The practical rule I follow: if the change is permanent, use a 301. If it is genuinely temporary and you want to keep the original URL in the index, use a 302. Do not reach for a 302 out of caution "just in case," because leaving a permanent move on a 302 keeps the old URL competing with the new one and slows consolidation.
When Do You Need a 301 Redirect?
A 301 is the right call any time a URL will never come back at its old address but the content still exists somewhere. In my client work, the same handful of scenarios come up again and again.
Common Situations That Call for a 301
- Changing a URL slug: You improve a messy URL, so the old one must forward to the clean one.
- Consolidating duplicate or thin pages: Two overlapping posts merge into one stronger page and the weaker URL redirects in.
- Switching domains: A rebrand or a move from a subdomain to a main domain needs every old URL mapped to its new home.
- Moving to HTTPS or a www/non-www version: All variants should funnel to one canonical protocol and host.
- Deleting a page that has value: If a retired page earned links or traffic, redirect it to the closest relevant page instead of returning a 404.
- Fixing trailing-slash or case inconsistencies: Pick one format and redirect the rest to it.
One caution: do not redirect a deleted page to your homepage as a lazy catch-all. Google treats an irrelevant redirect as a soft 404 and may not pass any value. Always send a retired URL to the most topically similar live page, which is also part of good technical SEO hygiene.
301 Redirect vs Canonical vs Noindex: Which to Use
A 301 is not the only way to tell Google which URL matters. Canonical tags and noindex directives solve related but different problems, and I see people reach for the wrong one constantly. Here is how I decide between them.
Choosing the Right Signal
| Tool | What it does | Users still reach the page? | Best when |
|---|---|---|---|
| 301 redirect | Permanently forwards to another URL | No, they land on the new URL | The old page should no longer exist |
| Canonical tag | Suggests a preferred version of near-duplicates | Yes, both stay live | Similar pages must both remain accessible |
| Noindex | Keeps a page out of search results | Yes | A live page you do not want ranked |
The quick heuristic: if the page needs to disappear, use a 301. If two similar pages both need to stay live (filtered product views, print versions, tracking parameters), use a canonical, which I cover in depth in my guide to canonical tags. If a real page simply should not appear in search, use noindex. Mixing these up, such as putting a canonical on a page you also redirect, sends conflicting signals.
How 301 Redirects Pass Link Equity
The reason redirects preserve rankings is that a 301 passes the vast majority of the original page's link equity (sometimes called "link juice") to the destination. In practice this means the backlinks pointing at your old URL keep counting toward the new one, so the authority you earned is not thrown away.
For years there was a myth that redirects "leaked" a fixed percentage of PageRank. Google has since clarified that a 301 (or any permanent redirect) does not lose PageRank simply for being a redirect. What actually erodes value is relevance: redirecting to an unrelated page, or through a long chain of hops, weakens the signal. Keep redirects direct and relevant and the equity transfers cleanly.
This is also why redirects are central to recovering lost authority during restructures. When you consolidate several aging posts into one comprehensive resource, you are pooling their combined link equity into a single stronger URL, which often ranks better than any of the originals did alone.
How to Set Up a 301 Redirect (Step by Step)
Implementation depends on your stack, but the workflow is consistent. Here is the sequence I use so nothing slips through.
Map old URLs to new ones
Before touching a server, build a spreadsheet with two columns: source URL and destination URL. Every important old URL needs a one-to-one match to the most relevant live page. This map is the single most important artifact of the whole job.
Choose your redirect method
On Apache, add rules to .htaccess: Redirect 301 /old-page /new-page. On Nginx, use rewrite ^/old-page$ /new-page permanent; in the server block. On WordPress, a plugin such as Redirection or your SEO plugin handles it without editing config files, which suits most WordPress sites.
Handle CDN and platform-level redirects
If you run Cloudflare, Shopify, or a headless setup, redirects may live at the edge or in the platform settings rather than the origin server. Put them wherever they resolve first, so a request never hits the origin only to bounce again.
Test every redirect returns a 301
Use a crawler or a browser dev-tools Network tab to confirm each source returns a single 301 hop landing on a 200 destination, not a 302 or a chain. Verify a representative sample manually before you trust the batch.
Update internal links to point directly
Redirects are a safety net, not a permanent crutch. Update your on-site links, menus, and sitemaps to reference the new URLs directly so users and crawlers skip the hop entirely.
Redirect Chains, Loops, and How to Fix Them
A redirect chain happens when URL A redirects to B, which redirects to C. Each extra hop adds latency, wastes crawl budget, and slightly dilutes the signal. A redirect loop is worse: A points to B and B points back to A, so the page never loads at all and both users and crawlers get stuck.
These sneak in over time. You redirect a page this year, redirect its destination next year, and suddenly you have a three-hop chain nobody noticed. During audits I regularly find chains four or five hops deep on older sites.
How I Clean Up Chains and Loops
- Crawl the whole site: A tool like Screaming Frog flags every multi-hop redirect and loop in one report.
- Flatten to a single hop: Rewrite the original source to point straight at the final destination, removing the middle hops.
- Break loops immediately: A loop means a live page is unreachable, so treat it as an emergency, not a cleanup task.
- Recheck after edits: Fixing one rule can expose another chain, so re-crawl until the report is clean.
- Watch crawl budget: Excess hops eat into crawl budget on large sites, so flattening pays off directly.
Using 301 Redirects During a Site Migration
Migrations are where redirects earn their reputation, for better or worse. Whether you are moving domains, switching platforms, or restructuring your URLs, a complete and accurate redirect map is what keeps your rankings intact. This is the highest-stakes redirect work I do, and it deserves its own careful process, which I detail in my SEO website migration guide.
The single biggest migration mistake is redirecting everything to the homepage instead of mapping URL to equivalent URL. If your old /services/seo page had authority, it must land on the new services page, not a generic front door. Map first, launch second, and keep the old sitemap submitted for a while so Google can discover the redirects quickly. Handled this way, a migration rarely causes more than a short, recoverable dip.
Redirects also interact with crawling and indexing during a move. If pages are not getting picked up afterward, my checklist for fixing pages that are not indexed will help you diagnose whether a redirect, a canonical, or a robots rule is the culprit.
Monitoring Redirects in Google Search Console
Setting redirects and walking away is how sites quietly decay. I monitor them continuously, and Google Search Console is the free tool that makes it possible. The Page Indexing report will show a "Page with redirect" status for your source URLs, which confirms Google has seen the move.
The URL Inspection tool is my go-to for spot checks: paste an old URL and it tells you the redirect target and whether the destination is indexed. Pair that with your analytics to watch that the destination pages actually retain their traffic. Configuring this well is part of getting real value from Analytics and Search Console, and it is one of the first things I set up for any serious project.
Common 301 Redirect Mistakes to Avoid
Most redirect damage comes from a short list of avoidable errors. I have cleaned up every one of these on client sites, and catching them early is exactly the kind of detail that separates a good technical setup from a costly one. If you want a partner who sweats these details, working with the best SEO expert you can find is worth far more than any plugin.
The Mistakes That Cost Rankings
- Redirecting everything to the homepage: Irrelevant redirects become soft 404s and pass no value.
- Using 302s for permanent moves: Temporary codes keep the old URL indexed and stall consolidation.
- Leaving redirect chains in place: Every hop adds latency and slowly dilutes the signal.
- Forgetting to update internal links: Relying on redirects forever wastes crawl budget and slows pages.
- Redirecting to non-equivalent content: Sending a product URL to an unrelated page confuses users and Google alike.
- Not testing after launch: A single typo in a rule can 404 hundreds of URLs overnight.
Frequently Asked Questions About 301 Redirects
Do 301 redirects hurt SEO?
No, a correctly implemented 301 protects SEO by carrying ranking signals from the old URL to the new one. Problems only arise from irrelevant destinations, long chains, or using the wrong status code.
How long should I keep a 301 redirect in place?
Keep it as long as the old URL might still be requested or linked to, which in practice means indefinitely. Removing a redirect too soon turns the old URL into a 404 and discards the value you preserved.
How long does it take Google to process a 301?
Google usually recognizes a permanent redirect within days to a few weeks, depending on how often it crawls the URL. You can speed discovery by keeping the old URLs in your sitemap temporarily and requesting indexing on key pages.
Is a 301 redirect the same as a canonical tag?
No. A 301 removes the old page and forwards everyone to a new URL, while a canonical tag keeps both pages live and only suggests a preferred version to search engines.
Conclusion: Treat Redirects as a Living System
A 301 redirect is a small piece of server configuration with an outsized impact on your rankings. Get the mapping right, choose the correct status code, keep every redirect a single relevant hop, and update your internal links, and you can restructure or migrate a site without surrendering the authority you have built. The technical part takes minutes; the discipline around it is what protects your traffic.
If you are planning a migration, a rebrand, or a big content consolidation and you want your 301 redirects handled without a rankings dip, that is exactly the kind of work I do every week. Do the mapping carefully, monitor it in Search Console, and treat your redirects as a living system rather than a one-time task.
Planning a Migration or URL Change?
Let me build and QA your 301 redirect map so you move, rebrand, or consolidate without losing rankings or traffic. I handle the mapping, implementation, and Search Console monitoring end to end.
Book a Free Consultation