{"id":5244,"date":"2019-12-30T10:29:35","date_gmt":"2019-12-30T08:29:35","guid":{"rendered":"https:\/\/www.dazzlepop.net\/site\/?p=5244"},"modified":"2020-04-30T14:03:21","modified_gmt":"2020-04-30T12:03:21","slug":"a-technical-seo-guide-to-redirects","status":"publish","type":"post","link":"https:\/\/www.dazzlepop.net\/site\/a-technical-seo-guide-to-redirects\/","title":{"rendered":"A Technical SEO Guide to Redirects"},"content":{"rendered":"
\"A<\/div>\n

A Technical SEO Guide to Redirects. Websites<\/a> change structure, delete pages and often move from one domain to another. Handling\u00a0redirects<\/a>\u00a0correctly is crucial in order to avoid losing rankings and help search engines understand the changes you have done.<\/p>\n\n\n\n

Redirects have a status code starting with number three (i.e., 3XX). There are 100 different<\/a> possible status codes but only a few are implemented<\/a> to carry certain information.<\/p>\n\n\n\n

In this guide, we will cover 3XX redirects relevant to SEO<\/a>.<\/p>\n\n\n\n

301: Moved Permanently<\/h2>\n\n\n\n

This well-known redirect indicates to a client* that the resource was changed to another location and that it should use the new URL for future requests. When search engines<\/a> see a 301 redirect, they pass the old page\u2019s ranking to the new one.<\/p>\n\n\n\n

Before making a change, you need to be careful when deciding to use a 301 redirect. This is because if you change your mind later and decide to remove the 301 redirect, your old URL may not rank anymore.<\/p>\n\n\n\n

Even if you swap the redirects, it will not help you get the old page back to its previous ranking position. So the main thing to remember is that there\u2019s no way to undo a 301 redirect.<\/p>\n\n\n\n

(*For beginners who may get confused with generic name client is used instead of browser since not only browsers are able to browse URLs but also search engine bots which are not browsers.)<\/em><\/p>\n\n\n\n

\"A
A Technical SEO Guide to Redirects<\/figcaption><\/figure>\n\n\n\n

307: Temporary Redirect<\/h2>\n\n\n\n

In HTTP 1.1, a 301 redirect means the resource is temporarily moved and the client should use the original resource\u2019s<\/strong> URL for future requests.<\/p>\n\n\n\n

For SEO, this means the client should follow a redirect but search engines should not update their links in the SERPs to the new, temporary page.<\/p>\n\n\n\n

In a 307 redirect, PageRank is not <\/em>passed from the original resource to the new one \u2013 contrary to a 301 redirect.<\/p>\n\n\n\n

302: Found<\/h2>\n\n\n\n

This means that the resource a client is looking for was found on another URL in the HTTP 1.1 version but was temporarily moved in HTTP 1.0.<\/p>\n\n\n\n

302 vs. 307<\/h2>\n\n\n\n

In almost all cases, 302 and 307 redirects will be treated the same<\/a>. But a 302 status code doesn\u2019t necessarily mean the client must follow a redirect and it is not considered an error if it decides to stay there.<\/p>\n\n\n\n

Modern clients will most likely follow the new destination but some old clients may incorrectly stay on the same URL.<\/p>\n\n\n\n

Contrary to a 302 status code, the 307 status code guarantees that the request method will not be changed. For instance, the GET request must continue to GET and POST to POST.<\/p>\n\n\n\n

With a 302 status code, some old or buggy clients may change the method which may cause unexpected behavior.<\/p>\n\n\n\n

For temporary redirects, you can use either 302 or 307 \u2013 but I do prefer 307.<\/p>\n\n\n\n

For routine redirect tasks, 301 (permanent redirect) and 307 (temporarily redirect) status codes should be used depending on what type of change you are implementing on your website. In both cases, the syntax of redirects doesn\u2019t change.<\/p>\n\n\n\n

You may handle redirect via server config files .htaccess on Apache, example.conf file on Nginx, or via plugins if you are using WordPress.<\/p>\n\n\n\n

In all instances, they have the same syntax for writing redirect rules. They differ only with commands used in configuration files. For example, redirect on Apache will look like this:<\/p>\n\n\n\n

Options +FollowSymlinks\nRewriteEngine on\nRedirectMatch 301 ^\/oldfolder\/ \/newfolder\/<\/pre>\n\n\n\n
(You can read about symlinks here<\/a> ).<\/p>\n\n\n\n
On Nginx servers, it will look like:<\/p>\n\n\n\n
rewrite ^\/oldfolder\/ \/newfolder\/ permanent;<\/pre>\n\n\n\n
The commands used to tell servers status code of redirect and the action command differ. For instance:<\/p>\n\n\n\n