Redirects are an indispensable tool in daily SEO practice, enabling the forwarding of URLs to other or new URLs. If you know how forwarding works and what to look for, you are clearly benefiting from the relaunch or domain move.
This guide covers the most important questions regarding redirects and its correct usage.
Forwarding, or redirection, is the process of redirecting a URL to another URL as requested by a client (browser). Redirects can be implemented in various ways and can be used temporarily or permanently. A redirect is completed when the client is successfully routed to the destination URL of the redirect.
There are various application scenarios for redirects. For example, Google explicitly recommends 301 redirect to seamlessly transition from an old domain to a new domain in the event of a domain move. Google has set up its own policies for this.
Other possible applications include:
Generally, this relates to either server-side or client-side redirects. The most common server-side redirects include 301 and 302 redirects. The most frequently used client-side redirect is meta-refresh.
What are server-sided redirects?
A server-sided redirect occurs when an http-request is performed. This happens when a client, i.e. a browser or bot, retrieves a URL and makes a request to a web server. The web server then delivers a status code. In the case of server-sided redirection, the server indicates that the requested document has been redirected to another URL. The client then invokes this new URL, and the user or bot is forwarded.
Servers can issue various status codes according to the RFC 7231 specification. Each of the specified redirects fulfills a different task. The entire process of server-sided forwarding takes only a few seconds and is hardly noticed by the user, depending on the type of redirect. Search engines must interpret each forwarding command and decide how to handle it. For SEOs and webmasters, the question arises as to whether the desired redirect can also pass on link power and ranking signals.
A guide to all important status codes and their effects can be found here.
If both of these relevant criteria are taken into account, the number of SEO-relevant, server-sided redirects can be reduced to the following five:
|HTTP Status Code||Temporary or permanent|
For SEO purposes, 301-forwarding is of great importance. It redirects link strength and passes on all relevant rankings to the new destination URL.
The 301 redirect is a useful solution to avoid orphaned pages. You should use a 301 redirect if:
The 301 redirect is for permanent redirection of URLs. Therefore, this type of forwarding is not suitable if, for example, you want to forward seasonal products in your online shop or require redirection to a temporary special offer page.
There is no all-encompassing answer to this question. Google itself takes some time to determine that the old URLs have been moved to new ones. These new URLs must first be indexed and output instead of the old URLs. While this process can be done within a few days for small websites with a few subpages, it takes considerably longer for larger projects with several thousand URLs.
Basically, you should keep forwarding in place as long as necessary. Random testing is recommended through site query on Google. This allows, for example, to check whether the new URLs have already been indexed and stored in the cache.
301 forwarding can be implemented via the .htaccess file of an Apache server or with PHP.
1. .htaccess: This file provides instructions for the server to run on an http-request. You need Apache module "mod rewrite" to implement the 301-redirect. The file specifies the URL to which the client is to be redirected.
The contents of an .htaccess file may appear as follows:
RewriteRule siteold.html sitenew.html [R=301]
In this case, the page would be redirected to newpage.
2. PHP: You can also set up forwarding via PHP. In order to do so, a code snippet is inserted into the header of the HTML document. When the client calls up the page, the user is redirected to the new URL. This type of forwarding is not server-sided forwarding. However, it is mentioned here for the sake of completeness.
You can find additional ways to implement a 301 redirect here.
This redirect shows a client that the requested document is temporarily accessible via a different URL. The 302 redirect, like all 3xx redirects, passes PageRank or relevant SEO signals to the destination URL.
A 302 redirect is recommended if you need temporary forwarding that does not affect your rankings and should not be cached. For example, you can use a 302 redirect to redirect a URL to a special offer page or seasonal product page. Likewise, it is also suitable for tracking or web page testing.
To set up a 302 redirect, you can use the .htaccess file or use PHP, as with the 301 redirect.
An entry in .htaccess for a 302 redirect might look as follows:
RewriteRule siteold.html sitenew.html [R=302]
A 302 redirect is always created temporarily. For this reason, you should not use these redirects for permanent URL redirects.
You can use this temporary redirect if a URL has to be redirected for a brief period. This is the case, for example, in the event of server maintenance. As with the 302 redirect, this redirect should not be used for permanent redirects.
What are client-sided redirects?
Client-sided Redirects is not performed by a server, but directly from a client, for example, a browser. Usually, server-sided forwarding is more appropriate. However, in practice there are cases in which client-sided redirects can be used.
A JS redirect is inserted as a script in the source code of the page.
window.location = "http://www.newsite.com/";
In this case, the user is directed to "newsite.com" when the existing URL is called.
For a long time, 301 redirects were associated with a loss of PageRank or link power. However, today there are numerous comments from Google employees, which show that forwards pass on PageRank.
Even if it seems to be confirmed that forwards pass on PageRank, webmasters should also consider other SEO factors. There are many other ranking factors that you should pay attention to when redirecting to new URLs.
If you forward your URLs with a redirect, you can configure the address change using a Google tool. In order to do so, you need an account for the Google Search Console. Both URLs, the new one and the old, must be set up here. When doing so, it is important that a 301 redirect has been previously performed. If the redirect simply involves a change of protocol, for example, from http to https, the tool does not work.
Here you can set up the changes in the Google Search Console and monitor the redirected traffic
|Application||temporary or permanent||cacheable||Possible status codes|
|Changes to the URL structure||permanent||yes||301|
|Affiliate campaign||temporary||Depends on the intention||302|
To avoid duplicate content, there are two common technical possibilities: the canonical Tag and 301-forwarding. While the canonical tag is an HTML meta element, which is implemented in the source code of the page, 301 redirection can be done via the server, for example.
In addition, the canonical tag is not actively redirected to the canonical URL. Rather, it is a reference for search engines that an "original" URL exists, to which the existing document refers or whose copy is the current document. Ideally, search engines should ignore the duplicates and index only the canonical URL. However, a canonical tag is only a recommendation for action that the bot does not necessarily have to implement.
A 301 redirect, on the other hand, is a unique default that the server or client must obey. Even with a 301 redirect, the original URL can still be indexed. However, it will be replaced in the index by the new destination URL of the redirect.
Generally, 301 redirects are the better solution when it comes to cleanly consolidating or redirecting URLs and where there are no reasons to suggest that content is accessible under different URLs. A common reason for this includes, for example, printed versions of news articles. In this case, a canonical tag is the better option to avoid duplicate content, since the printed version of the URL is absolutely necessary for the user.
If you use forwarding, especially 301 redirects, you should avoid forwarding chains. Such chains occur when a URL is redirected to another URL that already has a redirect. In extreme cases, the browser or bot can no longer resolve the source request and warns about "too many redirects." Likewise, loading times and server load are increased due to multiple forwarding lines. Further negative consequences of forwarding chains include waste of crawler budget as well as the waste of SEO potential. Google's John Müller, at the request of seoundtable.com 2016, confirmed that Webmasters should avoid and resolve forwarding chains, especially during domain migration.
When undertaking a domain change, it is wise to create an overview of all configured forwards. This enables you to avoid possible forwarding chains in the future.
Search engines are continually searching the web for new content. Thus, bots follow links, crawl websites, and index the content as well as other elements. However, there is only a limited crawler budget available for this operation. Webmasters have various options to influence how Googlebot can make the most of its crawl budget. An important factor in terms of crawling is the number of requests that the bot can make to the server.
If a URL is now redirected, Googlebot must execute an additional request. If there are many redirects on a web page, the number of requests increases. At the same time, the bots' crawler budget is reduced. Therefore, you should generally manage forwarding sparingly. This is because when the crawler budget is exhausted by redirects, Googlebot has less time to crawl and index pages. As a result, it is possible that your indexed pages will no longer be up-to-date.
In principle, any forwarding entails the risk of traffic loss. It is true that Google no longer punishes websites with a loss of link power, if these are forwarded, for example, with a 301-redirect. But ultimately, superfluous, misused, or unnecessary forwarding can be a disadvantage for a web page. This is the case, for example, if you use forwarding deliberately to transfer traffic to a sales page that has nothing to do with the redirected page. An example of such irrelevant forwarding would be if you redirected a high-traffic info page for spectacle lenses to a pure affiliate page via 301. In a 2016 study, it was demonstrated that Google can even interpret irrelevant forwarding as a soft 404 error.
In fact, the link force is only one of many ranking factors passed on via redirect. If, for example, the title is not maintained on the new target page or the content is inferior, a redirection can have negative consequences for the ranking. Therefore, it is recommended that nothing should change apart from the URL when setting a redirect.
If you use redirects correctly, you can fix SEO problems and redirect old domains safely and without major disadvantages to new ones. When undertaking redirects, consider for each redirect as to whether it is really useful and utilize the 301 redirect carefully, in order not to increase server latency unnecessarily or to unnecessarily consume the crawler budget of Googlebot.
Practice makes perfect!
Analyze your website with Ryte for FREE
Published on 06/01/2017 by Eva Wagner.
Eva is an experienced content marketer. Until May 2018 she was a member of online marketing team at Ryte. Using her creativity and the knowledge of current topics, she was responsible for the German Ryte Magazine and the Ryte Wiki. She also organized Ryte’s presence at major trade fairs such as the dmexco in Cologne.Become a guest author »
Get more traffic and customers by optimizing your website, content and search performance. What are you waiting for?Register for free