Yes, I agree - server side rendering is likely better for SEO in most scenarios, and so I should consider it in a business context where SEO is essential. This

Yes, I agree - server side rendering is likely better for SEO in most scenarios, and so I should consider it in a business context where SEO is essential. This isn't everyone. The comment I replied to said that Google should "delist client side rendered web pages", which is a terrible idea. Maybe I'm OK with the SEO hit? Maybe I've architectured my SPA so that it can be indexed? (At least to some degree) > The bigger question is why you think an spa should rank well in general. It's only one page. SPAs can have multiple pages (despite the name). Check out react-router [0]. Browser history can be manipulated to give the same "back button/forward button" functionality between logical pages. This is done for you by whatever framework you use. For my use case, having the browser reload every time a page is changed would severely interrupt UX. [0] https://reacttraining.com/react-router/web/guides/quick-start https://reacttraining.com/react-router/web/guides/quick-star...