Nuxt 3.15.4 SSR Application - Soft 404's in Google Search Console
Hello,
We're experiencing a surge of Soft 404's in Google Search Console on our Nuxt 3.15.4 SSR application.
Here's what we know;
- Live tests on GSC all seem to pass on any given 'Soft 404' page.
- We're getting 200's on all pages except for redirects, those give a 301, as they should.
- Some pages seem to index in Google but they might fall back to Soft 404 a couple days later.
Unfortunate events;
- We've updated from Nuxt 3.9.3 to 3.15.4 recently, with those some dependencies were updated aswell, such as
@nuxtjs/sitemap and @nuxtjs/i18n
- A faulty deploy was done and the Sitemap absolute path changed after the Nuxt update (and modules)
What we have done;
- We've disabled modulePreloads through this thread; https://github.com/nuxt/nuxt/issues/14584#issuecomment-2166544081
- We've resolved hydration mismatch errors we we're getting in production
- We've resolved all issues considering the sitemap
Does anyone else experience this? (Also after 6th of December since the last core update from Google Search). What did you do to fix it?
Thanks in advance for your time.
Interesting related posts;
- From the Nuxt community on Reddit: I created a website in nuxt and hosted it. But when i searched my website in google in place of meta title its showing 500 internal server error | nuxt. But there's no 500 internal server error in my application.
- https://support.google.com/webmasters/thread/322653126/surge-in-soft-404-which-lead-to-top-pages-disappearing-from-google-serp-being-deindexed?hl=enReddit
newton101's comment on "I created a website in nuxt and hosted it. ...
Explore this conversation and more from the Nuxt community
GitHub
optimisations for prefetching chunks · Issue #14584 · nuxt/nuxt
Currently dynamic imports include things like routes, error components, and any global components (so if using with @nuxt/content). I am very concerned to decrease HTML and number of prefetched res...
19 Replies
Hi @Kealtie. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I don't see specific information about Google Search Console's Soft 404 issues with Nuxt 3.15.4. However, I can identify some potential issues from the provided documents that might be related to your problem.
Possible Issues
1. Recent Nuxt and Nitro Updates
There have been several issues with recent Nuxt updates that might affect how pages are rendered or how status codes are handled:
- In Nuxt 3.15.4 with Tailwind v4, there were issues with HMR not working in server mode, causing 404 errors GitHub Issue #31096
- There was a bug where 404 errors were thrown before middleware could finish executing, which might affect how your pages are processed GitHub Pull #29054
2. Static Generation Issues
Some users reported problems with static page generation in Nuxt 3.15.4:
- The prerenderer stopped generating static HTML pages properly GitHub Issue #31226
- This was related to Nitro and was fixed in a later version
3. URL Encoding Problems
There were issues with URL encoding causing 404 errors when accessing apps through proxies:
- After updating to Nuxt 3.15.4, URL encoding of virtual file system paths caused 404 errors GitHub Issue #30811
Potential Solutions
1. Check Response Status Codes: Make sure your pages are properly returning 200 status codes for valid pages and appropriate status codes for errors. You can use
setResponseStatus to explicitly set status codes:
2. Consider Downgrading Nitro: Some users found that downgrading Nitro to version 2.10.4 fixed rendering issues:
3. Check for Module Compatibility: There were issues with module compatibility in Nuxt 3.16.0 (which might also affect 3.15.4), particularly with @nuxtjs/i18n. Make sure you're using compatible versions of all modules.
4. Investigate SSR Configuration: If you're using the respectNoSSRHeader experimental feature, it might affect how your pages are rendered for search engines.
Since Google's soft 404 detection is complex and considers multiple factors (content length, error messages, page structure), it's possible that something in your page rendering changed subtly after the update, causing Google to misinterpret your pages as soft 404s despite returning 200 status codes.
I recommend thoroughly testing your pages with tools like Google's Mobile-Friendly Test or Rich Results Test to see how Google is interpreting your pages, and consider implementing explicit status codes using Nuxt's setResponseStatus utility.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@235370777837436929> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
cc @danielroe - that's what we've talked about earlier
@manniL I am actually one of the developers you've been talking to. We're kind of out of idea's what it could be and if we're supposed to still do a rollback to the version that was indexed.
do you have a link to your site?
I've sent it to you in DM's.
happy to review also
Also, in DM's, thank you both for your interests.
Hey @Kealtie did you find anymore info on what was causing this?
@Lewis Hi Lewis, not yet. We've implemented a temporary solution by implementing prerender.io, which kind of caches pages and serves them statically to the bots. Are you facing similar issues?
Yea I'm having the exact same problem, it seems to be random pages it fails with too
is prerender.io easy to setup? I've not heard of it before
We’ve implemented it through cloudflare workers, cost us less then a day. So i’d say yes.
Hey again! has using this completely fixed the bug from showing up? I'm just considering buying their paid plan and want to make sure
For us, it is currently a temporary fix and all pages that were getting Soft 404's are now indexed. We can see exactly when a Google Bot comes across the website in the prerender dashboard.
Our game plan is the following;
- Uncache 10 pages from prerender that don't matter that much and keep looking for the server-side error that causes Google to see a 500 page.
We got the 90 dollar paid plan, for us that was more then enough.
Make sure you set a couple of 'Ignored URLs' so prerender doesn't start caching _nuxt folder files etc.
Does prerender.io serve no JavaScript at all then to the bot?
@manniL For what I understand it serves a fully rendered static HTML snapshot after all JavaScript has been executed.
In Google Search Console we now can even see the Google Bot has client-only content visible, where before it did only show the page after server-side hydration.
I'm not sure if this is directly linked, but I was looking for pages that errored on google and were reproducible with this and https://content.nuxt.com/docs/advanced/fulltext-search has a 500 error in google search results and when loading the url directly, but client side navigating to it works fine (like selecting 'fulltext search' in the sidebar here https://content.nuxt.com/docs/getting-started) @danielroe
I think this should be unrelated (as in the case described, SSR works fine for normal users) - but still good to know (cc @farnabaz / @Atinux regarding the docs here)
someone has just added a link to a vite dynamic import issue which sounds about right? https://github.com/nuxt/nuxt/issues/29624#issuecomment-2769487348
I've only ever seen the error occur with layouts and icons, has it been any different for anyone else?
GitHub
Cannot read properties of undefined (reading ‘default’) · Issu...
Reproduction It is impossible to reproduce the issue because the error occurs for 2-3% of users, and I can’t simulate this Approximately 1-2% of users on my website encounter the error Cannot read ...