What Is a 301 Redirect? How To Do a 301 Redirect on 3 Common Servers + WordPress

A 301 redirect is a best practice in SEO. It preserves a good user experience for both search engines and website visitors when trying to access a file on a website. 

But what exactly is a 301 redirect, and how do you implement it? In this article, I’ll discuss what a 301 redirect is and how to do it on three different types of servers plus WordPress sites. 

What Is a 301 Redirect?

You’ve probably heard about 301 redirects. But what exactly are they and why do they matter so much? Let’s break it down.

Definition of 301 Redirect

A 301 redirect is an HTTP status code that signals a permanent redirect from one URL to another. 

In simple terms, it tells search engines that a page has permanently moved to a new location and quickly ushers website visitors to the new URL.

When a user or search engine bot tries to access the old URL, they’re automatically forwarded to the new one. This happens so quickly that most people don’t even notice the change.

Note that some modern servers and frameworks also support HTTP 308 redirects, which function similarly to 301 redirects but preserve the original request method. 

While 301 redirects remain the most commonly used option for SEO, you may encounter 308 redirects in newer web applications and APIs.

How 301 Redirects Work

So how does this all work behind the scenes? When a server receives a request for a URL that’s been 301 redirected, it responds with the 301 status code and the new URL location.

The browser or search engine bot then makes a new request to the new URL, and voila — the user ends up on the right page. 

When to Use 301 Redirects

There are a few key situations where you’ll want to use a 301 redirect:

1. If you’ve permanently moved a page to a new URL.
2. If you’re merging two websites and want to consolidate content.
3. If you’ve changed your site’s domain name or structure.

Basically, any time a page’s location has changed for good, a 301 redirect should be implemented. 

For large site migrations, create a redirect mapping document that pairs every important old URL with its new destination. This helps preserve rankings, backlinks and user experience during the transition.

Benefits of Using 301 Redirects

Now that we know what 301 redirects are and when to use them, let’s discuss why they’re so important. Implementing 301 redirects correctly can benefit SEO and user experience.

Preserving Link Equity

One of the biggest advantages of using 301 redirects is that they help preserve your site’s link equity. When another site links to your content, it passes along some of its authority and ranking power.

If you move that content without a 301 redirect, all of that valuable link equity is lost. 

But with a proper redirect in place, search engines understand that the page has moved and credit the new URL with the existing backlinks and authority.

Improving User Experience

301 redirects also play a key role in creating a smooth user experience. Visitors clicking on an old link could get a 404 error page without them.

And if you don’t have a custom 404 page that guides them elsewhere on the site, you’ll probably lose a visitor.

But with a redirect, they’re seamlessly sent to the new location of the content they wanted. There is no confusion, no frustration, just a quick and easy path to the information they need. 

Maintaining Search Engine Rankings

Lastly, 301 redirects help maintain your search engine rankings when content moves. If you don’t use a redirect, search engines may see the old URL as a 404 error and remove it from the index, costing you valuable organic traffic.

By implementing a 301, you signal to Google and other search engines that the page has permanently moved.  

How to Do a 301 Redirect on Apache, NGINX and Microsoft IIS

OK, now onto the subject of how to do a 301 redirect. 

First, a word of warning: Be careful when making the changes. One small mistake in a server configuration file like .htaccess can take your site offline until the mistake is fixed.

Implementing a 301 Redirect in Apache .htaccess Files

To implement a 301 redirect on an Apache server, you modify the .htaccess file, which allows changes per directory. 

The examples below use Apache’s mod_alias directives, which are often simpler than mod_rewrite rules for straightforward redirects.

This file controls that directory and all the subdirectories in it. Modifying the .htaccess file doesn’t require administrative rights.

Follow these initial steps to get started:

• The first step in doing a 301 redirect is to have the old URL and the new URL handy. 
• Log on to your website and find the .htaccess file in the root web folder.
• Open the .htaccess file by using a text editor like Notepad++. 
• Edit the file using the examples that follow.

301 Redirecting a Page in Apache

When you are ready to 301 redirect a page in Apache, add a line to the .htaccess file that tells the server what to do. There are two ways you can do this:

Example 1:

RedirectPermanent       /old-file.html   

Example 2: 

Redirect 301   /old-file.html   

There are essentially three parts to this:

1. The first part is the RedirectPermanent or Redirect 301, which tells the server what to do.
2. Then, you tell the server the old file’s relative path. If the file is in your root web directory, you can use the file path without the domain name.
3. The third part is the full path to the new file.

Save the file and test the redirect carefully before deploying changes to production. 

301 Redirecting an Entire Domain in Apache

Add a line to the .htaccess file to tell the server what to do. A redirection from one domain to another would look like this:

RedirectPermanent  / 

Implementing a 301 Redirect on an NGINX Server

