Bolt.diy SEO
Your Bolt.diy App Is Invisible to Google
Bolt.diy is the open-source version of Bolt.new -- it lets you prompt, run, edit, and deploy full-stack web apps using any LLM. The catch? Apps built with Bolt.diy typically render on the client side. When Googlebot visits, it sees a blank HTML shell instead of your actual content.
If you have deployed your Bolt.diy project to Railway, Cloudflare Pages, a VPS, or any other host, chances are search engines cannot see your content.
What RndrKit Does
RndrKit intercepts search engine traffic and renders your pages in a headless browser before sending the HTML back to the crawler. Human visitors go straight to your app as usual. Google gets your full page content, meta tags, and structured data.
Setup
Step 1: Find Your App's Origin URL
Your origin URL depends on where you deployed your Bolt.diy project:
| Hosting Provider | Origin URL Format |
|---|---|
| Railway | your-app.up.railway.app |
| Cloudflare Pages | your-app.pages.dev |
| Render | your-app.onrender.com |
| VPS / Self-hosted | Your server's IP or hostname |
If you deployed to a platform that assigns a default URL (like Railway or Render), that URL is your origin. If you are self-hosting on a VPS, you can use the server's IP address or a subdomain you control.
Step 2: Sign Up for RndrKit
Create your account at rndrkit.io.
Step 3: Add Your Domain
Click Add Domain in the dashboard:
| Field | Example | Description |
|---|---|---|
| Custom Domain | www.example.com | The domain your visitors will use |
| Origin URL | your-app.up.railway.app | Where your Bolt.diy app is hosted |
Step 4: Configure DNS
Create a CNAME record at your DNS provider:
| Type | Name | Value | TTL |
|---|---|---|---|
| CNAME | www | cname.rndrkit.io | Auto |
If you are using Cloudflare, set the proxy status to DNS only (gray cloud).
See DNS Configuration for provider-specific instructions.
Step 5: Verify
# Bot request -- should return fully rendered HTML
curl -s -A "Googlebot/2.1" "https://www.example.com/" | head -50
# Human request -- should return your app shell
curl -s "https://www.example.com/" | head -50
Platform-Specific Notes
Hosting Provider Matters
If you deployed to a platform with custom domain support (Railway, Render, Cloudflare Pages), make sure to remove your custom domain from that platform before pointing DNS to RndrKit. Otherwise the hosting platform will intercept requests.
Self-Hosted on a VPS
If you are running Bolt.diy on your own server, your origin URL is your server's IP address or a subdomain. Make sure:
- Your app is accessible over HTTPS on the origin
- Port 443 is open and serving your app
- The origin responds to requests without requiring specific Host headers (or configure your server to accept the custom domain)
Status: Should Work
Bolt.diy is an open-source project and the apps it generates vary in structure. RndrKit works with any client-side rendered app, so it should work with Bolt.diy projects out of the box. If you run into rendering issues with a specific app, check troubleshooting or contact support.
SEO Quick Wins
Once pre-rendering is active, make sure your Bolt.diy app includes:
- Title tags on every page
- Meta descriptions for search result snippets
- Open Graph tags for social media sharing
- Semantic HTML -- use headings (
h1,h2, etc.) to structure content - Internal links between pages so crawlers can discover your content
Verify It Works
curl -s -A "Googlebot/2.1" "https://www.example.com/" | head -100
You should see your rendered page content in the HTML response. If the output is empty or shows an error, check troubleshooting.
Next Steps
- Analytics -- See which bots are visiting your site
- Cache Warming -- Pre-render key pages for faster bot responses
- SEO Audit -- Find SEO issues on your pages
- Quick Start Guide -- Full setup walkthrough