Page indexed but live url test gets 500 error

should i fix it?

[Nick11]

hi everyone,
My site is quite new and it is quite different from traditional SEO-focused sites because it is Nuxt-based with a very JS-heavy frontend architecture.
Our pages use SSR, but many sections still rely on hydration, dynamic imports, API-driven content, and a large amount of /_nuxt/*.js chunks.
From the perspective of visitor, when I visit my site, it is quite smooth but from the perspective of Google, there seems quite many problem. Many pictures can't be rendered during live test, and some pages, often blogs, even returns 500. 25% of js (100 among 400) can't be loaded.
Has anyone dealt with similar issues on Nuxt/Next.js sites? Should I try switching to traditional simple HTML-first architectures.

[lucy24]

:: idly wondering if there is any situation in which the answer to “Should I fix it?” is “No” ::

[Nick11]

I'm new to tech SEO. Since the pages pages are indexed, I thought I could save time for other projects, but I'm also afraid that Google will really get 500 error in the next crawl of the indexed pages and then remove them from the list.

[not2easy]

Hello Nick11 and welcome to WebmasterWorld [webmasterworld.com]

many sections still rely on hydration, dynamic imports, API-driven content, and a large amount of /_nuxt/*.js chunks.

may be the reason that not all resources can be processed before a server gives up on concurrent rendering. Your browser cache may make it smoother for you than for first-time visitors.

BTW - That welcome link above offers tips on using the forums' features and settings.