Indexing a fresh NuxtJS website with Directus API
nuxt3Subject: Persistent Indexing Issues for Nuxt/SSR Webshop (5xx errors & "Crawled - Currently Not Indexed")
Issue bescription
Since the soft launch of our new webshop in August 2025 (over 6 months ago), we have been facing severe indexing issues. Despite a technically sound setup using Nuxt with Server-Side Rendering (SSR), Google refuses to index the majority of our product pages and blog posts.
Current status in Google Search Console (GSC):
- 5xx Server Errors: GSC reports server errors that do not appear in our actual server logs or monitoring tools.
- "Crawled - currently not indexed": The bulk of our URLs are stuck in this status.
- Live Test Success: The "Live Test" in the URL Inspection Tool almost always returns a green "URL is available to Google" status. However, manual indexing requests do not lead to actual indexing.
Questions for the Community
Given that the site is technically healthy (confirmed by Screaming Frog and GSC Live Tests), there are no manual actions (penalties), and the content is unique:
- "Ghost" 5xx Errors: Why would GSC report 5xx errors that don't exist in our server logs? Could this be related to rate-limiting of Googlebot IP ranges at the firewall/WAF level that only triggers during high-intensity crawls?
- Legacy Impact: Could the previous manual removal of the test subdomain be "throttling" the crawl priority or trust of the main domain?
- Property Reset: Is there any merit in deleting and recreating the GSC property, or is that likely a waste of time?
- Nuxt/SSR Specifics: Are there known cases where specific Nuxt headers or the way Nuxt handles hydration causes Google to crawl but hesitate to index?
The website i am talking about is https://mijnporselein.nl (which only is indexed on the homepage).
Issue bescription
Since the soft launch of our new webshop in August 2025 (over 6 months ago), we have been facing severe indexing issues. Despite a technically sound setup using Nuxt with Server-Side Rendering (SSR), Google refuses to index the majority of our product pages and blog posts.
Current status in Google Search Console (GSC):
- 5xx Server Errors: GSC reports server errors that do not appear in our actual server logs or monitoring tools.
- "Crawled - currently not indexed": The bulk of our URLs are stuck in this status.
- Live Test Success: The "Live Test" in the URL Inspection Tool almost always returns a green "URL is available to Google" status. However, manual indexing requests do not lead to actual indexing.
Questions for the Community
Given that the site is technically healthy (confirmed by Screaming Frog and GSC Live Tests), there are no manual actions (penalties), and the content is unique:
- "Ghost" 5xx Errors: Why would GSC report 5xx errors that don't exist in our server logs? Could this be related to rate-limiting of Googlebot IP ranges at the firewall/WAF level that only triggers during high-intensity crawls?
- Legacy Impact: Could the previous manual removal of the test subdomain be "throttling" the crawl priority or trust of the main domain?
- Property Reset: Is there any merit in deleting and recreating the GSC property, or is that likely a waste of time?
- Nuxt/SSR Specifics: Are there known cases where specific Nuxt headers or the way Nuxt handles hydration causes Google to crawl but hesitate to index?
The website i am talking about is https://mijnporselein.nl (which only is indexed on the homepage).
MijnPorselein
MijnPorselein is dé specialist in het bedrukken van porselein, glazen & diverse extra’s met uw eigen huisstijl.
