Technical SEO

301 Redirects: Complete Guide to URL Redirection for SEO

301 redirects are one of the most important technical SEO tools. Whether you are changing URLs, migrating domains, consolidating pages, or fixing broken links, proper redirect implementation determines whether you keep your hard-earned rankings or lose them overnight. This guide covers everything you need to know about redirects in 2026.

Rank Crown Team
April 8, 2026
17 min read

Key Takeaway

A 301 redirect permanently moves a URL to a new location and passes approximately 95-99% of link equity to the destination. Always use 301 (not 302) for permanent URL changes. Avoid redirect chains (more than one hop), keep redirects in place for at least one year, and monitor for broken redirects regularly. A well-managed redirect strategy preserves rankings during any URL change.

What Is a 301 Redirect?

A 301 redirect is an HTTP status code that tells browsers and search engines that a page has permanently moved to a new URL. When a user or crawler requests the old URL, the server responds with status code 301 and the new location. The browser automatically navigates to the new URL, and search engines transfer the old page's ranking signals (link equity, authority) to the new URL. For background context, see the reference at Google Search Central documentation.

The "301" means "Moved Permanently" - as opposed to 302 ("Found" / temporary redirect) or 307 ("Temporary Redirect"). This distinction matters enormously for SEO because only permanent redirects reliably pass link equity.

Without 301 redirects, changing any URL on your site would result in a 404 error for anyone accessing the old URL - including Google. All the backlinks, social shares, and bookmarks pointing to the old URL would be wasted, and the new page would have to build authority from scratch.

Developer reviewing website source code and meta tags
Technical SEO ensures search engines can efficiently crawl and index your content.

1When to Use 301 Redirects

Changing URL slugs

When you rename a page's URL (e.g., /old-blog-post to /updated-seo-guide), redirect the old URL to the new one to preserve rankings and fix existing links.

Consolidating duplicate pages

If you have multiple pages targeting the same keyword (keyword cannibalization), redirect the weaker pages to the strongest one to consolidate link equity.

Domain migrations

Moving from olddomain.com to newdomain.com requires 301 redirects for every URL on the old domain to its equivalent on the new domain.

HTTP to HTTPS migration

Switching to HTTPS requires redirecting all HTTP URLs to their HTTPS equivalents. This preserves link equity from existing backlinks.

Fixing broken pages

When a page is removed and a relevant replacement exists, redirect the old URL to the most relevant alternative rather than returning a 404.

Merging websites

When combining two websites into one, redirect all pages from the absorbed site to relevant pages on the surviving site.

2301 vs 302 Redirects: Critical Difference

Feature301 (Permanent)302 (Temporary)
Link equity transfer~95-99%Historically none (now partial)
Google indexingIndexes new URLMay keep old URL indexed
Browser cachingCached permanentlyNot cached
Use casePermanent URL changesA/B tests, maintenance
SEO recommendationDefault choiceOnly when truly temporary

Common mistake: Using 302 redirects when you mean 301. Many CMS platforms and plugins default to 302. Always verify the redirect type. A 302 that stays in place for years tells Google confusing signals about which URL is canonical.

3Implementation Methods

There are several ways to implement 301 redirects depending on your server and CMS:

.htaccess (Apache)

Add Redirect 301 /old-page /new-page or use RewriteRule for pattern-based redirects. The most common method for Apache servers. Changes take effect immediately.

nginx configuration

Use 'return 301 /new-page;' in the server block or 'rewrite ^/old-page$ /new-page permanent;' for regex-based redirects. Requires nginx reload.

WordPress plugins

Rank Math and Yoast Premium include redirect managers. The Redirection plugin is a free dedicated option. These create .htaccess rules or PHP-level redirects.

Cloudflare Page Rules

Create redirect rules in Cloudflare's dashboard. Works regardless of your server. Limited to 3 free rules but handles bulk redirects in paid plans.

Next.js / Vercel

Add redirects to next.config.js or vercel.json. Use the 'permanent: true' flag to specify 301 status code.

JavaScript redirects

Using window.location = '/new-url' - NOT recommended for SEO. Search engines may not follow JavaScript redirects and link equity may not transfer.

5Redirect Chains and Loops

A redirect chain occurs when URL A redirects to URL B, which redirects to URL C, which redirects to URL D. Each hop adds latency and may dilute link equity. Google follows up to 5 redirect hops but recommends keeping chains to a single hop.

