The feasibility of these solutions depends on your website’s tech stack. Hence, laying out a good/better/best approach is important.
Ideal solution: Make critical content available in the raw HTML
As SEOs, we can sleep soundly at night knowing that our website’s internal links, page headings, body copy, and more are available to Google in our raw HTML. Searchbots can crawl and index our critical content efficiently without risking errors or delays associated with Google’s rendering service.
Ensure you highlight to developers the critical SEO elements currently absent from the raw HTML and explore the feasibility of making those updates.
Next best solution: Implement a server-side rendering (SSR) solution
Before we go into this solution, let’s understand server-side rendering (SSR) vs. client-side rendering (CSR):
Server-Side Rendering: The initial page load delivers all content to the browser via HTML.
I regularly use this analogy from Onely to explain the difference: “CSR is like a cooking recipe. Google gets the cake recipe that needs to be baked and collected. SSR – Google gets the cake ready to consume. No need for baking.”
So, the essential question for our devs is, “Could we lean on SSR instead of CSR to deliver content during the initial page load?”
Last-ditch solution: Implement dynamic rendering
Dynamic rendering is a hybrid solution where your users experience your website’s client-side rendering while search engine bots are served a separate, static HTML version.