<\/span><\/h2>\n\n\n\nOne of the most common and recommended solutions is to add a permanent 301 redirect from URL with trailing slash to URL without one. It returns a 301 response to search engines indicating the URL has permanently moved. This eliminates the problem of duplicate content. <\/p>\n\n\n\n
For this, open NGINX config file using text editor. It is typically located at \/etc\/nginx\/nginx.conf.<\/p>\n\n\n\n
$ vi \/etc\/nginx\/nginx.conf<\/pre>\n\n\n\nIf you use a virtual host, then open its configuration file at \/etc\/nginx\/sites-enabled\/<\/p>\n\n\n\n
In the server block, add the following line.<\/p>\n\n\n\n
rewrite ^\/(.*)\/$ \/$1 permanent;<\/pre>\n\n\n\nLet us look at the above command.<\/p>\n\n\n\n
^\/(.*)\/$ – Regular expression that matches any URL with a trailing slash.<\/p>\n\n\n\n
\/$1 – Format of new URL without trailing slash<\/p>\n\n\n\n
permanent – keyword to specify permanent redirection.<\/p>\n\n\n\n
Basically, the above directive tells NGINX to permanently redirect any URL that has a trailing slash. Save and close the file. You can add this directive to server, or location blocks. If you add it to a server block, then it will be applicable to all URLs served in the server. If you add it to a location block, then it will be applicable only to the URLs matched by the location block.<\/p>\n\n\n\n
server{
...
rewrite ^\/(.*)\/$ \/$1 permanent;
...
}
location \/ {
...
rewrite ^\/(.*)\/$ \/$1 permanent;
...
}<\/pre>\n\n\n\nTest NGINX configuration.<\/p>\n\n\n\n
$ sudo nginx -t<\/pre>\n\n\n\nRestart NGINX server.<\/p>\n\n\n\n
$ sudo service nginx reload<\/pre>\n\n\n\n