Implementing a 301 redirect on an NGINX server is similar to doing so on an Apache server (in other words, it’s fairly straightforward). 

You’ll modify the configuration file, and you need admin privileges to do so.

Typically, this file is located in the directory: /usr/local/nginx/conf, /etc/nginx or /usr/local/etc/nginx

But not always. The file could also be somewhere else. The best thing to do is to use the command “nginx -t” to find where it is, like this:

$ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

For simple redirects in NGINX, many administrators prefer the return 301 directive because it is simpler and more efficient than using rewrite rules. For example:

location /old-page {

    return 301

}

For more advanced redirects involving patterns or entire folders, you can use a rewrite rule like the following:

rewrite ^/category/something/(.*)$      permanent;

At this point, I want to stress that this specific mod rewrite is for redirecting a specific folder URL (the entire folder) to another URL. 

The little asterisk (.*) is a wildcard symbol, so that means that any path after the forward slash in the first URL will be redirected and used in the second URL ($1). 

This redirect basically says the following: “if you have a category named something, then redirect it and anything underneath it  to another folder with the name of something-else.”

Implementing a 301 Redirect on a Microsoft IIS Server

Implementing a 301 redirect on a Microsoft IIS server is a bit more complex than on other servers. 

You will most likely need admin rights to do a 301 redirect, and you need to ensure that the HTTP Redirection Feature is installed. You can do this in Server Manager, under Manage > Add Roles and Features. 

To implement a 301 redirect:

1. Open the internet services manager (Start > All > Windows Tools > Internet Information Services (IIS) Manager, or search for IIS Manager in the Start Menu).
2. In the left column, select the site, folder or page you want to redirect. If you cannot see the thing you want to redirect, you can select the site, then click on the “Content View” tab to show the contents of the folder to select the file you want to redirect. After selecting the file or folder, you can click on “Features View” again.

3. In the center panel, using the Features View tab, find the “HTTP Redirect” icon and double-click.

4. Select “Redirect requests to this destination” then type the URL you want to redirect.

• Redirect to a single page: www.mydomain.com/newpage.htm
• Redirect to a directory: www.mydomain.com/newdirectory
• Redirect to a domain: www.mydomain.com

5. If keeping the directory structure and page names the same, ensure the two checkboxes below “redirect options” are unselected. Here is some context for the two options you will see:

• “Redirect all requests to exact destination:” Choose this if you want every file in the directory or domain you’re redirecting from to be routed to a single page. One situation where you would want to do this is if you are combining groups of directories into one separate site devoted to a specific topic, rather than have that topic on your site. In which case, you would not want all that content on the other site showing up on this existing site as duplicate content. So these content pages and files would need to be pruned and redirected accordingly. Another situation is if you had a hacked directory that wasn’t applied to the entire site, and you no longer want people to go to that directory. You could technically rename that directory, and redirect all files to a specific page. With additional work, this could effectively rebuild that directory.

• “Only redirect requests to content in this directory;” Choose this if you want to redirect only the files located in the selected directory, not subdirectories. One situation where you would want to do this is if you have performed a content audit and found pages that you want to prune from your overall content profile. You would want to eliminate and redirect pages within a category to the main category page.

6. For “Status code,” choose “Permanent (301).”

7. In the menu on the right column, choose “Apply.”

How to Do a 301 Redirect on WordPress 

If your site runs on WordPress, you’re in luck — there are several handy plugins that make setting up 301 redirects a breeze. Some popular options include:

• Redirection.
• Yoast SEO. 
• Simple 301 Redirects.
• Quick Page/Post Redirect Plugin.
• Rank Math.

With these plugins, you can easily create and manage redirects right from your WordPress dashboard, without messing with any code. 

Just enter the old URL, the new URL, hit save and you’re good to go.

Note that for large websites or complex migrations, server-level redirects are generally more scalable and performant than relying entirely on plugins.

Common Mistakes to Avoid with 301 Redirects

When implementing 301 redirects, a few common pitfalls can lead to issues later on. So, let’s dive into some of the most frequent mistakes and how to avoid them.

Redirect Chains

First, we have the redirect chain. This happens when a series of redirects point to each other, creating a long chain of hops before finally reaching the destination page.

Not only does this slow down the user experience, but it can also dilute the link equity you’re trying to pass along. Search engines might even give up trying to follow the chain altogether.

Redirect Loops

Next, we have redirect loops. This is when you accidentally create a circular path of redirects, sending users and search engine bots into an infinite loop of frustration. 

It’s crucial to double-check your redirects to ensure they’re all pointing in the right direction.

Redirecting to Irrelevant Pages

Another common mistake is redirecting users to completely irrelevant pages. This is a surefire way to annoy your visitors and increase bounce rates.

Always take the time to map out your redirects and ensure that users are sent to the most relevant page possible. It’s worth the extra effort.

