The "SPA Shell" problem
Real-world example
A user submitted a product with the URL
quanhieptruyen.zalogames.me. VIONSKY's AI could not read the content — the page returned an empty HTML shell and all content was rendered by JavaScript in the browser. The AI only saw <div id="root"></div> and had nothing to evaluate.Why it happens
A SPA (Single Page Application) renders the entire UI on the client. When a bot or AI fetches the URL, the server returns a near-empty HTML file:
<!DOCTYPE html>
<html>
<body>
<div id="root"></div>
<script src="/main.js"></script>
</body>
</html>Search engines and AI do not execute JavaScript, so they only see the empty shell → no title, description, or images → a low Content Score (feedback signal, not an approval gate).
How to fix it
Pick one of the following:
1. Server-Side Rendering (SSR)
Render full HTML on the server before sending it to the browser. Supported by: Next.js, Nuxt, SvelteKit, Remix.2. Static Site Generation (SSG) / Prerender
Generate static HTML files for each route at build time. Best for pages that change rarely.3. Dynamic / Hybrid rendering
Some routes render on the server, some on the client (e.g. product page SSR, dashboard client).4. Prerender service (quick fix)
Use a service like Rendertron or Prerender.io to serve a static HTML snapshot to bots.Quick check
Open your page and press Ctrl+U (View Source). If you see the full content (title, description, images) in the HTML → OK. If you only see
<div id="root"></div> and <script> → you have the SPA Shell problem.See also
- Why was your product rejected?
- How to improve your Content Score