SEO limitations for Emerald and Sapphire stores

React stores cannot have search engines crawl into their React Store based (Emerald/Sapphire) store pages, which impacts their Store's SEO Score and, hence, the revenue indirectly.

React stores (such as Sapphire and Emerald) render pages in the browser (client side rendering). Client side rendering shows an empty or partially generated page before loading, while Server Side rendering technology displays a fully-rendered HTML page on the first load. In the case of client-side rendering, search crawlers cannot process the serving pages completely and might impact the SEO Score of your E-store pages.

You may need to leverage a third-party solution such as pre-rendering to improve the SEO for client-side rendered pages. The pre-rendering technology is to help improve the SEO, allowing search engines to crawl and index the dynamic content properly. When search engines crawl your pages, pre-rendering technology frameworks such as prerendor.io serve as a pre-rendered or fully formed page version. Integrate the prerendor.io framework with your web server/backend/CDN to have a mechanism that determines requests forwarded to pre-render and available to search engines to crawl and process.
Note: HCL Commerce React Stores (Sapphire and Emerald) do not offer default pre-rendering solution.
HCL Commerce Version 9.1.13.0 or laterNote: A default pre-rendering solution is available for the Ruby store from version 9.1.13 onwards. The Ruby store is based on next.js which does the server side rendering and is compliant with search crawlers.