As a final note on this, avoid redirecting large groups of unrelated URLs to the homepage. Search engines may treat these as soft 404s if the destination is not meaningfully related to the original content.

Using 302s Instead of 301 Redirects

It is important to make sure that you’re using the redirect type that is relevant for your use case. 

If you’re only making temporary changes, you have to make sure that these changes are followed up by removing the redirect as soon as possible once Google has crawled and indexed the new versions of your pages.

If the redirect is of a permanent nature, always use the 301 redirect instead of the 302. 

While Google can pass ranking signals through many redirect types today, using the correct redirect type still matters. A 301 or 308 redirect clearly signals a permanent move, while a 302 or 307 indicates a temporary change.

Best Practices for 301 Redirects

Now that we’ve covered some of the most common mistakes to avoid with 301 redirects, let’s talk about best practices. 

Here are a few key tips to keep in mind:

Updating Internal Links

One often overlooked aspect of implementing redirects is updating your internal links. 

If you’ve moved a page and set up a 301 redirect, that’s great. But don’t forget to also update any internal links on your site that point to the old URL.

This helps site visitors and search engine bots navigate your site more efficiently, without running into unnecessary redirects. 

It’s a small step that can make a big difference in your site’s overall performance.

Monitoring and Testing Redirects

Another key best practice is regularly monitoring and testing your redirects. Just because you set them up once doesn’t mean you can set it and forget it.

I recommend using tools like Screaming Frog or Google Search Console to monitor your redirects and ensure they’re all working as intended. 

You can also test redirects manually using browser developer tools, online redirect header checkers or command-line tools like curl. For example:

curl -I

This command returns the HTTP response headers so you can verify that the page is returning the correct redirect status code and destination URL.

You’d be surprised how often redirect issues can crop up over time, especially if you frequently change your site’s structure or content.

If you use a CDN or reverse proxy like Cloudflare, redirect behavior may also be configured or cached outside the origin server. 

In these cases, you may need to clear caches or review CDN-level redirect rules when troubleshooting issues

Keeping URLs Simple and Relevant

Finally, when you’re setting up new URLs for your redirected pages, it’s important to keep them simple, relevant and descriptive. 

Avoid using complex structures or unnecessary parameters that could cause problems down the line.

Remember, your URLs are important for user experience and your site’s overall SEO. 

When you keep them clean and descriptive, you’ll make it easier for both users and search engines to understand what your pages are about.

Final Thoughts

301 redirects may seem like a small, technical detail, but they are crucial in keeping the web running smoothly. 

Understanding when and how to use them helps ensure that your site visitors always find what they’re looking for, even if things move around behind the scenes.

With these best practices in your toolkit, you’ll be sure to create a great user experience on any website. 

FAQ: How can I use a 301 redirect to manage permanent URL changes on my website?

A 301 redirect is the standard method for permanently moving a webpage from one URL to another. 

When implemented correctly, it automatically sends users and search engines from the old URL to the new one, helping preserve traffic, maintain search visibility and prevent 404 errors.

A 301 redirect differs from a 302 redirect, which indicates that a move is temporary. 

While a 301 signals that search engines should update their index to the new URL, a 302 typically tells them to continue treating the original URL as the primary destination.

Proper 301 redirect management is important because it:

• Preserves user access to content after URL changes.
• Helps maintain organic search performance during site updates and migrations.
• Consolidates ranking signals from existing backlinks.
• Prevents broken links and unnecessary 404 errors.
• Improves the overall user experience.

301 redirects are commonly used during website migrations, domain changes, content consolidation and URL structure updates. 

However, poorly managed redirects can create issues such as redirect chains, redirect loops and slower page loads.

Best practices for managing 301 redirects include:

• Use 301 redirects only for permanent URL changes.
• Redirect each old URL directly to its most relevant new destination.
• Avoid redirect chains by limiting redirects to a single hop whenever possible.
• Maintain a documented redirect map for site updates and migrations.
• Regularly monitor 404 errors and fix broken links.
• Keep redirects in place as long as users, backlinks or search engines may still access the old URLs.
• Audit redirects periodically to identify outdated or unnecessary rules.

Action Plan: Implementing 301 Redirects

1. Identify the URLs that need to be redirected.
2. Map each old URL to the most relevant new URL.
3. Configure the redirect within your CMS, server or redirect management platform.
4. Verify that each redirect returns a 301 Moved Permanently status code.
5. Test redirects to confirm they resolve correctly and do not create loops or chains.
6. Monitor analytics and search performance after implementation.
7. Review redirects regularly, especially after major website updates.

Tools such as Redirect Path can help validate redirect status codes and identify redirect chains, loops and broken URLs.

301 redirects are a critical part of technical SEO and website maintenance. A well-planned redirect strategy helps users find the content they need, preserves valuable search visibility and supports a smooth experience during website changes or migrations.

See Bruce’s author page for links to connect on social media.