Are Javascript Redirects SEO Friendly?

Posted by

So, you wish to implement JavaScript redirects, however you’re not sure how they work?

Yes, they are more difficult to carry out than basic redirects.

Preferably, you must utilize 301s, 302s, or 307-based redirects for application. This is the normal finest practice.

However … what if you do not have that level of gain access to? What if you have a problem with producing standard redirects in such a method that would be helpful to the website as a whole?

This is where using JavaScript redirects comes in.

They are not a finest practice that you must be utilizing specifically, nevertheless.

But there are some situations where you just can not avoid utilizing a JavaScript redirect.

The following is a standard primer on JavaScript redirects, when to utilize them, how to utilize them, and best practices you should use when making use of these types of redirects for SEO.

What Are JavaScript Redirects?

JavaScript redirects, essentially, are among a number of methods of informing users and web crawlers that a page is available in another area.

They are frequently used to notify users about changes in the URL structure, but they can be utilized for just about anything.

Many contemporary websites use these types of redirects to reroute to HTTPS versions of websites.

Then, whenever someone visits the original URL, the web browser loads the JavaScript file and performs whatever code is within it. If the script includes guidelines to open a different URL, it does this immediately.

Doing redirects in this way is useful in a number of methods.

For instance, you can change URLs without manually updating every single URL on your website. In addition, JavaScript reroutes can make it much easier for search engines to discover your own content.

A Quick Overview Of Redirect Types

There are several basic redirect types, all of which are beneficial depending on your circumstance.

Server-side Reroutes

Ideally, many redirects will be server-side redirects.

These types of redirects stem on the server, and this is where the server chooses which area to redirect the user or online 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 use server-side reroutes most of the time. Client-side redirects have some downsides, and they are usually suitable for more particular scenarios.

Client-side Redirects

Client-side redirects are those where the browser is what decides the place of where to send the user to. You need to not need to utilize these unless you remain in a situation where you don’t have any other choice to do so.

Meta Refresh Redirects

The meta revitalize reroute gets a bad rap and has an awful track record within the SEO neighborhood.

And for excellent reason: they are not supported by all internet browsers, and they can be confusing for the user. Instead, Google advises utilizing a server-side 301 redirect rather of any meta refresh redirects.

JavaScript Redirects

JavaScript reroutes, however, make use of the JavaScript language to send out directions to the internet browser to redirect users to another URL. There is a dominating belief that JavaScript reroutes cause issues for SEO.

Although Google does have excellent JavaScript rendering capabilities nowadays, JavaScript can still present problems. This holds true for other types of platforms also, such as Spotify and other ecommerce platforms.

If, however, you’re in a scenario where you can just utilize a JavaScript redirect as your only option, then you can just utilize JavaScript.

Also, Google’s Gary Illyes has specified as recently as 2020 that JavaScript Reroutes “are most likely not a good idea.”

Js redirects are most likely not a good idea though.

— Gary 鯨理 / 경리 Illyes (@methode) July 8, 2020

Best Practices For SEO-Friendly JavaScript Redirects

Regardless of whether you are utilizing conventional redirects or JavaScript redirects, there are several best practices you must follow in order to not mess things up for SEO.

These best practices include preventing redirect chains and reroute loops.

What’s the distinction?

Prevent Redirect Chains

A redirect chain is a long chain of redirect hops, describing any scenario 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 approximately 3 redirects, although they have actually been known to process more.

Google’s John Mueller recommends less than 5 hops per redirect.

“It does not matter. The only thing I ‘d watch out for is that you have less than 5 hops for URLs that are frequently crawled. With several hops, the primary impact is that it’s a bit slower for users. Search engines simply follow the redirect chain (for Google: approximately 5 hops in the chain per crawl attempt).”

Preferably, web designers will want to go for no more than one hop.

What occurs when you add another hop? It slows down the user experience. And more than five present substantial confusion when it comes to Googlebot having the ability to comprehend your site at all.

Repairing redirect chains can take a great deal of work, depending upon their intricacy and how you set them up.

But, the main principle driving the repair work of redirect chains is: Simply make certain that you total two steps.

First, get rid of the additional hops in the redirect so that it’s under five hops.

Second, implement a redirect that redirects the former URLs

Avoid Redirect Loops

Reroute loops, by contrast, are basically a boundless loop of redirects. These loops occur when you redirect a URL to itself. Or, you mistakenly reroute a URL within a redirect chain to a URL that occurs previously in the chain.

Example of a redirect loop: Redirect 1 > redirect 2 > redirect 3 > redirect 2

This is why oversight of website redirects and URLs are so essential: You do not desire a scenario where you implement a redirect just to learn 3 months down the line that the redirect you developed months back was the reason for issues since it produced a redirect loop.

There are a number of reasons why these loops are disastrous:

Concerning users, reroute loops eliminate all access to a particular resource located on a URL and will wind up triggering the internet browser to display a “this page has too many redirects” mistake.

For online search engine, reroute loops can be a substantial waste of your crawl budget. They likewise develop confusion for bots.

This creates what’s referred to as a spider trap, and the crawler can not get out of the trap easily unless it’s manually pointed elsewhere.

Repairing redirect loops is pretty easy: All you need to do is eliminate the redirect triggering the chain’s loop and change it with a 200 okay operating URL.

Wish To Use JavaScript Redirects For SEO? Not So Quick …

Beware about creating JavaScript redirects due to the fact that they might not be the very best option for redirects, depending upon what you have access to.

They should not be your go-to service when you have access to other redirects since these other types of redirects are preferred.

However, if they are the only alternative, you may not be shooting yourself in the foot.

More resources:

Featured Image: RoseRodionova/Best SMM Panel