Personally, I've found that to a large extent, if you aren't a content driven site/app that the SEO portion is largely not going to be very useful. Also, Google and Azure are pretty quick to handle JS content changes (usually 2-3 days from past experience). If what you are building is more like an application, and you aren't selling products in a public facing way then you may not want to focus on SEO or server-rendering.
However, if you are largely content driven, or public facing sales driven you should probably go the other direction with pre-rendered content first, then add features as needed. It comes down to what your focus is on.
I've been split about half and half in my career between the two, and it really should inform your approach. The more SEO friendly your content needs to be, the more you should lean into a static first approach. Even if that means running multiple renders a day. If you're dealing with a lot of content, with lots of searchable options, and results that need indexing, you may want a light server to do your basic renders. If you're creating an application experience like chat, games or otherwise heavily interactive content, then don't worry about the server/seo render. Most of the businesses I've worked with rely on other sales channels and SEO has been a reduced influence.
tracker1 1753 days ago. link 1 point ▲ ▼