301 redirect: permanent redirect explained

If you've ever moved a website, renamed pages or changed your URL structure, you've dealt with redirects. The 301 redirect is the most used and important redirect for SEO. In this article we explain what a 301 redirect is, how it differs from other redirects, and how to implement it correctly.

What is a 301 redirect?

A 301 redirect is a permanent redirect from one URL to another. It's an HTTP status code that tells browsers and search engines: "This page has moved to a new location permanently. Update your bookmarks and indexes."

When a visitor or search engine requests a page that has a 301 redirect, they're automatically and immediately forwarded to the new URL. They don't even see the old page - the redirect happens within milliseconds.

The "301" is the official HTTP status code. Servers use these codes to communicate what's happening with a request. A 301 specifically means "Moved Permanently".

Difference between 301 and 302 redirect

There are different types of redirects, and it's crucial to use the right one:

301 (Permanent) tells Google the page has moved permanently. Google passes all link juice (SEO value) to the new URL and replaces the old URL with the new one in search results. This is what you want to use in 95% of cases.

302 (Temporary) indicates the move is temporary. Google keeps the old URL in the index and does NOT fully pass the link juice. Only use this if you want to temporarily redirect the page but later return to the original URL.

Using a 302 instead of a 301 incorrectly is a common SEO mistake. You lose your rankings because Google thinks it's temporary and keeps indexing the old page (which no longer exists).

When do you use a 301 redirect?

There are numerous situations where you need a 301 redirect:

Website move to new domain: If you move from olddomain.com to newdomain.com, you redirect all old URLs to their new equivalents. This preserves your SEO value.

HTTPS migration: When switching from HTTP to HTTPS, you must redirect all HTTP URLs to their HTTPS versions. This is standard nowadays.

Change URL structure: If you adjust your permalink structure (for example from /p=123 to /blog/article-title/), you redirect all old URLs to the new ones.

Deleted pages: When you delete a page, redirect it to the most relevant similar page or the homepage. This way you don't lose link juice and visitors don't get a 404 error.

Solve duplicate content: If you have multiple URLs showing the same content (with and without www, with and without trailing slash), you redirect to one canonical version.

Merging pages: If you combine two pages into one, you redirect the old pages to the new combined page.

Impact on SEO: what happens to your rankings?

This is what many people worry about: do you lose SEO value with a 301 redirect?

The short answer: a correctly implemented 301 redirect preserves 90-99% of your SEO value. Google has confirmed there's no significant ranking loss with 301 redirects. The small link juice lost (if any) is negligible.

Link juice is passed: All backlinks pointing to the old URL pass their value to the new URL. This is crucial for maintaining your rankings.

Rankings remain largely intact: If your old page was at position 3 in Google, the new page will take approximately the same position over time (provided the content is comparable).

Indexing is updated: Google replaces the old URL with the new one in their index. This can take several days to weeks, depending on your crawl budget.

Anchor texts remain preserved: The anchor texts of backlinks to the old URL remain relevant for the new URL, which is good for SEO.

How do you implement a 301 redirect?

There are several ways to set up a 301 redirect, depending on your setup:

Via .htaccess (Apache servers)

This is the most common method for WordPress sites and other Apache-running servers. Add this to your .htaccess file:

Redirect 301 /old-page/ https://yourdomain.com/new-page/

For an entire domain redirect:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^olddomain.com [NC]
RewriteRule ^(.*)$ https://newdomain.com/$1 [L,R=301]

Via WordPress plugins

For WordPress there are excellent redirect plugins:

Redirection is the most popular free plugin. You can easily add redirects, monitor 404 errors and manage redirects via a user-friendly dashboard.

Rank Math and Yoast SEO Premium have built-in redirect managers.

Via PHP

In your theme's functions.php or in a template:

header("HTTP/1.1 301 Moved Permanently");
header("Location: https://yourdomain.com/new-page/");
exit();

Via Nginx

In your Nginx configuration:

