What problems are SSRs supposed to solve?

Prefix U AND RISE ONCE AGAIN

SEO for SPAs.

It solves SEO. How good web site is found by Google. (And by other search engines)

SSG solves SEO for static content with some interactivity (content necessary to scan by Google search changes only when new version of site is deployed)

SSR solves SEO for dynamic content like posts in blog by users, news often written by moderators. When content is changed without new version of website deployment

Having web site remained as static assets / generated by SSG is more preferable than SSR due to easier all kind of caching

@darkwind Google scans also static sites periodically, no interactivity needed. You can ofc also submit a new sitemap in the Google Search Console to speed that up a little, but Google will still re-crawl that at its own leisure, not right after submittal.

@Fast-Nop ... Of course Google rescans but... That is not the point here. The point is that SSG and SSR provides access to web site in html/css form without requiring bot to run JS files of a virtual doms present in react/angular/vue.js.

The point is to provide easier/faster/more readable/faster to load access to web site for the re scans.

I had Vue.js site and my content was static, I just used prerender plugin which made the build as SSG for example.
SSR difference in only having the build on a run from active nodejs server

For Google bot end result, be it SSG or SSR, it will look all same. We just get rid of virtual Dom loading

@kiki might have more to say on the topic, but it was a way to effectively control multiple nations occupied by "the bear". However, it failed, because the propaganda machine never made us believe the shit they announced. Injust killings, blackmail, one-way-tickets, though not announced publicly, were all known and a strong motivator for civil resistance

@netikras wrong rant? this one is about SSR

@kiki OP said SSRs [CCPC?] :)

@ars1 what problems are SPA supposed to solve?

@gymnasium being MPA

@gymnasium Bandwidth mainly, by pulling only the data rather than pushing all client state and then pulling the entire page again, and a bunch of nontechnical issues that all derive from this difference.