{"id":2000,"date":"2023-11-08T16:08:18","date_gmt":"2023-11-08T10:38:18","guid":{"rendered":"https:\/\/www.veeble.org\/kb\/?p=2000"},"modified":"2025-03-17T11:48:22","modified_gmt":"2025-03-17T06:18:22","slug":"create-redirects-nginx","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/create-redirects-nginx\/","title":{"rendered":"How to Create Redirects with Nginx"},"content":{"rendered":"\n

A redirect is a way to send both users and search engines to a different URL from the one they initially requested. This guide will walk you through the basics of redirects and how to implement them using Nginx, making your website management journey smoother and more efficient. The simplicity of Nginx configuration files makes it an accessible tool for setting up redirects.<\/p>\n\n\n\n

<\/p>\n\n\n

How to Create Redirects in Nginx<\/h3>\n\n\n

Creating redirects in Nginx is done by modifying the server configuration files. The primary configuration file for Nginx is located at \/etc\/nginx\/nginx.conf<\/code>. Individual site configurations reside in \/etc\/nginx\/sites-available<\/code> and are enabled by linking to \/etc\/nginx\/sites-enabled<\/code>. Familiarizing yourself with these files is key to successfully managing redirects.<\/p>\n\n\n

Implementing a 301 Permanent Redirect<\/h5>\n\n\n

A 301 redirect is used when a page has been moved permanently. To implement a 301 redirect in Nginx, you would add the following line to your server configuration block:<\/p>\n\n\n\n

rewrite ^\/old-page$ http:\/\/www.yourdomain.com\/new-page permanent;<\/pre>\n\n\n
Implementing a 302 Temporary Redirect<\/h5>\n\n\n
A 302 redirect<\/a> is similar but is used when the move is temporary. The Nginx configuration line would look like this:<\/p>\n\n\n\n
rewrite ^\/old-page$ http:\/\/www.yourdomain.com\/new-page redirect;<\/pre>\n\n\n
Creating Wildcard Redirects<\/h5>\n\n\n
For multiple URL changes, wildcard redirects are handy. With Nginx, you can use regular expressions to match patterns:<\/p>\n\n\n\n
rewrite ^\/old-folder\/(.*)$ http:\/\/www.yourdomain.com\/new-folder\/$1 permanent;<\/pre>\n\n\n
Redirecting WWW to Non-WWW<\/h5>\n\n\n
Canonicalizing your domain is crucial for SEO. Here’s how you redirect the www<\/code> version of your site to the non-www<\/code>:<\/p>\n\n\n\n
server {\n    server_name www.yourdomain.com;\n    return 301 $scheme:\/\/yourdomain.com$request_uri;\n}<\/pre>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n
Testing and Troubleshooting Your Redirects<\/h3>\n\n\n
After setting up redirects, testing them is essential to ensure they work as intended.<\/p>\n\n\n
How to Test Redirects<\/h5>\n\n\n
You can test redirects by visiting the old URLs and observing whether you’re taken to the new location. Tools like curl<\/code> are also handy for testing redirects non-interactively.<\/p>\n\n\n
Solving Common Redirect Issues<\/h5>\n\n\n
If a redirect isn’t working, check for typos in the URL patterns or incorrect file paths. Ensure that you reload Nginx after making changes (sudo systemctl reload nginx<\/code>) so that your updates take effect.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Avoid creating long chains of redirects, as they can slow down page load times and impact SEO. Consolidate multiple-step redirects into a single step where possible. And for complex redirect rules, Nginx allows the use of regular expressions. This is advanced usage and requires careful testing.<\/pre>\n\n\n\n
<\/p>\n\n\n
Conclusion and Further Learning<\/h3>\n\n\n
You\u2019re now equipped with the knowledge to implement redirects using Nginx. While there is much more to learn, this guide provides a solid foundation for managing web traffic effectively.<\/p>\n\n\n\n