A redirect loop occurs when URL A redirects to URL B, and URL B redirects back to URL A. This creates an infinite cycle that browsers detect and stop after a few attempts, showing an error page. Fix loops immediately - they make pages completely inaccessible.

Use Screaming Frog to identify redirect chains on your site. The Response Codes tab highlights all redirect chains and their hop counts. Fix chains by updating each redirect to point directly to the final destination.

6Redirects for Site Migrations

Site migrations - changing domain, platform, or URL structure - are the highest-stakes redirect scenarios. Every URL on the old site must have a corresponding 301 redirect to the equivalent page on the new site. Missing redirects during migrations are the #1 cause of post-migration traffic losses.

Crawl the entire old site before migration to get a complete URL list
Create a 1:1 redirect map: old URL → new URL for every page
Map old pages to the most relevant new page (not all to homepage)
Test every redirect before going live using staging environment
Monitor Search Console for crawl errors after migration
Keep old domain redirects active for at least 1 year
Submit updated XML sitemap with new URLs immediately after migration

7Common 301 Redirect Mistakes

Redirecting everything to homepage

Lazy redirect mapping sends all old URLs to the homepage. This is a soft 404 in Google's eyes - the homepage doesn't satisfy the original search intent. Map each old URL to the most relevant new page.

Using 302 instead of 301

Many CMS platforms default to 302 redirects. Always verify the status code. A 302 tells Google the old URL might come back, preventing proper link equity transfer.

Creating redirect chains

Over time, accumulated redirects create chains (A→B→C→D). Audit regularly and point all redirects directly to the final destination URL.

Removing redirects too soon

Removing 301 redirects after a few weeks means any backlinks pointing to the old URL will hit 404 errors. Keep redirects for at least 1 year.

Not updating internal links

After adding redirects, update all internal links to point directly to the new URLs. Internal links should never pass through redirects - it wastes crawl budget.

SEO analytics dashboard showing traffic and ranking metrics
Monitoring key SEO metrics helps track progress and identify optimization opportunities.

8Best Practices

Always use 301 for permanent URL changes - never 302 or meta refresh
Redirect to the most topically relevant page, not just the homepage
Keep redirect chains to a single hop - always point directly to the final URL
Implement server-side redirects (.htaccess, nginx) - avoid JavaScript redirects
Update internal links to point to new URLs directly after setting up redirects
Monitor Google Search Console for crawl errors and redirect issues
Keep 301 redirects in place for at least 1 year, preferably indefinitely
Document all redirects in a spreadsheet for future reference
Test redirects after implementation - verify correct status code and destination
Audit existing redirects quarterly for chains, loops, and broken destinations

Monitor Your Redirects and Rankings

Rank Crown tracks your site's technical health including redirect issues, broken links, and ranking changes. Get alerts when redirects break or rankings drop after URL changes.

Start Tracking for Free

Frequently Asked Questions

What is a 301 redirect?

A 301 redirect is an HTTP status code that permanently moves a URL to a new location. It tells browsers and search engines to update their records and passes approximately 95-99% of link equity (ranking power) from the old URL to the new one.

Do 301 redirects pass link equity?

Yes. Google confirmed that 301 redirects pass PageRank to the destination URL with minimal loss. For best results, redirect to a topically relevant page (not the homepage) and keep the redirect in place for at least one year.

When should I use 301 vs 302 redirect?

Use 301 for any permanent URL change - domain migrations, slug changes, page consolidation. Use 302 only for genuinely temporary situations like A/B tests or maintenance pages where you intend to restore the original URL.

How long should I keep 301 redirects?

Google recommends keeping 301 redirects 'as long as possible.' At minimum, keep them for 1 year. After that, Google has typically updated its index. Many SEO professionals keep redirects indefinitely since there is no cost to doing so.

Do redirect chains hurt SEO?

Yes. Redirect chains (A→B→C→D) add latency, waste crawl budget, and may lose a small amount of link equity at each hop. Google follows up to 5 hops but recommends single-hop redirects. Audit and flatten chains regularly.

Monitor Your Redirects and Rankings

Rank Crown tracks your site's technical health including redirect issues, broken links, and ranking changes. Get alerts when redirects break or rankings drop after URL changes.