Google Cloud Search VS Prerender

Https://workspace.google.com/products/cloud-search/. - Source: Hacker News / about 2 years ago

This is a thing that exists already for Google Cloud Search https://workspace.google.com/products/cloud-search/ https://marketplace.atlassian.com/apps/1212945/google-cloud-search-confluence-connector?tab=overview&hosting=server. - Source: Hacker News / over 2 years ago

What framework or service are you using to pre-render your content? Check out https://nuxt.com and https://prerender.io if you're not using something like this already. Source: about 1 year ago

The best option is going to be using SSR using Next.js/Vite SSR/similar as others have mentioned. If you do want to stick to an SPA though (vanilla React + Vite/CRA), make sure your meta tags are set dynamically, and you can definitely pre-render (using prerender.io for example) as well. Source: about 1 year ago

If you don't go with Next, you'll want to make sure that you're properly setting all your page titles, meta descriptions, and tags with something like react-helmet (or whatever the newer fork of it is called) and prerendering with prerender.io or something. Source: about 1 year ago

Thank you for the comment. I'll investigate prerender.io. I think we'll most likely change the architecture, but if we continued the developers recommended next.js. Source: about 1 year ago

Depending on how many pages you have, that can get expensive. You can get around the cost by implementing prerender.io as a stopgap (to start getting your pages indexed again -- this can take precious time) and then work your way towards a node instance that handles the static rendering for you. There are lots of tutorials on this, but they depend on which instance of React you're working in. Source: about 1 year ago