Yes, they are more difficult to execute than basic redirects.
Preferably, you ought to use 301s, 302s, or 307-based redirects for execution. This is the usual best practice.
However … what if you don’t have that level of gain access to? What if you have a problem with creating standard redirects in such a method that would be useful to the website as a whole?
They are not a finest practice that you ought to be utilizing solely, nevertheless.
They are frequently utilized to notify users about modifications in the URL structure, but they can be used for practically anything.
Many modern-day sites utilize these kinds of redirects to redirect to HTTPS versions of websites.
Doing redirects in this manner is useful in several ways.
A Quick Overview Of Redirect Types
There are several standard redirect types, all of which are helpful depending upon your situation.
Preferably, the majority of redirects will be server-side redirects.
These types of redirects stem on the server, and this is where the server chooses which place to reroute the user or search engine to when a page loads. And the server does this by returning a 3xx HTTP status code.
For SEO reasons, you will likely utilize server-side reroutes the majority of the time. Client-side redirects have some downsides, and they are generally suitable for more specific circumstances.
Client-side redirects are those where the internet browser is what decides the location of where to send the user to. You need to not need to utilize these unless you remain in a situation where you do not have any other choice to do so.
Meta Refresh Redirects
The meta refresh reroute gets a bad rap and has an awful track record within the SEO community.
And for excellent factor: they are not supported by all internet browsers, and they can be confusing for the user. Rather, Google recommends using a server-side 301 redirect rather of any meta refresh redirects.
Js redirects are most likely not a great concept though.
— Gary 鯨理 ／ 경리 Illyes (@methode) July 8, 2020
These best practices include preventing redirect chains and reroute loops.
What’s the difference?
Avoid Redirect Chains
A redirect chain is a long chain of redirect hops, describing any situation where you have more than 1 redirect in a chain.
Example of a redirect chain:
Reroute 1 > redirect 2 > redirect 3 > redirect 4 > redirect 5
Why are these bad? Google can only process up to three redirects, although they have actually been known to process more.
Google’s John Mueller recommends less than 5 hops per redirect.
“It doesn’t matter. The only thing I ‘d watch out for is that you have less than 5 hops for URLs that are regularly crawled. With multiple hops, the primary effect is that it’s a bit slower for users. Search engines simply follow the redirect chain (for Google: up to 5 hops in the chain per crawl effort).”
Preferably, web designers will want to aim for no more than one hop.
What takes place when you add another hop? It slows down the user experience. And more than 5 present substantial confusion when it pertains to Googlebot having the ability to understand your website at all.
Fixing redirect chains can take a lot of work, depending upon their intricacy and how you set them up.
However, the primary principle driving the repair work of redirect chains is: Simply ensure that you total 2 steps.
Initially, get rid of the extra hops in the redirect so that it’s under five hops.
Second, carry out a redirect that redirects the former URLs
Avoid Redirect Loops
Reroute loops, by contrast, are basically an infinite loop of redirects. These loops happen when you reroute a URL to itself. Or, you accidentally redirect a URL within a redirect chain to a URL that occurs previously in the chain.
Example of a redirect loop: Reroute 1 > redirect 2 > redirect 3 > redirect 2
This is why oversight of website redirects and URLs are so important: You do not want a circumstance where you execute a redirect only to learn 3 months down the line that the redirect you produced months ago was the reason for problems because it developed a redirect loop.
There are several reasons these loops are disastrous:
Regarding users, reroute loops get rid of all access to a particular resource located on a URL and will wind up triggering the browser to show a “this page has a lot of redirects” mistake.
For online search engine, redirect loops can be a substantial waste of your crawl budget. They also develop confusion for bots.
This develops what’s referred to as a crawler trap, and the spider can not get out of the trap quickly unless it’s manually pointed somewhere else.
Repairing redirect loops is pretty easy: All you need to do is get rid of the redirect causing the chain’s loop and change it with a 200 OK functioning URL.
They should not be your go-to solution when you have access to other redirects because these other types of redirects are chosen.
However, if they are the only alternative, you may not be shooting yourself in the foot.
Featured Image: RoseRodionova/SMM Panel