The latest articles on DEV Community by Ben Carp (@carpben). https://dev.to/carpben https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F172235%2F0fd37077-9a8f-4274-86ab-49a82953dc41.jpeg https://dev.to/carpben en Ben Carp Tue, 14 Jan 2020 09:31:46 +0000 https://dev.to/carpben/ssr-compared-to-prerendering-for-seo-2cb5 https://dev.to/carpben/ssr-compared-to-prerendering-for-seo-2cb5 <p>Our site is rendered on the server, but then certain pages are mostly a react component. We would like to move to be towards being completely client rendered but for certain pages we are very much concerned about SEO.</p> <p>We are aware of solutions such as Next (SSR+CSR), but we aren't keen towards such solutions.</p> <p>We are considering CSR + dynamic rendering. This means, building pages/routes completely in React, and then serving a pre-rendered page to crawlers. So far SSR was considered the best practice for SEO. Will the same page rendered via pre-rendering be equivalent to that same page rendered via SSR in terms of SEO?</p> <p>I see no reason it won't be, as the html is the same. Perhaps excluding response time, as non cached pages might take much longer to render using pre-rendering.</p> react