Problems with nuxt.js development

considering the problem of SEO optimization, the project uses the nuxt framework.
now there are three issues that I don"t quite understand. I hope the Great God will take the time to explain them in the midst of his busy schedule.
Thank you.

1.nuxt provides two ways to package deployment, static and server-side rendering. There are a lot of tabs, broadcast maps, and a lot of data in the project that require back-end interaction. This situation is not suitable for static deployment.

2. I just realized this problem. The
asyncData method is called only when the page is initialized. So will the data returned when I trigger the request when I switch tabs be displayed in the source code when rendered?
if not, is there any way to solve this problem?
is this important for SEO?

Feb.23,2022

answer your questions one by one. First of all, the essence of SEO is not only to do server rendering, but also to consider whether your page needs to be crawled and included by search engines, and page weight.
in addition, asyncData this API is mainly called when the page is loaded or refreshed for the first time, but switching this scenario directly in nuxt will also normally switch your request in asyncData . Internally, you only need to change the context to the this pointer, so a request that does not pass a page refresh will not directly render a page to return, but separate data. But when you refresh the page, you will return a rendered page from the server, and the two do not conflict.

Menu