预渲染 Vue？ Nuxt.js 或插件，现有网站哪个更好

Question

I have webiste which is available in the internet. Front is written in Vue.js and CMS is created using Laravel (PHP). These are separate applications. Unfortunatelly Google dosen't see the page because of lack of SEO (yeah. Vue), The website is big, has a lot of routes. fetches data from API ex. for a blog. Here is my question? What is a better solution? Move website to Nuxt.js or use some fancy plugin like https://github.com/chrisvfritz/prerender-spa-plugin and fetch data from API. I'll be gratefull for any tips!

Answer 1

Use @prerenderer/renderer-puppeteer if: You're prerendering up to a couple hundred pages and want accurate results.

Use @prerenderer/renderer-jsdom if: You need to prerender thousands upon thousands of pages, but quality isn't all that important, and you're willing to work around issues for more advanced cases. (Programmatic SVG support, etc.)

Answer 2

Let me try to put my two cents here. As far as I know, here are two ways to rendering statically on your server using vue.

1. SSR (Server Side Rendering) - (I haven't implemented it) What happens is that when you call a certain route the HTML dom content is loaded and set to the page before loading and then loads the page with the HTML content on the fly, this prevents the blanks pages sent to google crawlers (As far as I know). You are basically showing basic html, css and js now. This will use a lot of server CPU for processing every route request that comes to the server, so you have to make sure that the project you are developing doesn't have so much traffic that your server overloads.
2. Prerendering - In this, the server prebuilds the HTML pages for each and every route in your site. Also you have to specify the routes that are needed to be rendered manually or you have to find a way to pass the dynamic array to build it all the time. Since the generation of the files needs a building of the new HTML files with new content you need to implement a system to run the build each time you have to add a new route or a do some updates on the existing pages. You should try CI/CD for this for automated processes. I haven't implemented it but it might get a little bit hectic.