SofTeCode Blogs

One Place for all Tech News and Support

Javascript SEO: Server side or client side rendering?

3 min read
java script

The immediate differences between server-side and client-side rendering.

First of all, I feel it might be fitting on behalf of me to elucidate the overall definitions of both Javascript SEO servers- and client-side rendering and the way the 2 differ from each other.

Server-side rendering (SSR)

Server-side rendering (often mentioned as SSR), is that the traditional way of rendering content to your page. When a user enters your site, an invitation is shipped to the server. The response will return the HTML file for your page and your content will load correspondingly.

Client rendering (CSR)

Client-side rendering (CSR) on the opposite hand, may be a more modern technique in web-development. Whereas an SSR request would respond with a whole HTML file that’s displayed as your site within the browser, CSR will only be sending an HTML file containing a Javascript file. With this file, the browser will generate the remainder of your page.

Server-side rendering (SSR)

Since SSR is that the traditional way of rendering an internet site, most websites online are going to be doing it this manner. Does this mean that this is often the proper way? Not necessarily, but it’s important to notice that each one search engine are optimized for SSR, meaning you ought to consider how important good SEO is to you or your clients.

*Note: Google claims that their program can read through javascript files, yet tons of individuals seem to be disagreeing.

Client rendering (CSR)

So you would possibly ask yourself, what are the advantages of CSR? rather than an HTML file, I’ll be presenting the search engines with a javascript file, that they arguably cannot understand?

Well, Speed is the primary answer to the present controversy. The Client also can be interpreted as your device whether that might be your computer or phone. Javascript may be a client-side language, which suggests that your device can build the page for you. In most cases, this may reduce the time that it takes for your page to create.

Server-side rendering (SSR)

So you would possibly have already got guessed what disadvantages SSR comes with. Pagespeed is that the main reason that somebody would choose CSR over SSR – especially when it involves web applications that don’t necessarily need good SEO. Since Javascript may be a client-side language it’ll load faster than serverside rendered HTML-files, because it can cash in of the processor of your device.

Client rendering (CSR)

Since CSR is predicated on javascript, many developers believe that search engines can’t crawl your site. I cannot confirm whether that’s true or not.

Can server-side rendering and client-side rendering be combined?

Well no… and yes.

Naturally, SSR and CSR are two various things. SSR happening at a server, whereas CSR is occurring directly on your device – so there’s no way of mixing the 2 into a replacement sort of rendering.

However, there have been developed Javascript frameworks who’s utter purpose is to use both SSR and CSR on an equivalent page. the present frameworks that I’m conscious of are:

  • Gatsby.js
  • Next.js
  • Nuxt.js

I won’t go an excessive amount of into details about how each of them works, but just the explain the concepts they’re built upon.

Next.js and Gatsby.js are frameworks that believe another javascript framework called react.js, whereas Nuxt.js depends on a javascript framework called Vue.js. In theory Vue and React are great frameworks – but they need a standard pitfall… you would possibly have guessed it already: They’ve supported javascript which could end in low ranking during a search field.

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

Give your views

This site uses Akismet to reduce spam. Learn how your comment data is processed.