Syndi by Syndigo - Server-Side Rendering (SSR) is an integration option which requires website owners to manage Enhanced Content within their server web application prior to sending it out to visitors’ browsers. This extra integration effort comes with the benefit of reduced network time loading pages and improved search engine readability (SEO).
How it Works (Simplified)
Integration
A common pattern in server-side rendered website frameworks is to use a static HTML template which can be dynamically populated when a requested by a user. You can think of Syndi SSR as inline HTML being added to the template wherever you want Enhanced Content to display for your customers. In your dynamic layer (often a Controller) you check if new content exists and fetch it using standard HTTP.
HTTP Based URL Pattern
Content that is pre-rendered by Syndigo is accessible via a convention-based URL:
https://content.syndigo.com/ssr/<siteid>/<pageid>/inline.html
The two parts of this template URL are:
- SiteId - Static GUID issued to each retailer partner per website
- PageId - A unique identifier used in the URL of a product, on the retailer’s website, which identifies the product. Sometimes a SKU, or other existing product identifier.
Additional Considerations
The following are the additional considerations:
- Scalability: Server-side rendering puts additional demand on a website operator’s server infrastructure. Proper scaling strategies must be deployed to support variable customer demand.
- Caching: Brands change their content regularly within Syndigo’s system. Using an aggressive caching strategy will reduce the ability of the brands on your site to get content out to their customers. We recommend supporting standard HTTP cache headers to ensure you’re getting the latest content. This includes checking to see if content has changed since last request.