<\/span>When to use 301 redirects?<\/span><\/h2>\n\n\n\n\n- Responsive design.<\/strong> The most popular redirect is redirecting the user from the desktop version of the site to the mobile version.<\/li>\n\n\n\n
- When rebranding.<\/strong> In cases where you changed the brand name and moved to a site with a new domain name.<\/li>\n\n\n\n
- When you switch to a secure connection protocol:<\/strong> change the HTTP protocol to HTTPS to protect yourself and your clients.<\/li>\n\n\n\n
- To redirect from irrelevant pages\/sites. <\/strong>For example, a product is no longer on sale, or you no longer provide a service and want to redirect the user to a page with a similar product or service.<\/li>\n\n\n\n
- When sites or pages are duplicated.<\/strong> Similar content on several resources worsens the ranking, and if the sites or pages are identical, search engines will exclude these pages from the search. Permanent and temporary redirects will be helpful to avoid creating duplicates and risking ranking.<\/li>\n\n\n\n
- With frequent queries with a www, if your site is without a www.<\/strong> You can be linked to both, but they are different sites for search engines, so it\u2019s a good idea to set up a redirect to just one of the pages.<\/li>\n\n\n\n
- When migrating to a new site engine.<\/strong> Each CMS has its own rules for generating URLs. If the address does not match the old one, you can not do without a redirect – otherwise, customers will never find you. <\/li>\n\n\n\n
- 404 pages<\/strong>. Sometimes it is necessary to set a redirection up from a broken page to a live one.<\/li>\n<\/ul>\n\n\n\n
<\/span>What is a 301 redirect in SEO?<\/span><\/h2>\n\n\n\n301 redirect benefits for SEO:<\/strong><\/p>\n\n\n\n\n- Save traffic;<\/li>\n\n\n\n
- Prevent the loss of PageRank;<\/li>\n\n\n\n
- Get rid of duplicate pages;<\/li>\n\n\n\n
- Eliminate the presence of low-quality pages in the search results;<\/li>\n\n\n\n
- Redirect the crawler (search bot) and the user from an irrelevant page or with a 404 server response code.<\/li>\n<\/ul>\n\n\n\n
From a user experience standpoint, 301 redirects are helpful because they allow redirecting traffic to related products if the one they are looking for is deleted. Such practice reduces the probability of user bounce.<\/strong><\/p>\n\n\n\nSome time after you set up the redirect, the search engine will update its index, replacing the old page address with the new one. Browsers and other types of clients will cache the new URL and automatically follow the redirect directly without checking the original for subsequent requests. Saved bookmarks are also usually updated.<\/p>\n\n\n\n
<\/span>How to set up 301 redirects?<\/span><\/h2>\n\n\n\nThere are many ways to make a 301 redirect: .htaccess, PHP, javascript, server settings, <\/strong>and others. We recommend not using all methods at once. There is too high a probability of discrepancies between different processes. The most commonly used way of configuration is through .htaccess. <\/p>\n\n\n\n<\/span>What is the .htaccess file for, and how to find it?<\/span><\/h3>\n\n\n\nThe .htaccess file is a configuration file that defines the rules of the web server in the directories and subdirectories where it is located<\/strong>. Most often, it will be the root folder of your site.<\/p>\n\n\n\nIf you can’t find<\/strong> the .htaccess, there are a few options:<\/p>\n\n\n\n\n- The file has a different name. It is scarce, but it is possible. The actual name can be clarified with the hosting provider: it can be, for example, .config, .htaccess.http, access.conf.<\/li>\n\n\n\n
- The file still needs to be created. This is the most common case. It is necessary to create a .htaccess file and write the redirection directives into it later.<\/li>\n<\/ol>\n\n\n\n
Further info on .htaccess: https:\/\/developer.wordpress.org\/advanced-administration\/server\/web-server\/httpd\/<\/a><\/p>\n\n\n\n<\/span>How to create a new .htaccess file?<\/span><\/h3>\n\n\n\n\n- Create an empty text file with a .txt extension.<\/li>\n\n\n\n
- Rename it by removing the name and adding the extension .htaccess. <\/li>\n\n\n\n
- If you work on macOS, a file with no name will not be visible. Then give it any name you want, and rename it after it is uploaded to the server.<\/li>\n<\/ol>\n\n\n\n
<\/span>Setting up 301 redirects in .htaccess with examples<\/span><\/h2>\n\n\n\nWe will use the conventional addresses of sites and pages to show you 301 redirect examples – <\/em>you will need to replace them with yours.<\/em><\/strong><\/p>\n\n\n\n<\/span>301 redirect of one page<\/span><\/h3>\n\n\n\nThe easiest way is to use the Redirect directive. Try one of the options:<\/p>\n\n\n\n
\n\nRedirect 301 \/old-page \/new-page<\/em><\/p>\n<\/blockquote>\n<\/div><\/div>\n\n\n\nor<\/p>\n\n\n\n
\nRedirect 301 \/old-page\/ https:\/\/your-site.com\/new-page<\/em><\/p>\n<\/blockquote>\n\n\n\nYou can also redirect with the module mod_rewrite:<\/em><\/strong><\/p>\n\n\n\n\nRewriteCond %{REQUEST_URI} ^\/old-page\/$<\/p>\n\n\n\n
RewriteRule ^.*$ http:\/\/your-site.com\/new-page\/? [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect from the domain without WWW to the domain with WWW<\/span><\/h3>\n\n\n\nIt is necessary for gluing duplicate pages like sitexample.com and www.sitexample.com when you decide to make the leading site with the WWW prefix.<\/p>\n\n\n\n
\nRewriteCond %{HTTP_HOST} ^site\\.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/www.site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect from the domain with WWW to the domain without WWW<\/span><\/h3>\n\n\n\n\nRewriteCond %{HTTP_HOST} ^www.site.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect using RewriteRule<\/span><\/h3>\n\n\n\nRewriteRule is a directive of the .htaccess file, the mod_rewrite module, which defines URL conversion rules. Use it when you need to perform a mass 301 redirect.<\/p>\n\n\n\n
By default, the mod_rewrite module is disabled. To enable it, you need to use the directives:<\/p>\n\n\n\n
\nRewriteEngine on<\/p>\n\n\n\n
RewriteBase \/<\/p>\n<\/blockquote>\n\n\n\n
The principle of the module is built using the rules according to which the URL is converted.<\/p>\n\n\n\n
Two directives serve to define the rules:<\/p>\n\n\n\n
\n- RewriteCond<\/strong> – defines the conditions under which the RewriteRule directive will be triggered. The number of RewriteCond conditions before the RewriteRule directive is unlimited.<\/li>\n\n\n\n
- RewriteRule<\/strong> – sets the URL conversion rule.<\/li>\n<\/ul>\n\n\n\n
Example of RewriteRule for redirection:<\/p>\n\n\n\n
\nRewriteRule ^my-old-url\\.html$ \/my-new-url.html [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
\n- The first part of the rule specifies the condition under which the URL conversion will be performed.<\/li>\n\n\n\n
- The second part of the rule determines what the URL should be converted to.<\/li>\n\n\n\n
- The third part of the rule (in square brackets) contains additional options called flags. It is optional. In our case, it includes the redirect code – R=301, as well as the flag L – “last rule,” which says to stop the URL conversion process if it matches the rule.<\/li>\n<\/ul>\n\n\n\n
<\/span>301 redirect from domain to domain<\/span><\/h3>\n\n\n\nUsed when it is necessary to stick together old and new pages after changing the domain.<\/p>\n\n\n\n
\nRewriteCond %{HTTP_HOST} ^old-site.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/www.new-site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect to HTTPS from HTTP<\/span><\/h3>\n\n\n\n\nRewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirects from a page with a slash to a URL without a slash, and vice versa<\/span><\/h3>\n\n\n\nOn a URL without “\/”<\/strong><\/p>\n\n\n\n\nRewriteCond %{REQUEST_FILENAME} !-d<\/p>\n\n\n\n
RewriteCond %{REQUEST_URI} ^(.+)\/$<\/p>\n\n\n\n
RewriteRule ^(.+)\/$ \/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
On a URL with a “\/”<\/strong><\/p>\n\n\n\n\nRewriteCond %{REQUEST_URI} \/+[^.]+$<\/p>\n\n\n\n
RewriteRule ^(.+[^\/])$ %{REQUEST_URI}\/ [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
But even with a ready-made code for different needs, something could go wrong, and the best option is to contact a programmer.<\/strong> Since it is possible that you accidentally catch another type of page or dynamic data that you need or something else, it is essential to check all pages after implementing the code.<\/strong><\/p>\n\n\n\n<\/span>How to set up a 301 redirect in WordPress?<\/span><\/h2>\n\n\n\nAt the beginning of 2019, approximately 75 million sites were implemented using CMS WordPress. It allows you to solve a wide range of tasks with the help of plugins. This is also true for 301 redirects. If you need to redirect from one page to another, it is unnecessary to involve a programmer. It will be enough to use a plugin<\/strong>.<\/p>\n\n\n\n<\/span>301 redirect with the 301 Redirects plugin<\/span><\/h3>\n\n\n\n\n- Setup plugin<\/a> and install it in WordPress<\/li>\n\n\n\n
- Configure the plugin. To do this, go to the “Settings” tab with the plugin’s name.<\/li>\n<\/ol>\n\n\n\n
![\"\"\/](\"https:\/\/lh4.googleusercontent.com\/yFimO-_znkfZn9GAkToxmMU5ORjKUlnuFi7b-pvEMT-E1JqR-6n0k4QBMjc_gW237WMtTE5USx4fADehA17raz0mTlZwvw8YISMYlV2QAToKTIAz6iqd1Bh0T71N32lX7yxok4tkTu3EZfrb5igf6OK9ROh6FwnfgMEeKtOOi6AawcoAj4qgQSAzElDN0w\")
<\/figure>\n\n\n\n3. Select the type of redirect. The plugin allows you to implement different types of redirects: 301, 302, 307. To implement a redirect, you need to select the desired redirect type from the menu in the Redirect Rules tab:<\/p>\n\n\n\n![\"\"\/](\"https:\/\/lh6.googleusercontent.com\/gxLha0ieJdAT84T_j-jLJhHNM7Wq841jEWZ982z8B-tK8c67pIYTyQvFnHUH7wCGfF6AW9iMb9Ue4TAA6UO0W2m111tOPLOorXc3z2_zCvhGo5BQK_ASEJy_cBEESX9M3DwOm84F2qwJ7izsOQBTco2gNgfXVugsSF4-LJ7uzJWqPQ8MkFjeDysI0uDxtg\")
<\/figure>\n\n\n\n4. Next, you need to specify the relative link of the page from which to perform the redirect and the link to which it should be committed. Then click the “save” button.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/lh4.googleusercontent.com\/d84v1XWZF1HbNmbOgAgxl8ZvjjX-NIfE2200k3ua7gT67PYICv9iTQ3-IoyPSqhUvuLzTFhFv3AaJXHS0CfHIN0REv9LQLw8OBia_5iEmPJSxQz_X9JS1pRUAsfDhrJFfNVc36MfVZmNOaSgmMpe54379t_Cd0nVAHFzA7TEZIgKMNZX908bD6X3EYgn0g\")
<\/figure>\n\n\n\nYou can check the result after saving. To do this, enter the URL from which you made the redirect in the address bar. You should be redirected to the page whose URL you specified in the second field.<\/p>\n\n\n\n
Important!<\/strong> <\/span>If you have any problems with the redirect, make sure that all fields are filled in, and the cache is cleared. To do this, go to the Tools & Options tab and click on the Empty Cache<\/strong> button.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/lh3.googleusercontent.com\/rNhq_hYXR9m3oyIKuCPNrvRurozMUp_VP7Luqnsm4G9R6iqNzBafVioXHY7RwGqKlH6ZCHx-Jdad8bwCFXUkrD7LdXEOpxlZhlyVJmADyl2BSaZcBw4hWpe0jxFAdzUVQau9jK9SaripeyhcYgIsBbGtwPlpzEXikEBXqDVDrkpjx-bLrHVQEDdy8bM5Qg\")
<\/figure>\n\n\n\nAfter clearing the cache, recheck the redirect.<\/p>\n\n\n\n
<\/span>When should you avoid 301 redirects?<\/span><\/h2>\n\n\n\nNo one should use a permanent redirect for temporary solutions; it is evident from its name. For temporary movement, use 302 Redirect Moved Temporarily<\/strong>. In this case, there will be no gluing of pages, and the site owner can restore the page with the redirect at any time.<\/p>\n\n\n\n
If there are any problems with your domain, for example, filters or bans, and you decide to change the address of the site (domain), you should not make a 301 redirect<\/a> from the old domain to the new one – as a result, you will stick all the problems of the old domain to the new one. In the end, nothing will change.<\/p>\n\n\n\n<\/span>Other Types of 3xx Redirects<\/span><\/h2>\n\n\n\n<\/span>302 Redirect \u2013 Moved Temporarily<\/span><\/h3>\n\n\n\nSuitable for cases when some page or section of the site is under technical maintenance. You can redirect users to a copy of the old page version at this time. It is a signal for the search engine that removing the donor page from the index is unnecessary, and there is no need to index the acceptor page. <\/p>\n\n\n\n
However, if the 302 redirects stand for a long time, the search bot may consider this a permanent move and make appropriate changes in the index.<\/p>\n\n\n\n
We know about the practice when online shop owners set up a 302 redirect for a product that is out of stock. We don’t recommend doing this. It’s better to specify that the product is out of stock now and add a block with similar or exciting products on this page.<\/p>\n\n\n\n
<\/span>303 and 307 Redirect <\/span><\/h3>\n\n\n\n307 redirects (Temporary Redirect) is an exact copy of the 303 (Found) redirect for search engines. It is a temporary redirection of traffic to a new page with all the parameters of the original page.<\/p>\n\n\n\n
These types are used when there is a need to redirect the user to another page that does not contain an exact answer but is a partial replacement of the search query.<\/p>\n\n\n\n
303 and 307 redirects have been created to differentiate between the two supposed features of the 302 response code. In practice, no SEOs intentionally use either of them. <\/p>\n\n\n\n
<\/span>304 Redirect \u2013 Not Modified <\/span><\/h3>\n\n\n\nBrowsers can send a request that asks if the resource has been modified. We can assist the browser by controlling The Last-Modified and If-Modified-Since headers to enter information about the last editing of a web page.<\/p>\n\n\n\n
The primary purpose of using If-Modified-Since and Last-Modified headers is to ensure that cached information is updated efficiently. Cache management will help improve page load speeds, as well as improve overall website performance and, thus, user experience.<\/p>\n\n\n\n
From an SEO point of view, monitoring cache updates is very important because it can improve the crawling and indexing of the site.<\/p>\n\n\n\n
You do remember that each site has a specific crawling budget, and the task of the optimizer is to use it as effectively as possible.<\/p>\n\n\n\n
The 304 redirect is the most helpful for owners of large sites who meet problems with scanning. The search robot scans pages that are non-priority and may never get to the necessary content. For example, the ‘About us’ page is frequently scanned because there is a link to it on every site page in the header or footer. Therefore, the robot may consider it important, but it is not.<\/p>\n\n\n\n
By configuring If-Modified-Since and Last-Modified, you can show the robot which pages you updated and which have remained unchanged.<\/p>\n\n\n\n
<\/span>305 Redirect \u2013 Use Proxy <\/span><\/h3>\n\n\n\n305 redirects occur when the requested resource is available only through a proxy server. The web browser is expected to repeat the request through the proxy.<\/p>\n\n\n\n
Some browsers (Mozilla, Internet Explorer) mismanage this status. Most likely, they regard the fact that the request is not sent directly to the server as insecure.<\/p>\n\n\n\n
Programmers use proxy servers for various purposes, ranging from anonymity to the need to cache content to speed up page loading.<\/p>\n\n\n\n
We note that many search engines ignore this code and, in fact, abandon it.<\/p>\n\n\n\n
<\/span>306 Redirect \u2013 Switch Proxy<\/span><\/h3>\n\n\n\nInitially, the 306 response code signaled that the client must use a specific proxy server. It is no longer relevant and remains reserved.<\/p>\n\n\n\n
<\/span>308 Redirect \u2013 Permanent Redirect<\/span><\/h3>\n\n\n\nThis response code is similar to a 301 redirect, with the only difference being that it does not allow you to change the request method from POST to GET. It’s also automatically cached and passes internal weight to the new page.<\/p>\n\n\n\n
It’s worth noting that this response code is experimental.<\/p>\n\n\n\n
There are other use cases for the 308 redirect. For example, Google Drive redirects with a 308 response code to show that a data download was interrupted.<\/p>\n\n\n\n
<\/span>Which redirects should SEO experts use?<\/span><\/h3>\n\n\n\nWe work with the following redirects: 301, 302, 304, 307, 308. But we actually use 301, 304, and 302<\/strong>. Can you guess why?<\/p>\n\n\n\nYes, because all browsers, clients, and search engines do not yet love the 307 and 308 server response codes. So let’s communicate with them in a language they understand.<\/p>\n\n\n\n
<\/span>Most Common Mistakes With Redirects<\/span><\/span><\/h2>\n\n\n\n<\/span>Redirect robots.txt<\/span><\/h3>\n\n\n\nWhen changing a site’s domain, the owner sometimes sets up a mass redirect of all pages and files, including the robots.txt file. But, to glue domains faster for search engines, the robots.txt on the old domain should be available for scanning<\/strong>, not redirected.<\/p>\n\n\n\n<\/span>The acceptor page is not relevant to the donor.<\/span><\/h3>\n\n\n\nThe main advantage of 301 redirects for SEO is the transfer of weight and authority from the old page to the new page. However, if you put a redirect to a page that is irrelevant to the donor – with different information, a completely different product – then the search engines will consider it wrong. The weight will not be fully transferred. In some cases, the search engine will not consider it a redirect at all.<\/p>\n\n\n\n
<\/span>Redirect chains<\/span><\/h3>\n\n\n\n![\"\"](\"https:\/\/site.wstatic.net\/blog\/wp-content\/uploads\/2023\/02\/Redirect_chains-1200x550.png\")
<\/figure>\n\n\n\nWe can often encounter situations of multiple-page redirects.<\/p>\n\n\n\n
For example, you delete page A and redirect to page B. Later you delete B and redirect to page C. As a result, a user who wants to go to page A is first redirected to page B and then to C. The robot may not understand why you’re doing this.<\/p>\n\n\n\n
Ideally, the redirect on page A should be fixed by putting it right on page C. And here, the robot is happy – the redirect is done correctly.<\/p>\n\n\n\n
<\/span>What’s wrong with redirect chains:<\/span><\/h4>\n\n\n\n\n- They slow down the opening of the final page, worsen the behavioral performance of the site and Core Web Vitals;<\/li>\n\n\n\n
- Search robots can handle no more than five redirects;<\/li>\n\n\n\n
- Increase the risk of redirect loops leading to the page’s inaccessibility.<\/li>\n<\/ul>\n\n\n\n
You can detect redirect chains with WebCEO\u2019s Technical Audit Tool<\/a> for free. Just add your project, and it will be automatically scanned. Afterward, move to the Site Health menu and check if your site has any redirect chains.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/lh4.googleusercontent.com\/Hfi1NJwF4g_-11DFEYq5yo2AVVIolTVGqlTuppBLZIR0q5OqFoBjw58duQKdIoZezKs_aj3mRRSzwpAjtSHub0cxHEL9y-qzaP_n1GzA-k_VeFTclxpHuPF3_xDqjMcNfJyqgawo40UmomzR-LV4pNP-ow4Va8GNKnxzDK19YPaX4LgkZ_o1EqYC77-LZg\")
<\/figure>\n\n\n\n<\/span>Redirect loops<\/span><\/h3>\n\n\n\n![\"Redirect](\"https:\/\/site.wstatic.net\/blog\/wp-content\/uploads\/2023\/01\/Redirect_loops.png\")
<\/figure>\n\n\n\nA fictional example: you have set up a redirect from page A to page B and from there to page C. But page C is already redirected to page A. We get a vicious redirect loop. All URLs in the chain become inaccessible to users and search engines.<\/p>\n\n\n\n
In practice, redirect loops<\/a> often occur when mass redirect rules are confused: pages with and without the slash, with and without WWW, etc.<\/p>\n\n\n\nYou should avoid redirecting loops because they negatively affect your ranking by increasing the content loading time, wasting crawling budgets, and decreasing link weight.<\/p>\n\n\n\n
<\/span>Pages with code 301 remained in the sitemap.<\/span><\/h3>\n\n\n\nYou must remove URLs with 301 redirects from sitemap.xml. Otherwise, the search robot will spend its crawling budget to crawl these pages.<\/p>\n\n\n\n
<\/span>Redirect to the 404 page<\/span><\/h3>\n\n\n\nCheck the relevance of redirects on the site regularly, especially after cardinal restructuring and removal of irrelevant pages. It often happens that you put a redirect, but after some time, the URL acceptor was deleted, or it became inaccessible because of technical errors. As a result, redirects lead nowhere to a broken link.<\/p>\n\n\n\n
<\/span>Unusual Ways to Create Redirects (Redirects via meta refresh, javascript, and PHP)<\/span><\/h2>\n\n\n\n<\/span>PHP redirects<\/span><\/h3>\n\n\n\nThe main feature of the redirect in PHP<\/a> is that redirection is not written in the page’s code but with the help of a script on the server. This reduces the susceptibility to search engine filters<\/strong>. You need to find the PHP file in the site’s root folder and enter a line of code for the appropriate redirect.<\/p>\n\n\n\nThis type is slower than .htaccess<\/strong>, but if you have hundreds of pages that need to be redirected and want to do it selectively rather than all of them, PHP might be the best choice.<\/p>\n\n\n\n<\/span>JavaScript redirects<\/span><\/h3>\n\n\n\nThis differs from the previous ones in that the redirection takes place on the browser side<\/strong>, not the server side. Therefore, the redirection speed is drastically reduced because the script must fully load to perform actions.<\/p>\n\n\n\nWhen do you use this? For example, when you move to a new site, it displays a message<\/strong> like “you will now be automatically redirected to our new site.”<\/p>\n\n\n\nThe JavaScript redirect<\/a> should be set up in the page’s source code from which the redirect comes by changing the text between the <head>-<\/head> tags.<\/p>\n\n\n\n<\/span>HTML redirect or meta-refresh<\/span><\/h3>\n\n\n\nA browser type of redirect. It is a meta tag, which usually specifies the delay time and the page to which the user is redirected.<\/p>\n\n\n\n
Example code for a meta refresh tag with a redirect delay of 2 seconds:<\/p>\n\n\n\n
<meta http-equiv=”refresh” content=”2;https:\/\/livepage.pro”><\/p>\n\n\n\n
The meta-refresh has a bad reputation among search engines<\/strong>, as this method has often been used to redirect to doorways. In addition, meta-refresh has other disadvantages:<\/p>\n\n\n\n\n- Is not supported by all browsers;<\/li>\n\n\n\n
- Leads to crawl errors. The search robot does not crawl the page on which the refresh meta tag is located but goes directly to the one to which the redirection leads;<\/li>\n\n\n\n
- Can be defined by Google as spam with appropriate sanctions;<\/li>\n\n\n\n
- Google bots may ignore pages with this meta tag and not index them.<\/li>\n<\/ul>\n\n\n\n
However, in some cases, the use of such a redirect may be appropriate, for example, for:<\/p>\n\n\n\n
\n- Redirecting the visitor to the gratitude page after placing an order;<\/li>\n\n\n\n
- “Backing up” redirects implemented in JavaScript – if the visitor’s browser does not support scripts;<\/li>\n\n\n\n
- Redirecting the visitor to the page with links to download the correct browsers – if his browser displays your site with errors.<\/li>\n<\/ul>\n\n\n\n
<\/span>Summary<\/span><\/h2>\n\n\n\n\n- A 301 redirect is a significant SEO optimization tool that improves the user experience and communication with search engine robots. It allows you to save the weight of pages, glue them together, save traffic, and retain the user. However, it\u2019s crucial that you use the correct type of redirect status code for your purpose to get the correct outcome.<\/li>\n\n\n\n
- There are different ways to implement 301 redirects. The most common are edits in the web server configuration file (.htaccess). When implementing 301 redirects through the .htaccess file, site owners use classic 301 redirects or the RewriteRule directive.<\/li>\n\n\n\n
- It is unnecessary to involve a programmer in implementing 301 redirects on different CRMs. The task is easily solved using modules or platform features.<\/li>\n\n\n\n
- There are many different redirects, but 301, 302, and 304 will affect your SEO 98% of the time.<\/li>\n\n\n\n
- Avoid redirect chains and redirect loops, as they can seriously worsen your rankings.<\/li>\n\n\n\n
- Be very careful, and be active in checking the result of your settings. When working with redirects, it is easy to make mistakes and affect other pages or files. <\/li>\n<\/ol>\n\n\n\n
To make sure your site is search-engine friendly, check your site for technical issues and redirects with the help of the WebCEO Auditor Tool.\u00a0<\/a><\/p>\n\n\n\n\r\n
<\/span>What is a 301 redirect in SEO?<\/span><\/h2>\n\n\n\n301 redirect benefits for SEO:<\/strong><\/p>\n\n\n\n\n- Save traffic;<\/li>\n\n\n\n
- Prevent the loss of PageRank;<\/li>\n\n\n\n
- Get rid of duplicate pages;<\/li>\n\n\n\n
- Eliminate the presence of low-quality pages in the search results;<\/li>\n\n\n\n
- Redirect the crawler (search bot) and the user from an irrelevant page or with a 404 server response code.<\/li>\n<\/ul>\n\n\n\n
From a user experience standpoint, 301 redirects are helpful because they allow redirecting traffic to related products if the one they are looking for is deleted. Such practice reduces the probability of user bounce.<\/strong><\/p>\n\n\n\nSome time after you set up the redirect, the search engine will update its index, replacing the old page address with the new one. Browsers and other types of clients will cache the new URL and automatically follow the redirect directly without checking the original for subsequent requests. Saved bookmarks are also usually updated.<\/p>\n\n\n\n
<\/span>How to set up 301 redirects?<\/span><\/h2>\n\n\n\nThere are many ways to make a 301 redirect: .htaccess, PHP, javascript, server settings, <\/strong>and others. We recommend not using all methods at once. There is too high a probability of discrepancies between different processes. The most commonly used way of configuration is through .htaccess. <\/p>\n\n\n\n<\/span>What is the .htaccess file for, and how to find it?<\/span><\/h3>\n\n\n\nThe .htaccess file is a configuration file that defines the rules of the web server in the directories and subdirectories where it is located<\/strong>. Most often, it will be the root folder of your site.<\/p>\n\n\n\nIf you can’t find<\/strong> the .htaccess, there are a few options:<\/p>\n\n\n\n\n- The file has a different name. It is scarce, but it is possible. The actual name can be clarified with the hosting provider: it can be, for example, .config, .htaccess.http, access.conf.<\/li>\n\n\n\n
- The file still needs to be created. This is the most common case. It is necessary to create a .htaccess file and write the redirection directives into it later.<\/li>\n<\/ol>\n\n\n\n
Further info on .htaccess: https:\/\/developer.wordpress.org\/advanced-administration\/server\/web-server\/httpd\/<\/a><\/p>\n\n\n\n<\/span>How to create a new .htaccess file?<\/span><\/h3>\n\n\n\n\n- Create an empty text file with a .txt extension.<\/li>\n\n\n\n
- Rename it by removing the name and adding the extension .htaccess. <\/li>\n\n\n\n
- If you work on macOS, a file with no name will not be visible. Then give it any name you want, and rename it after it is uploaded to the server.<\/li>\n<\/ol>\n\n\n\n
<\/span>Setting up 301 redirects in .htaccess with examples<\/span><\/h2>\n\n\n\nWe will use the conventional addresses of sites and pages to show you 301 redirect examples – <\/em>you will need to replace them with yours.<\/em><\/strong><\/p>\n\n\n\n<\/span>301 redirect of one page<\/span><\/h3>\n\n\n\nThe easiest way is to use the Redirect directive. Try one of the options:<\/p>\n\n\n\n
\n\nRedirect 301 \/old-page \/new-page<\/em><\/p>\n<\/blockquote>\n<\/div><\/div>\n\n\n\nor<\/p>\n\n\n\n
\nRedirect 301 \/old-page\/ https:\/\/your-site.com\/new-page<\/em><\/p>\n<\/blockquote>\n\n\n\nYou can also redirect with the module mod_rewrite:<\/em><\/strong><\/p>\n\n\n\n\nRewriteCond %{REQUEST_URI} ^\/old-page\/$<\/p>\n\n\n\n
RewriteRule ^.*$ http:\/\/your-site.com\/new-page\/? [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect from the domain without WWW to the domain with WWW<\/span><\/h3>\n\n\n\nIt is necessary for gluing duplicate pages like sitexample.com and www.sitexample.com when you decide to make the leading site with the WWW prefix.<\/p>\n\n\n\n
\nRewriteCond %{HTTP_HOST} ^site\\.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/www.site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect from the domain with WWW to the domain without WWW<\/span><\/h3>\n\n\n\n\nRewriteCond %{HTTP_HOST} ^www.site.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect using RewriteRule<\/span><\/h3>\n\n\n\nRewriteRule is a directive of the .htaccess file, the mod_rewrite module, which defines URL conversion rules. Use it when you need to perform a mass 301 redirect.<\/p>\n\n\n\n
By default, the mod_rewrite module is disabled. To enable it, you need to use the directives:<\/p>\n\n\n\n
\nRewriteEngine on<\/p>\n\n\n\n
RewriteBase \/<\/p>\n<\/blockquote>\n\n\n\n
The principle of the module is built using the rules according to which the URL is converted.<\/p>\n\n\n\n
Two directives serve to define the rules:<\/p>\n\n\n\n
\n- RewriteCond<\/strong> – defines the conditions under which the RewriteRule directive will be triggered. The number of RewriteCond conditions before the RewriteRule directive is unlimited.<\/li>\n\n\n\n
- RewriteRule<\/strong> – sets the URL conversion rule.<\/li>\n<\/ul>\n\n\n\n
Example of RewriteRule for redirection:<\/p>\n\n\n\n
\nRewriteRule ^my-old-url\\.html$ \/my-new-url.html [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
\n- The first part of the rule specifies the condition under which the URL conversion will be performed.<\/li>\n\n\n\n
- The second part of the rule determines what the URL should be converted to.<\/li>\n\n\n\n
- The third part of the rule (in square brackets) contains additional options called flags. It is optional. In our case, it includes the redirect code – R=301, as well as the flag L – “last rule,” which says to stop the URL conversion process if it matches the rule.<\/li>\n<\/ul>\n\n\n\n
<\/span>301 redirect from domain to domain<\/span><\/h3>\n\n\n\nUsed when it is necessary to stick together old and new pages after changing the domain.<\/p>\n\n\n\n
\nRewriteCond %{HTTP_HOST} ^old-site.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/www.new-site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect to HTTPS from HTTP<\/span><\/h3>\n\n\n\n\nRewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirects from a page with a slash to a URL without a slash, and vice versa<\/span><\/h3>\n\n\n\nOn a URL without “\/”<\/strong><\/p>\n\n\n\n\nRewriteCond %{REQUEST_FILENAME} !-d<\/p>\n\n\n\n
RewriteCond %{REQUEST_URI} ^(.+)\/$<\/p>\n\n\n\n
RewriteRule ^(.+)\/$ \/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
On a URL with a “\/”<\/strong><\/p>\n\n\n\n\nRewriteCond %{REQUEST_URI} \/+[^.]+$<\/p>\n\n\n\n
RewriteRule ^(.+[^\/])$ %{REQUEST_URI}\/ [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
But even with a ready-made code for different needs, something could go wrong, and the best option is to contact a programmer.<\/strong> Since it is possible that you accidentally catch another type of page or dynamic data that you need or something else, it is essential to check all pages after implementing the code.<\/strong><\/p>\n\n\n\n<\/span>How to set up a 301 redirect in WordPress?<\/span><\/h2>\n\n\n\nAt the beginning of 2019, approximately 75 million sites were implemented using CMS WordPress. It allows you to solve a wide range of tasks with the help of plugins. This is also true for 301 redirects. If you need to redirect from one page to another, it is unnecessary to involve a programmer. It will be enough to use a plugin<\/strong>.<\/p>\n\n\n\n<\/span>301 redirect with the 301 Redirects plugin<\/span><\/h3>\n\n\n\n\n- Setup plugin<\/a> and install it in WordPress<\/li>\n\n\n\n
- Configure the plugin. To do this, go to the “Settings” tab with the plugin’s name.<\/li>\n<\/ol>\n\n\n\n
<\/figure>\n\n\n\n3. Select the type of redirect. The plugin allows you to implement different types of redirects: 301, 302, 307. To implement a redirect, you need to select the desired redirect type from the menu in the Redirect Rules tab:<\/p>\n\n\n\n<\/figure>\n\n\n\n4. Next, you need to specify the relative link of the page from which to perform the redirect and the link to which it should be committed. Then click the “save” button.<\/p>\n\n\n\n<\/figure>\n\n\n\nYou can check the result after saving. To do this, enter the URL from which you made the redirect in the address bar. You should be redirected to the page whose URL you specified in the second field.<\/p>\n\n\n\n
Important!<\/strong> <\/span>If you have any problems with the redirect, make sure that all fields are filled in, and the cache is cleared. To do this, go to the Tools & Options tab and click on the Empty Cache<\/strong> button.<\/p>\n\n\n\n<\/figure>\n\n\n\nAfter clearing the cache, recheck the redirect.<\/p>\n\n\n\n
<\/span>When should you avoid 301 redirects?<\/span><\/h2>\n\n\n\nNo one should use a permanent redirect for temporary solutions; it is evident from its name. For temporary movement, use 302 Redirect Moved Temporarily<\/strong>. In this case, there will be no gluing of pages, and the site owner can restore the page with the redirect at any time.<\/p>\n\n\n\n
If there are any problems with your domain, for example, filters or bans, and you decide to change the address of the site (domain), you should not make a 301 redirect<\/a> from the old domain to the new one – as a result, you will stick all the problems of the old domain to the new one. In the end, nothing will change.<\/p>\n\n\n\n<\/span>Other Types of 3xx Redirects<\/span><\/h2>\n\n\n\n<\/span>302 Redirect \u2013 Moved Temporarily<\/span><\/h3>\n\n\n\nSuitable for cases when some page or section of the site is under technical maintenance. You can redirect users to a copy of the old page version at this time. It is a signal for the search engine that removing the donor page from the index is unnecessary, and there is no need to index the acceptor page. <\/p>\n\n\n\n
However, if the 302 redirects stand for a long time, the search bot may consider this a permanent move and make appropriate changes in the index.<\/p>\n\n\n\n
We know about the practice when online shop owners set up a 302 redirect for a product that is out of stock. We don’t recommend doing this. It’s better to specify that the product is out of stock now and add a block with similar or exciting products on this page.<\/p>\n\n\n\n
<\/span>303 and 307 Redirect <\/span><\/h3>\n\n\n\n307 redirects (Temporary Redirect) is an exact copy of the 303 (Found) redirect for search engines. It is a temporary redirection of traffic to a new page with all the parameters of the original page.<\/p>\n\n\n\n
These types are used when there is a need to redirect the user to another page that does not contain an exact answer but is a partial replacement of the search query.<\/p>\n\n\n\n
303 and 307 redirects have been created to differentiate between the two supposed features of the 302 response code. In practice, no SEOs intentionally use either of them. <\/p>\n\n\n\n
<\/span>304 Redirect \u2013 Not Modified <\/span><\/h3>\n\n\n\nBrowsers can send a request that asks if the resource has been modified. We can assist the browser by controlling The Last-Modified and If-Modified-Since headers to enter information about the last editing of a web page.<\/p>\n\n\n\n
The primary purpose of using If-Modified-Since and Last-Modified headers is to ensure that cached information is updated efficiently. Cache management will help improve page load speeds, as well as improve overall website performance and, thus, user experience.<\/p>\n\n\n\n
From an SEO point of view, monitoring cache updates is very important because it can improve the crawling and indexing of the site.<\/p>\n\n\n\n
You do remember that each site has a specific crawling budget, and the task of the optimizer is to use it as effectively as possible.<\/p>\n\n\n\n
The 304 redirect is the most helpful for owners of large sites who meet problems with scanning. The search robot scans pages that are non-priority and may never get to the necessary content. For example, the ‘About us’ page is frequently scanned because there is a link to it on every site page in the header or footer. Therefore, the robot may consider it important, but it is not.<\/p>\n\n\n\n
By configuring If-Modified-Since and Last-Modified, you can show the robot which pages you updated and which have remained unchanged.<\/p>\n\n\n\n
<\/span>305 Redirect \u2013 Use Proxy <\/span><\/h3>\n\n\n\n305 redirects occur when the requested resource is available only through a proxy server. The web browser is expected to repeat the request through the proxy.<\/p>\n\n\n\n
Some browsers (Mozilla, Internet Explorer) mismanage this status. Most likely, they regard the fact that the request is not sent directly to the server as insecure.<\/p>\n\n\n\n
Programmers use proxy servers for various purposes, ranging from anonymity to the need to cache content to speed up page loading.<\/p>\n\n\n\n
We note that many search engines ignore this code and, in fact, abandon it.<\/p>\n\n\n\n
<\/span>306 Redirect \u2013 Switch Proxy<\/span><\/h3>\n\n\n\nInitially, the 306 response code signaled that the client must use a specific proxy server. It is no longer relevant and remains reserved.<\/p>\n\n\n\n
<\/span>308 Redirect \u2013 Permanent Redirect<\/span><\/h3>\n\n\n\nThis response code is similar to a 301 redirect, with the only difference being that it does not allow you to change the request method from POST to GET. It’s also automatically cached and passes internal weight to the new page.<\/p>\n\n\n\n
It’s worth noting that this response code is experimental.<\/p>\n\n\n\n
There are other use cases for the 308 redirect. For example, Google Drive redirects with a 308 response code to show that a data download was interrupted.<\/p>\n\n\n\n
<\/span>Which redirects should SEO experts use?<\/span><\/h3>\n\n\n\nWe work with the following redirects: 301, 302, 304, 307, 308. But we actually use 301, 304, and 302<\/strong>. Can you guess why?<\/p>\n\n\n\nYes, because all browsers, clients, and search engines do not yet love the 307 and 308 server response codes. So let’s communicate with them in a language they understand.<\/p>\n\n\n\n
<\/span>Most Common Mistakes With Redirects<\/span><\/span><\/h2>\n\n\n\n<\/span>Redirect robots.txt<\/span><\/h3>\n\n\n\nWhen changing a site’s domain, the owner sometimes sets up a mass redirect of all pages and files, including the robots.txt file. But, to glue domains faster for search engines, the robots.txt on the old domain should be available for scanning<\/strong>, not redirected.<\/p>\n\n\n\n<\/span>The acceptor page is not relevant to the donor.<\/span><\/h3>\n\n\n\nThe main advantage of 301 redirects for SEO is the transfer of weight and authority from the old page to the new page. However, if you put a redirect to a page that is irrelevant to the donor – with different information, a completely different product – then the search engines will consider it wrong. The weight will not be fully transferred. In some cases, the search engine will not consider it a redirect at all.<\/p>\n\n\n\n
<\/span>Redirect chains<\/span><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe can often encounter situations of multiple-page redirects.<\/p>\n\n\n\n
For example, you delete page A and redirect to page B. Later you delete B and redirect to page C. As a result, a user who wants to go to page A is first redirected to page B and then to C. The robot may not understand why you’re doing this.<\/p>\n\n\n\n
Ideally, the redirect on page A should be fixed by putting it right on page C. And here, the robot is happy – the redirect is done correctly.<\/p>\n\n\n\n
<\/span>What’s wrong with redirect chains:<\/span><\/h4>\n\n\n\n\n- They slow down the opening of the final page, worsen the behavioral performance of the site and Core Web Vitals;<\/li>\n\n\n\n
- Search robots can handle no more than five redirects;<\/li>\n\n\n\n
- Increase the risk of redirect loops leading to the page’s inaccessibility.<\/li>\n<\/ul>\n\n\n\n
You can detect redirect chains with WebCEO\u2019s Technical Audit Tool<\/a> for free. Just add your project, and it will be automatically scanned. Afterward, move to the Site Health menu and check if your site has any redirect chains.<\/p>\n\n\n\n<\/figure>\n\n\n\n<\/span>Redirect loops<\/span><\/h3>\n\n\n\n<\/figure>\n\n\n\nA fictional example: you have set up a redirect from page A to page B and from there to page C. But page C is already redirected to page A. We get a vicious redirect loop. All URLs in the chain become inaccessible to users and search engines.<\/p>\n\n\n\n
In practice, redirect loops<\/a> often occur when mass redirect rules are confused: pages with and without the slash, with and without WWW, etc.<\/p>\n\n\n\nYou should avoid redirecting loops because they negatively affect your ranking by increasing the content loading time, wasting crawling budgets, and decreasing link weight.<\/p>\n\n\n\n
<\/span>Pages with code 301 remained in the sitemap.<\/span><\/h3>\n\n\n\nYou must remove URLs with 301 redirects from sitemap.xml. Otherwise, the search robot will spend its crawling budget to crawl these pages.<\/p>\n\n\n\n
<\/span>Redirect to the 404 page<\/span><\/h3>\n\n\n\nCheck the relevance of redirects on the site regularly, especially after cardinal restructuring and removal of irrelevant pages. It often happens that you put a redirect, but after some time, the URL acceptor was deleted, or it became inaccessible because of technical errors. As a result, redirects lead nowhere to a broken link.<\/p>\n\n\n\n
<\/span>Unusual Ways to Create Redirects (Redirects via meta refresh, javascript, and PHP)<\/span><\/h2>\n\n\n\n<\/span>PHP redirects<\/span><\/h3>\n\n\n\nThe main feature of the redirect in PHP<\/a> is that redirection is not written in the page’s code but with the help of a script on the server. This reduces the susceptibility to search engine filters<\/strong>. You need to find the PHP file in the site’s root folder and enter a line of code for the appropriate redirect.<\/p>\n\n\n\nThis type is slower than .htaccess<\/strong>, but if you have hundreds of pages that need to be redirected and want to do it selectively rather than all of them, PHP might be the best choice.<\/p>\n\n\n\n<\/span>JavaScript redirects<\/span><\/h3>\n\n\n\nThis differs from the previous ones in that the redirection takes place on the browser side<\/strong>, not the server side. Therefore, the redirection speed is drastically reduced because the script must fully load to perform actions.<\/p>\n\n\n\nWhen do you use this? For example, when you move to a new site, it displays a message<\/strong> like “you will now be automatically redirected to our new site.”<\/p>\n\n\n\nThe JavaScript redirect<\/a> should be set up in the page’s source code from which the redirect comes by changing the text between the <head>-<\/head> tags.<\/p>\n\n\n\n<\/span>HTML redirect or meta-refresh<\/span><\/h3>\n\n\n\nA browser type of redirect. It is a meta tag, which usually specifies the delay time and the page to which the user is redirected.<\/p>\n\n\n\n
Example code for a meta refresh tag with a redirect delay of 2 seconds:<\/p>\n\n\n\n
<meta http-equiv=”refresh” content=”2;https:\/\/livepage.pro”><\/p>\n\n\n\n
The meta-refresh has a bad reputation among search engines<\/strong>, as this method has often been used to redirect to doorways. In addition, meta-refresh has other disadvantages:<\/p>\n\n\n\n\n- Is not supported by all browsers;<\/li>\n\n\n\n
- Leads to crawl errors. The search robot does not crawl the page on which the refresh meta tag is located but goes directly to the one to which the redirection leads;<\/li>\n\n\n\n
- Can be defined by Google as spam with appropriate sanctions;<\/li>\n\n\n\n
- Google bots may ignore pages with this meta tag and not index them.<\/li>\n<\/ul>\n\n\n\n
However, in some cases, the use of such a redirect may be appropriate, for example, for:<\/p>\n\n\n\n
\n- Redirecting the visitor to the gratitude page after placing an order;<\/li>\n\n\n\n
- “Backing up” redirects implemented in JavaScript – if the visitor’s browser does not support scripts;<\/li>\n\n\n\n
- Redirecting the visitor to the page with links to download the correct browsers – if his browser displays your site with errors.<\/li>\n<\/ul>\n\n\n\n
<\/span>Summary<\/span><\/h2>\n\n\n\n\n- A 301 redirect is a significant SEO optimization tool that improves the user experience and communication with search engine robots. It allows you to save the weight of pages, glue them together, save traffic, and retain the user. However, it\u2019s crucial that you use the correct type of redirect status code for your purpose to get the correct outcome.<\/li>\n\n\n\n
- There are different ways to implement 301 redirects. The most common are edits in the web server configuration file (.htaccess). When implementing 301 redirects through the .htaccess file, site owners use classic 301 redirects or the RewriteRule directive.<\/li>\n\n\n\n
- It is unnecessary to involve a programmer in implementing 301 redirects on different CRMs. The task is easily solved using modules or platform features.<\/li>\n\n\n\n
- There are many different redirects, but 301, 302, and 304 will affect your SEO 98% of the time.<\/li>\n\n\n\n
- Avoid redirect chains and redirect loops, as they can seriously worsen your rankings.<\/li>\n\n\n\n
- Be very careful, and be active in checking the result of your settings. When working with redirects, it is easy to make mistakes and affect other pages or files. <\/li>\n<\/ol>\n\n\n\n
To make sure your site is search-engine friendly, check your site for technical issues and redirects with the help of the WebCEO Auditor Tool.\u00a0<\/a><\/p>\n\n\n\n\r\n
- \n
- Save traffic;<\/li>\n\n\n\n
- Prevent the loss of PageRank;<\/li>\n\n\n\n
- Get rid of duplicate pages;<\/li>\n\n\n\n
- Eliminate the presence of low-quality pages in the search results;<\/li>\n\n\n\n
- Redirect the crawler (search bot) and the user from an irrelevant page or with a 404 server response code.<\/li>\n<\/ul>\n\n\n\n
From a user experience standpoint, 301 redirects are helpful because they allow redirecting traffic to related products if the one they are looking for is deleted. Such practice reduces the probability of user bounce.<\/strong><\/p>\n\n\n\n
Some time after you set up the redirect, the search engine will update its index, replacing the old page address with the new one. Browsers and other types of clients will cache the new URL and automatically follow the redirect directly without checking the original for subsequent requests. Saved bookmarks are also usually updated.<\/p>\n\n\n\n
<\/span>How to set up 301 redirects?<\/span><\/h2>\n\n\n\n
There are many ways to make a 301 redirect: .htaccess, PHP, javascript, server settings, <\/strong>and others. We recommend not using all methods at once. There is too high a probability of discrepancies between different processes. The most commonly used way of configuration is through .htaccess. <\/p>\n\n\n\n
<\/span>What is the .htaccess file for, and how to find it?<\/span><\/h3>\n\n\n\n
The .htaccess file is a configuration file that defines the rules of the web server in the directories and subdirectories where it is located<\/strong>. Most often, it will be the root folder of your site.<\/p>\n\n\n\n
If you can’t find<\/strong> the .htaccess, there are a few options:<\/p>\n\n\n\n
- \n
- The file has a different name. It is scarce, but it is possible. The actual name can be clarified with the hosting provider: it can be, for example, .config, .htaccess.http, access.conf.<\/li>\n\n\n\n
- The file still needs to be created. This is the most common case. It is necessary to create a .htaccess file and write the redirection directives into it later.<\/li>\n<\/ol>\n\n\n\n
Further info on .htaccess: https:\/\/developer.wordpress.org\/advanced-administration\/server\/web-server\/httpd\/<\/a><\/p>\n\n\n\n
<\/span>How to create a new .htaccess file?<\/span><\/h3>\n\n\n\n
- \n
- Create an empty text file with a .txt extension.<\/li>\n\n\n\n
- Rename it by removing the name and adding the extension .htaccess. <\/li>\n\n\n\n
- If you work on macOS, a file with no name will not be visible. Then give it any name you want, and rename it after it is uploaded to the server.<\/li>\n<\/ol>\n\n\n\n
<\/span>Setting up 301 redirects in .htaccess with examples<\/span><\/h2>\n\n\n\n
We will use the conventional addresses of sites and pages to show you 301 redirect examples – <\/em>you will need to replace them with yours.<\/em><\/strong><\/p>\n\n\n\n
<\/span>301 redirect of one page<\/span><\/h3>\n\n\n\n
The easiest way is to use the Redirect directive. Try one of the options:<\/p>\n\n\n\n
\n\n
Redirect 301 \/old-page \/new-page<\/em><\/p>\n<\/blockquote>\n<\/div><\/div>\n\n\n\n
or<\/p>\n\n\n\n
\n
Redirect 301 \/old-page\/ https:\/\/your-site.com\/new-page<\/em><\/p>\n<\/blockquote>\n\n\n\n
You can also redirect with the module mod_rewrite:<\/em><\/strong><\/p>\n\n\n\n
\n
RewriteCond %{REQUEST_URI} ^\/old-page\/$<\/p>\n\n\n\n
RewriteRule ^.*$ http:\/\/your-site.com\/new-page\/? [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect from the domain without WWW to the domain with WWW<\/span><\/h3>\n\n\n\n
It is necessary for gluing duplicate pages like sitexample.com and www.sitexample.com when you decide to make the leading site with the WWW prefix.<\/p>\n\n\n\n
\n
RewriteCond %{HTTP_HOST} ^site\\.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/www.site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect from the domain with WWW to the domain without WWW<\/span><\/h3>\n\n\n\n
\n
RewriteCond %{HTTP_HOST} ^www.site.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect using RewriteRule<\/span><\/h3>\n\n\n\n
RewriteRule is a directive of the .htaccess file, the mod_rewrite module, which defines URL conversion rules. Use it when you need to perform a mass 301 redirect.<\/p>\n\n\n\n
By default, the mod_rewrite module is disabled. To enable it, you need to use the directives:<\/p>\n\n\n\n
\n
RewriteEngine on<\/p>\n\n\n\n
RewriteBase \/<\/p>\n<\/blockquote>\n\n\n\n
The principle of the module is built using the rules according to which the URL is converted.<\/p>\n\n\n\n
Two directives serve to define the rules:<\/p>\n\n\n\n
- \n
- RewriteCond<\/strong> – defines the conditions under which the RewriteRule directive will be triggered. The number of RewriteCond conditions before the RewriteRule directive is unlimited.<\/li>\n\n\n\n
- RewriteRule<\/strong> – sets the URL conversion rule.<\/li>\n<\/ul>\n\n\n\n
Example of RewriteRule for redirection:<\/p>\n\n\n\n
\n
RewriteRule ^my-old-url\\.html$ \/my-new-url.html [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
- \n
- The first part of the rule specifies the condition under which the URL conversion will be performed.<\/li>\n\n\n\n
- The second part of the rule determines what the URL should be converted to.<\/li>\n\n\n\n
- The third part of the rule (in square brackets) contains additional options called flags. It is optional. In our case, it includes the redirect code – R=301, as well as the flag L – “last rule,” which says to stop the URL conversion process if it matches the rule.<\/li>\n<\/ul>\n\n\n\n
<\/span>301 redirect from domain to domain<\/span><\/h3>\n\n\n\n
Used when it is necessary to stick together old and new pages after changing the domain.<\/p>\n\n\n\n
\n
RewriteCond %{HTTP_HOST} ^old-site.com$ [NC]<\/p>\n\n\n\n
RewriteRule ^(.*)$ https:\/\/www.new-site.com\/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirect to HTTPS from HTTP<\/span><\/h3>\n\n\n\n
\n
RewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301]<\/p>\n<\/blockquote>\n\n\n\n
<\/span>301 redirects from a page with a slash to a URL without a slash, and vice versa<\/span><\/h3>\n\n\n\n
On a URL without “\/”<\/strong><\/p>\n\n\n\n
\n
RewriteCond %{REQUEST_FILENAME} !-d<\/p>\n\n\n\n
RewriteCond %{REQUEST_URI} ^(.+)\/$<\/p>\n\n\n\n
RewriteRule ^(.+)\/$ \/$1 [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
On a URL with a “\/”<\/strong><\/p>\n\n\n\n
\n
RewriteCond %{REQUEST_URI} \/+[^.]+$<\/p>\n\n\n\n
RewriteRule ^(.+[^\/])$ %{REQUEST_URI}\/ [R=301,L]<\/p>\n<\/blockquote>\n\n\n\n
But even with a ready-made code for different needs, something could go wrong, and the best option is to contact a programmer.<\/strong> Since it is possible that you accidentally catch another type of page or dynamic data that you need or something else, it is essential to check all pages after implementing the code.<\/strong><\/p>\n\n\n\n
<\/span>How to set up a 301 redirect in WordPress?<\/span><\/h2>\n\n\n\n
At the beginning of 2019, approximately 75 million sites were implemented using CMS WordPress. It allows you to solve a wide range of tasks with the help of plugins. This is also true for 301 redirects. If you need to redirect from one page to another, it is unnecessary to involve a programmer. It will be enough to use a plugin<\/strong>.<\/p>\n\n\n\n
<\/span>301 redirect with the 301 Redirects plugin<\/span><\/h3>\n\n\n\n
- \n
- Setup plugin<\/a> and install it in WordPress<\/li>\n\n\n\n
- Configure the plugin. To do this, go to the “Settings” tab with the plugin’s name.<\/li>\n<\/ol>\n\n\n\n
3. Select the type of redirect. The plugin allows you to implement different types of redirects: 301, 302, 307. To implement a redirect, you need to select the desired redirect type from the menu in the Redirect Rules tab:<\/p>\n\n\n\n
4. Next, you need to specify the relative link of the page from which to perform the redirect and the link to which it should be committed. Then click the “save” button.<\/p>\n\n\n\n
You can check the result after saving. To do this, enter the URL from which you made the redirect in the address bar. You should be redirected to the page whose URL you specified in the second field.<\/p>\n\n\n\n
Important!<\/strong> <\/span>If you have any problems with the redirect, make sure that all fields are filled in, and the cache is cleared. To do this, go to the Tools & Options tab and click on the Empty Cache<\/strong> button.<\/p>\n\n\n\n
After clearing the cache, recheck the redirect.<\/p>\n\n\n\n
<\/span>When should you avoid 301 redirects?<\/span><\/h2>\n\n\n\n
No one should use a permanent redirect for temporary solutions; it is evident from its name. For temporary movement, use 302 Redirect Moved Temporarily<\/strong>. In this case, there will be no gluing of pages, and the site owner can restore the page with the redirect at any time.<\/p>\n\n\n\n
If there are any problems with your domain, for example, filters or bans, and you decide to change the address of the site (domain), you should not make a 301 redirect<\/a> from the old domain to the new one – as a result, you will stick all the problems of the old domain to the new one. In the end, nothing will change.<\/p>\n\n\n\n<\/span>Other Types of 3xx Redirects<\/span><\/h2>\n\n\n\n
<\/span>302 Redirect \u2013 Moved Temporarily<\/span><\/h3>\n\n\n\n
Suitable for cases when some page or section of the site is under technical maintenance. You can redirect users to a copy of the old page version at this time. It is a signal for the search engine that removing the donor page from the index is unnecessary, and there is no need to index the acceptor page. <\/p>\n\n\n\n
However, if the 302 redirects stand for a long time, the search bot may consider this a permanent move and make appropriate changes in the index.<\/p>\n\n\n\n
We know about the practice when online shop owners set up a 302 redirect for a product that is out of stock. We don’t recommend doing this. It’s better to specify that the product is out of stock now and add a block with similar or exciting products on this page.<\/p>\n\n\n\n
<\/span>303 and 307 Redirect <\/span><\/h3>\n\n\n\n
307 redirects (Temporary Redirect) is an exact copy of the 303 (Found) redirect for search engines. It is a temporary redirection of traffic to a new page with all the parameters of the original page.<\/p>\n\n\n\n
These types are used when there is a need to redirect the user to another page that does not contain an exact answer but is a partial replacement of the search query.<\/p>\n\n\n\n
303 and 307 redirects have been created to differentiate between the two supposed features of the 302 response code. In practice, no SEOs intentionally use either of them. <\/p>\n\n\n\n
<\/span>304 Redirect \u2013 Not Modified <\/span><\/h3>\n\n\n\n
Browsers can send a request that asks if the resource has been modified. We can assist the browser by controlling The Last-Modified and If-Modified-Since headers to enter information about the last editing of a web page.<\/p>\n\n\n\n
The primary purpose of using If-Modified-Since and Last-Modified headers is to ensure that cached information is updated efficiently. Cache management will help improve page load speeds, as well as improve overall website performance and, thus, user experience.<\/p>\n\n\n\n
From an SEO point of view, monitoring cache updates is very important because it can improve the crawling and indexing of the site.<\/p>\n\n\n\n
You do remember that each site has a specific crawling budget, and the task of the optimizer is to use it as effectively as possible.<\/p>\n\n\n\n
The 304 redirect is the most helpful for owners of large sites who meet problems with scanning. The search robot scans pages that are non-priority and may never get to the necessary content. For example, the ‘About us’ page is frequently scanned because there is a link to it on every site page in the header or footer. Therefore, the robot may consider it important, but it is not.<\/p>\n\n\n\n
By configuring If-Modified-Since and Last-Modified, you can show the robot which pages you updated and which have remained unchanged.<\/p>\n\n\n\n
<\/span>305 Redirect \u2013 Use Proxy <\/span><\/h3>\n\n\n\n
305 redirects occur when the requested resource is available only through a proxy server. The web browser is expected to repeat the request through the proxy.<\/p>\n\n\n\n
Some browsers (Mozilla, Internet Explorer) mismanage this status. Most likely, they regard the fact that the request is not sent directly to the server as insecure.<\/p>\n\n\n\n
Programmers use proxy servers for various purposes, ranging from anonymity to the need to cache content to speed up page loading.<\/p>\n\n\n\n
We note that many search engines ignore this code and, in fact, abandon it.<\/p>\n\n\n\n
<\/span>306 Redirect \u2013 Switch Proxy<\/span><\/h3>\n\n\n\n
Initially, the 306 response code signaled that the client must use a specific proxy server. It is no longer relevant and remains reserved.<\/p>\n\n\n\n
<\/span>308 Redirect \u2013 Permanent Redirect<\/span><\/h3>\n\n\n\n
This response code is similar to a 301 redirect, with the only difference being that it does not allow you to change the request method from POST to GET. It’s also automatically cached and passes internal weight to the new page.<\/p>\n\n\n\n
It’s worth noting that this response code is experimental.<\/p>\n\n\n\n
There are other use cases for the 308 redirect. For example, Google Drive redirects with a 308 response code to show that a data download was interrupted.<\/p>\n\n\n\n
<\/span>Which redirects should SEO experts use?<\/span><\/h3>\n\n\n\n
We work with the following redirects: 301, 302, 304, 307, 308. But we actually use 301, 304, and 302<\/strong>. Can you guess why?<\/p>\n\n\n\n
Yes, because all browsers, clients, and search engines do not yet love the 307 and 308 server response codes. So let’s communicate with them in a language they understand.<\/p>\n\n\n\n
<\/span>Most Common Mistakes With Redirects<\/span><\/span><\/h2>\n\n\n\n
<\/span>Redirect robots.txt<\/span><\/h3>\n\n\n\n
When changing a site’s domain, the owner sometimes sets up a mass redirect of all pages and files, including the robots.txt file. But, to glue domains faster for search engines, the robots.txt on the old domain should be available for scanning<\/strong>, not redirected.<\/p>\n\n\n\n
<\/span>The acceptor page is not relevant to the donor.<\/span><\/h3>\n\n\n\n
The main advantage of 301 redirects for SEO is the transfer of weight and authority from the old page to the new page. However, if you put a redirect to a page that is irrelevant to the donor – with different information, a completely different product – then the search engines will consider it wrong. The weight will not be fully transferred. In some cases, the search engine will not consider it a redirect at all.<\/p>\n\n\n\n
<\/span>Redirect chains<\/span><\/h3>\n\n\n\n
<\/figure>\n\n\n\nWe can often encounter situations of multiple-page redirects.<\/p>\n\n\n\n
For example, you delete page A and redirect to page B. Later you delete B and redirect to page C. As a result, a user who wants to go to page A is first redirected to page B and then to C. The robot may not understand why you’re doing this.<\/p>\n\n\n\n
Ideally, the redirect on page A should be fixed by putting it right on page C. And here, the robot is happy – the redirect is done correctly.<\/p>\n\n\n\n
<\/span>What’s wrong with redirect chains:<\/span><\/h4>\n\n\n\n
- \n
- They slow down the opening of the final page, worsen the behavioral performance of the site and Core Web Vitals;<\/li>\n\n\n\n
- Search robots can handle no more than five redirects;<\/li>\n\n\n\n
- Increase the risk of redirect loops leading to the page’s inaccessibility.<\/li>\n<\/ul>\n\n\n\n
You can detect redirect chains with WebCEO\u2019s Technical Audit Tool<\/a> for free. Just add your project, and it will be automatically scanned. Afterward, move to the Site Health menu and check if your site has any redirect chains.<\/p>\n\n\n\n
<\/span>Redirect loops<\/span><\/h3>\n\n\n\n
<\/figure>\n\n\n\nA fictional example: you have set up a redirect from page A to page B and from there to page C. But page C is already redirected to page A. We get a vicious redirect loop. All URLs in the chain become inaccessible to users and search engines.<\/p>\n\n\n\n
In practice, redirect loops<\/a> often occur when mass redirect rules are confused: pages with and without the slash, with and without WWW, etc.<\/p>\n\n\n\n
You should avoid redirecting loops because they negatively affect your ranking by increasing the content loading time, wasting crawling budgets, and decreasing link weight.<\/p>\n\n\n\n
<\/span>Pages with code 301 remained in the sitemap.<\/span><\/h3>\n\n\n\n
You must remove URLs with 301 redirects from sitemap.xml. Otherwise, the search robot will spend its crawling budget to crawl these pages.<\/p>\n\n\n\n
<\/span>Redirect to the 404 page<\/span><\/h3>\n\n\n\n
Check the relevance of redirects on the site regularly, especially after cardinal restructuring and removal of irrelevant pages. It often happens that you put a redirect, but after some time, the URL acceptor was deleted, or it became inaccessible because of technical errors. As a result, redirects lead nowhere to a broken link.<\/p>\n\n\n\n
<\/span>Unusual Ways to Create Redirects (Redirects via meta refresh, javascript, and PHP)<\/span><\/h2>\n\n\n\n
<\/span>PHP redirects<\/span><\/h3>\n\n\n\n
The main feature of the redirect in PHP<\/a> is that redirection is not written in the page’s code but with the help of a script on the server. This reduces the susceptibility to search engine filters<\/strong>. You need to find the PHP file in the site’s root folder and enter a line of code for the appropriate redirect.<\/p>\n\n\n\n
This type is slower than .htaccess<\/strong>, but if you have hundreds of pages that need to be redirected and want to do it selectively rather than all of them, PHP might be the best choice.<\/p>\n\n\n\n
<\/span>JavaScript redirects<\/span><\/h3>\n\n\n\n
This differs from the previous ones in that the redirection takes place on the browser side<\/strong>, not the server side. Therefore, the redirection speed is drastically reduced because the script must fully load to perform actions.<\/p>\n\n\n\n
When do you use this? For example, when you move to a new site, it displays a message<\/strong> like “you will now be automatically redirected to our new site.”<\/p>\n\n\n\n
The JavaScript redirect<\/a> should be set up in the page’s source code from which the redirect comes by changing the text between the <head>-<\/head> tags.<\/p>\n\n\n\n
<\/span>HTML redirect or meta-refresh<\/span><\/h3>\n\n\n\n
A browser type of redirect. It is a meta tag, which usually specifies the delay time and the page to which the user is redirected.<\/p>\n\n\n\n
Example code for a meta refresh tag with a redirect delay of 2 seconds:<\/p>\n\n\n\n
<meta http-equiv=”refresh” content=”2;https:\/\/livepage.pro”><\/p>\n\n\n\n
The meta-refresh has a bad reputation among search engines<\/strong>, as this method has often been used to redirect to doorways. In addition, meta-refresh has other disadvantages:<\/p>\n\n\n\n
- \n
- Is not supported by all browsers;<\/li>\n\n\n\n
- Leads to crawl errors. The search robot does not crawl the page on which the refresh meta tag is located but goes directly to the one to which the redirection leads;<\/li>\n\n\n\n
- Can be defined by Google as spam with appropriate sanctions;<\/li>\n\n\n\n
- Google bots may ignore pages with this meta tag and not index them.<\/li>\n<\/ul>\n\n\n\n
However, in some cases, the use of such a redirect may be appropriate, for example, for:<\/p>\n\n\n\n
- \n
- Redirecting the visitor to the gratitude page after placing an order;<\/li>\n\n\n\n
- “Backing up” redirects implemented in JavaScript – if the visitor’s browser does not support scripts;<\/li>\n\n\n\n
- Redirecting the visitor to the page with links to download the correct browsers – if his browser displays your site with errors.<\/li>\n<\/ul>\n\n\n\n
<\/span>Summary<\/span><\/h2>\n\n\n\n
- \n
- A 301 redirect is a significant SEO optimization tool that improves the user experience and communication with search engine robots. It allows you to save the weight of pages, glue them together, save traffic, and retain the user. However, it\u2019s crucial that you use the correct type of redirect status code for your purpose to get the correct outcome.<\/li>\n\n\n\n
- There are different ways to implement 301 redirects. The most common are edits in the web server configuration file (.htaccess). When implementing 301 redirects through the .htaccess file, site owners use classic 301 redirects or the RewriteRule directive.<\/li>\n\n\n\n
- It is unnecessary to involve a programmer in implementing 301 redirects on different CRMs. The task is easily solved using modules or platform features.<\/li>\n\n\n\n
- There are many different redirects, but 301, 302, and 304 will affect your SEO 98% of the time.<\/li>\n\n\n\n
- Avoid redirect chains and redirect loops, as they can seriously worsen your rankings.<\/li>\n\n\n\n
- Be very careful, and be active in checking the result of your settings. When working with redirects, it is easy to make mistakes and affect other pages or files. <\/li>\n<\/ol>\n\n\n\n
To make sure your site is search-engine friendly, check your site for technical issues and redirects with the help of the WebCEO Auditor Tool.\u00a0<\/a><\/p>\n\n\n\n\r\n
- Configure the plugin. To do this, go to the “Settings” tab with the plugin’s name.<\/li>\n<\/ol>\n\n\n\n
- Setup plugin<\/a> and install it in WordPress<\/li>\n\n\n\n
- RewriteRule<\/strong> – sets the URL conversion rule.<\/li>\n<\/ul>\n\n\n\n
- RewriteCond<\/strong> – defines the conditions under which the RewriteRule directive will be triggered. The number of RewriteCond conditions before the RewriteRule directive is unlimited.<\/li>\n\n\n\n