Collins Dictionary named "vibe coding" the word of the year in 2025. It describes the practice of building software through natural language prompts with AI tools, telling the AI what you want and letting it generate the code. Tools like Lovable, Bolt.new, Replit, Base44, and Cursor have made it possible for anyone to build a professional website in hours.
But there's a problem that affects virtually every vibe-coded website: Google can't see the content.
The Architectural Problem
Almost every AI website builder defaults to the same technology stack: React + Vite, producing a client-side rendered (CSR) single-page application. This is the fastest and easiest way for AI to generate deployable code, but it creates a fundamental SEO problem.
In a CSR app, the server sends an empty HTML shell with a JavaScript bundle. The browser downloads and executes the JavaScript to render the content. But search engines, social media crawlers, and AI crawlers either can't execute JavaScript or do it unreliably.
Google's Own Warning
Google's John Mueller has personally flagged SEO issues on vibe-coded websites. The r/vibecoding subreddit (with 153,000+ members) is filled with posts asking "why doesn't my site show up on Google?" The answer is always the same: client-side rendering.
Every Major AI Builder Is Affected
- Lovable: React + Vite CSR, .lovable.app hosting
- Bolt.new: React + Vite CSR, optional SEO Boost (limited)
- Replit: React + Vite CSR, SSR conversion blocked
- Base44: CSR with proprietary routing, no SEO solution
- Cursor: Puts 'use client' on everything, breaks Next.js SSR
- Claude Artifacts: Pure client-side React components
- Tempo Labs: React + Vite CSR
The AI Search Dimension
The problem is worse than just Google. AI search engines like ChatGPT, Claude, and Perplexity are becoming major traffic sources. Their crawlers (GPTBot, ClaudeBot, PerplexityBot) execute zero JavaScript. An analysis of 500M+ GPTBot fetches found zero evidence of JavaScript execution. Your vibe-coded site is 100% invisible to AI search.
The Solution: Prerendering
You can't fix this with better prompts. The problem is architectural (CSR vs SSR) and requires an infrastructure-level solution. Prerendering works by running your JavaScript in a headless browser and serving the rendered HTML to bots. It's the most practical fix because it requires zero changes to your existing code.
PrimeHTML provides done-for-you prerendering for any vibe-coded website. We also include complete white-labeling. Get started →
