Server Side Rendered, Client Side Rendered, Server Side Generated Sites & Search Engine Optimisation
Max Entwickler's normal fare is Line-of-Business corporate applications. These do not require SEO & can be CSR (static) apps (built in Vue.js for example) or SSR (non-static) apps (like Django). What about sites which require SEO?. Consumer sites drive business thro marketing & the major search engines play a huge part in this. SEO is (mainly) executed on the SERVER SIDE where pages can be built & crawled by bots & the like.
Static Sites? Sorry to get technical. The easiest, cheapest & most popular way to get a site up & running is as a static site. Put simply a static site is one which is a) deployed to a static host (many providers of site hosting only host static sites) and b) if SEO is required pages are generated (pre-generated) as part of the development tool-chain by SSG (Server Side Generation). It is these pre-generated snap-shots which are available to bots on the server & are delivered on request to the browser. SSG pages can also be refreshed on a time basis.
Non-Static Sites? Sites can be deployed as SSR (Server Side Rendered) sites. When you request a page or click a link on a site & you see the browser loopy thing rotating you are seeing SSR. Way back in the mists of time all pages were delivered like this - with a full page refresh. Once the page is on the client, the app can function as an SPA.
SSR is more expensive & complex to host than static because the pages delivered by the server are not snap-shots - they are live (built each time) pages & require specific software to enable this. If your page content can change frequently and SEO is required, then SSR is the way to go.