How to Fix Bolt.new SEO

Bolt.new lets you build full-stack web apps with AI prompts in minutes. The apps look great and work perfectly — but search engines and AI bots can't read them. If your Bolt-built site isn't showing up in Google, this guide explains why and how to fix it.

Why Bolt.new Apps Are Invisible to Search Engines

Bolt.new generates client-side React applications built with Vite. When a search engine crawler like Googlebot visits your site, it receives a minimal HTML shell:

There's no content, no headings, no text — just an empty container and a JavaScript bundle. Google has to execute that JavaScript to see your content, and it often fails or deprioritizes JavaScript-rendered pages. AI bots like ChatGPT (GPTBot), Claude (ClaudeBot), and Perplexity (PerplexityBot) don't execute JavaScript at all — they see a completely blank page.

Why You Can't Fix This in Bolt's Code

Unlike a traditional development environment where you could add server-side rendering (SSR) or static site generation (SSG), Bolt.new gives you a client-side React/Vite application. You can't modify the server configuration, add middleware, or change how the app is served. The code Bolt generates runs entirely in the browser.

This means the fix has to happen at the infrastructure level — outside your Bolt app.

The Fix: DNS-Level Pre-rendering

DNS-level pre-rendering works by intercepting requests from search engine and AI bots before they reach your Bolt app. When a bot visits your site, it receives a fully-rendered HTML snapshot of your page — complete with all your content, headings, meta tags, and structured data. Human visitors continue to get your normal Bolt application.

Setup takes under 2 minutes and requires zero code changes:

1. Add your domain to a pre-rendering service
2. Enter your Bolt app URL as the origin
3. Update your DNS records to point to the pre-rendering service

Bolt-Specific: Netlify DNS Considerations

Bolt.new deploys apps to Netlify by default. If you've connected a custom domain through Bolt/Netlify, you'll need to remove the custom domain from your Netlify site settings before pointing your DNS to a pre-rendering service. Otherwise, Netlify's DNS configuration will conflict with the pre-rendering proxy.

The process is straightforward: remove the custom domain from Netlify, then add your DNS records pointing to the pre-rendering service. Your Bolt app URL (the .netlify.app subdomain) becomes the origin that the pre-rendering service fetches from.

AI Bots Can't Read Bolt Apps Either

It's not just Google. Over 40 AI bots now crawl the web, including GPTBot (ChatGPT), ClaudeBot (Anthropic's Claude), PerplexityBot (Perplexity AI), and Google-Extended (Gemini). None of these bots execute JavaScript. If you want your Bolt-built site to be recommended by AI assistants or appear in AI-powered search results, pre-rendering is essential.

Going Beyond Indexing: AI SEO Optimization

Getting indexed is the foundation, but to actually rank well and earn AI citations, your Bolt site needs more:

• Optimized meta tags — AI-generated titles and descriptions that target your keywords
• Schema markup — Structured data (FAQ, Product, Organization) that search engines and AI systems use to understand your content
• Rank tracking — Monitor your positions for target keywords over time
• AEO optimization — Answer Engine Optimization to get cited by ChatGPT, Perplexity, and Google AI Overviews

These optimizations can be applied at the pre-rendering layer — injected into the HTML that bots receive — without modifying your Bolt source code.