Need some assistance in article part using server side rendering

[praneetharao0994]

Currently, the article body content is delivered as JSON within a Fusion script tag and rendered client-side using React. Since the article content is not available in the initial HTML, Googlebot may not be able to reliably crawl and index the content. As a result, SEO enhancements such as schema markup, breadcrumbs, and sitemaps may have limited impact until the article content itself is server-rendered.

The category pages are already server-rendered and could potentially serve as a reference for implementing a similar approach for the article pages.

There is currently a single canonical template for article pages. For example:

https://insights.citeline.com/medtech-insight/business/r-and-d/clinical-trials/fda-cor-mdx-clearance-puts-peerbridges-predictive-health-ambitions-within-reach-RERWGKSNIBAVHF7IGJBBQIR4KM/

Could we explore whether the article body content can also be done using server side rendering

[matthewroach]

There's no reason why an article cannot be server-side rendered and sent to the browser. This will all depend on the requirements you have. I can see from the URL you provided there is a paywall being shown - which will add to the complexity, depending on your setup.

For basic article rendering server side rendering is simple - if you have complex rendering you'll need to make sure you account for items that rely on window and make sure you account for their server side counter parts.

I can see this coming from the server

<div style="display:none" id="c0ficjkXNGBE6hq" data-fusion-collection="chains" data-fusion-type="article-body" data-fusion-name="Article Body – Norstella Block" data-fusion-message="Could not render component [chains:article-body]"></div>

Something in the article-body chain is causing the server side render to fail and then goes to client side rendering. Locally you can check your terminal logs when Fusion is running to see what's causing the issue