A 301 redirect is one of the most important technical SEO tools available to website owners. When you move content, change URLs, or restructure your site, a 301 redirect ensures both visitors and search engines are sent to the correct destination — and that your hard-earned rankings and link equity transfer to the new URL. This guide explains what 301 redirects are, when to use them, and how to implement them without harming your SEO.
What Is a 301 Redirect?
A 301 redirect is an HTTP response code that tells browsers and search engine crawlers that a page has permanently moved to a new URL. The "301" refers to the HTTP status code returned when the server is requested for the old URL. When a redirect is in place, anyone visiting the old URL is automatically sent to the new one — they typically never see the old URL at all.
The word "permanent" is what distinguishes a 301 from other redirect types. It signals to search engines: this URL has moved forever, not temporarily. As a result, search engines transfer the indexing signals, PageRank, and link equity from the old URL to the new one over time.
301 redirects are used in the everyday management of websites — whenever URLs change, domains are migrated, HTTP is upgraded to HTTPS, or old content is merged or replaced. Handling these transitions with a 301 redirect preserves the SEO value accumulated by the original URL.
Redirect Types Compared
Several HTTP redirect codes exist, each with different SEO implications:
- 301 (Moved Permanently) — the standard redirect for permanent URL changes. Transfers full link equity to the destination. Use this for almost all SEO-relevant redirects.
- 302 (Found / Temporary Redirect) — signals a temporary move. Search engines do not transfer link equity and continue to index the original URL. Use only when the redirect is genuinely temporary (e.g., a promotional page visible for two weeks).
- 307 (Temporary Redirect) — HTTP/1.1 version of 302. Preserves the request method. Rarely needed for standard SEO purposes.
- 308 (Permanent Redirect) — HTTP/1.1 version of 301. Preserves the request method. Can be used instead of 301 for APIs; for standard web content, 301 is more universally understood.
- Meta refresh — a page-level redirect implemented in HTML rather than at the server level. Slower, less SEO-friendly, and generally avoided. Use server-side 301 redirects instead.
For SEO purposes, 301 is the correct choice in the vast majority of permanent URL-change scenarios.
When to Use a 301 Redirect
Use a 301 redirect in these common situations:
1. Changing a URL slug — if you rename a blog post from /blog/seo-tips-2024 to /blog/seo-tips-2026, the old URL must redirect to the new one. Any external links or bookmarks pointing to the old URL will continue to work, and Google will eventually update its index to point to the new URL.
2. Migrating to HTTPS — redirecting all HTTP URLs to their HTTPS equivalents is one of the most common uses of 301 redirects. A wildcard redirect in your server configuration sends every HTTP request to the HTTPS version automatically.
3. Consolidating www and non-www versions — your site should be accessible on only one version: either www.example.com or example.com. Redirect the non-canonical version to the canonical one. Both versions serving content creates a duplicate content issue.
4. Moving to a new domain — when migrating from an old domain to a new one, page-by-page 301 redirects from old URLs to their equivalent new URLs transfer accumulated link equity and help Google re-index your content under the new domain.
5. Deleting or merging pages — if you delete a page, redirect its URL to the most relevant surviving page (or your homepage as a last resort). If you merge two articles into one, redirect both old URLs to the new consolidated URL.
6. Fixing trailing slash inconsistencies — /about and /about/ are technically different URLs. Consistently redirect one to the other so search engines index only one version.
How 301 Redirects Affect SEO
When implemented correctly, 301 redirects transfer the majority of the SEO value from the old URL to the new one. Google has confirmed that 301 redirects pass PageRank (link equity) and that rankings generally transfer to the new URL — though this process may take several weeks as Google recrawls and re-indexes the URLs involved.
Key SEO considerations:
Link equity transfer — the consensus among SEO practitioners (supported by Google's own statements) is that 301 redirects pass close to 100% of link equity. Earlier beliefs that redirects caused significant PageRank loss are outdated. Implement 301 redirects without fear of substantial ranking loss.
Crawl budget impact — redirect chains (URL A to URL B to URL C) consume crawl budget and slow down equity transfer. Always redirect directly from the old URL to the final destination URL. Eliminate chains where possible.
Time to transfer — Google typically updates its index within a few weeks of encountering a 301 redirect. High-authority pages with frequent crawling update faster. Newly implemented redirects may temporarily show fluctuation in rankings — this usually stabilises within 4–8 weeks.
Redirect loops — a redirect loop occurs when URL A redirects to URL B, which redirects back to URL A. This prevents access to the page and generates a crawl error. Always test your redirects after implementation.
How to Implement 301 Redirects
The method for adding 301 redirects depends on your server and CMS:
Apache (.htaccess file) — for Apache web servers, add redirect rules to your .htaccess file. A single URL redirect uses: Redirect 301 /old-page /new-page. For HTTP-to-HTTPS redirection use a RewriteEngine rule with the R=301 flag.
Nginx — in the server block configuration, a permanent redirect can be set with: return 301 https://$host$request_uri;
WordPress — most SEO plugins (Yoast SEO Premium, Rank Math, Redirection plugin) provide a redirect manager with a UI for adding 301 redirects without editing server files.
Laravel — in routes/web.php: Route::redirect('/old-slug', '/new-slug', 301);
Shopify, Squarespace, Wix — all major hosted platforms provide a redirect manager in their admin dashboard under URL redirects or navigation settings.
After implementing, test each redirect using a tool like httpstatus.io or the curl command to verify the correct 301 status code and destination URL.
Common Mistakes to Avoid
- Using 302 when you mean 301 — accidentally setting a temporary redirect when the move is permanent means Google retains the old URL in its index and does not pass link equity. Always double-check the redirect code.
- Redirect chains — redirecting A to B to C instead of A to C directly. Each hop in a chain dilutes equity transfer and wastes crawl budget. Audit your redirects regularly and collapse chains.
- Forgetting internal links — after setting up 301 redirects, update your internal links to point directly to the new URLs. A redirect works, but a direct link is faster and cleaner.
- Redirecting to irrelevant pages — pointing deleted product pages to your homepage rather than a relevant category page is a poor user experience. Google notices when redirect destinations are not relevant and may not fully pass the equity.
- Not updating your sitemap — after changing URLs, update your XML sitemap to include only the new canonical URLs. A sitemap with old redirected URLs slows Google's index update.
- Not testing after implementation — always verify your redirects are returning 301 (not 302, 404, or 500) before considering the job done.
Frequently Asked Questions
Do 301 redirects lose SEO value?
Google has stated that 301 redirects pass PageRank and that rankings should transfer to the destination URL. Earlier studies suggesting significant link equity loss are now considered outdated. In practice, well-implemented 301 redirects result in minimal ranking impact over the short term, with full transfer confirmed over a few weeks.
How long should I keep a 301 redirect?
Keep 301 redirects in place for at least one year after a URL change. Google recommends keeping them permanently for important pages, since external sites may continue linking to the old URL indefinitely. The overhead of maintaining redirect rules is minimal compared to the risk of losing link equity by removing them prematurely.
What is the difference between a 301 and a canonical tag?
A 301 redirect sends both users and search engines to a new URL. A canonical tag (rel="canonical") tells search engines which URL to index as the preferred version, but does not redirect users — both URLs remain accessible. Use 301 redirects when you want to permanently retire the old URL; use canonical tags when both URLs need to remain accessible but you want Google to index only one.
Can I use 301 redirects for HTTPS migration?
Yes — HTTPS migration is one of the primary use cases for 301 redirects. Set up server-level redirects to send all HTTP traffic to HTTPS, and ensure your canonical tags and internal links all use HTTPS URLs. Update your sitemap to HTTPS URLs and resubmit to Google Search Console.