location /old-page/ {
return 301 https://yourdomain.com/new-page/;
}

Common mistakes with 301 redirects

Even experienced webmasters make these mistakes:

Redirect chains: This is when URL A redirects to B, which redirects to C, which redirects to D. Each additional hop in the chain costs time and SEO value. Google follows a maximum of 5 redirects and then stops. Ensure redirects always go directly to the final destination.

Redirect loops: URL A redirects to B, which redirects back to A. This creates an infinite loop and results in a "Too many redirects" error. Check your redirect logic carefully.

Using 302 instead of 301: As mentioned earlier, this is a critical SEO mistake. Always check which status code your redirect uses.

Redirecting to irrelevant pages: If you delete an article about "WordPress hosting" and redirect to your homepage, you lose relevance. Always redirect to the most similar page.

Waiting too long to implement: During a domain move, redirects must go live immediately when the new site is online. Every day old URLs give 404 errors, you lose SEO value and traffic.

Removing redirects after time: Some people remove redirects after a year, thinking Google knows the new URLs by then. But backlinks exist forever. Keep redirects permanently.

How many redirects are too many?

Too many redirects can slow down your site. Each redirect costs time - usually 20-50 milliseconds. For individual pages you barely notice this, but if you have thousands of redirects, it can have impact.

As a rule of thumb: under 1000 redirects is no problem. Websites with 5000-10000 redirects also work fine, as long as your redirect management is well organized.

With extremely many redirects (50,000+) it's wise to look at server-level solutions like Nginx or Varnish instead of .htaccess or database-based redirects.

Monitoring and testing 301 redirects

After implementing redirects, you must test them:

Browser tools: Open browser developer tools (F12), go to the Network tab, and load the old URL. You now see the HTTP status code. This should be 301, not 302.

Online redirect checkers: Tools like httpstatus.io and redirect-checker.org show you the complete redirect chain and status codes.

Google Search Console: Monitor your old URLs in Search Console. Google indicates when URLs are replaced by redirects and shows any errors.

Screaming Frog: This SEO tool can crawl your entire site and report all redirects, including chains and loops.

Check your redirects regularly, especially after major site changes or updates.

HTTP to HTTPS redirects

This deserves special attention because it's so universal. Every modern website should run on HTTPS. The redirect from HTTP to HTTPS is a permanent 301 redirect:

In .htaccess:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

This redirects all HTTP requests to their HTTPS equivalent. Important: only implement this after your SSL certificate is correctly installed and working.

Performance impact of redirects

Redirects have a small but measurable impact on loading time:

A single redirect costs approximately 20-50ms extra loading time. For mobile users on slow connections this can run up to 200-400ms.

Redirect chains (multiple redirects in succession) stack this delay. A chain of 3 redirects can cost 100-200ms, which is significant for user experience and SEO.

Best practice: minimize redirects in your critical rendering path. Update internal links directly to the new URL instead of relying on redirects.

Alternative: canonical tags vs 301 redirects

Sometimes a canonical tag is a better alternative than a 301 redirect:

Canonical tags tell Google which version of a page is the "main" version, without redirecting the user. This is useful for:

• Same content on multiple URLs (print versions, pagination)
• URL parameters creating duplicate content
• A/B testing variants

A 301 redirect actually forwards users and search engines. A canonical tag lets all URLs exist but tells Google which to index.

Use canonical tags when different URLs must legitimately continue to exist. Use 301 redirects when the old URL should no longer exist.

Frequently Asked Questions

How much does web hosting cost on average?

Web hosting costs between €3 and €15 per month for shared hosting on average. VPS hosting starts around €10-€20 per month, and dedicated servers from €50 per month.

Can I upgrade to a different package later?

Yes, with most hosting providers you can easily upgrade to a larger package when your website grows. This can usually be done without downtime.

Is Dutch hosting better than foreign hosting?

For Dutch visitors, Dutch hosting is often faster due to the shorter distance. Additionally, communication with support is easier and you comply with GDPR legislation.