Is Bolt.new SEO friendly?
Bring your published Bolt project. Check with one curl command whether bots see your text; if they don’t, connect a custom domain and turn on Bolt’s pre-rendering, or have Bolt render the public pages in code. Then make one domain primary, keep the site public, and write pages that answer buyers’ questions. You don’t have to leave Bolt or rebuild the app to do any of it.
The short answer
It can be. Bolt focuses on JavaScript web apps and supports any front-end framework that runs in the browser, with Node.js on the back end (Bolt Help, “Supported technologies”, read 15 Oct 2026). If Bolt built yours as a single-page app (look for vite and react in package.json), the HTML holds very little text until JavaScript runs, and AI crawlers don’t run it (Vercel, “The rise of the AI crawler”, December 2024, third-party study).
Bolt’s answer is pre-rendering. Its pricing page lists “SEO boosting” next to custom domain support on the Pro plan (Bolt pricing, read 15 Oct 2026), and the Bolt Cloud launch post of 14 August 2025 describes “automatic SEO pre-rendering”. We couldn’t confirm the current setup steps: the help article that described the setting now opens Bolt’s general hosting page. An earlier version placed the switch in project settings under Domains & Hosting and required a custom domain, so look there.
Where a Bolt site loses bots
| Cause | What you see | Fix |
|---|---|---|
| Text drawn by JavaScript | curl shows a few dozen words | SEO boosting on a custom domain, or render public pages in code |
| Site published as private | Bots get a login wall | Publish as public; Bolt says only public sites can be found by search engines |
| Hosting limit reached | The site stops displaying until the next billing cycle | Watch usage; paid plans can raise limits |
| Two addresses for one site | bolt.host and your domain both answer |
Primary domain plus aliases, and canonical tags |
| Missing pages return 200 | Every made-up URL shows the app | A real 404 for unknown public paths |
Sources for the Bolt rows: Bolt Help, “Publish your project” and hosting limits, read 15 Oct 2026.
Test it in one minute
An example; replace the domain. The second line asks as GPTBot, because pre-rendering services often answer bots differently from browsers:
URL=https://yoursite.com
echo "browser: $(curl -s $URL/ | sed 's/<[^>]*>/ /g' | wc -w) words"
echo "GPTBot: $(curl -s -A 'Mozilla/5.0 (compatible; GPTBot/1.2)' $URL/ \
| sed 's/<[^>]*>/ /g' | wc -w) words"
curl -s -o /dev/null -w '%{http_code}\n' $URL/no-such-page
What good looks like: hundreds of words on the GPTBot line, and 404 for the made-up page. Few words on both lines means bots see an empty shell.
Fixes on Bolt
- Connect a custom domain. Custom domains are for Pro users; you can buy one through Bolt or connect your own with a CNAME for
wwwand an ALIAS, ANAME or flattened CNAME for the root, both pointing atsite-dns.bolt.host(Bolt Help, “Connect a domain”, read 15 Oct 2026). - Turn on pre-rendering in project settings, then rerun the test. If the GPTBot line still shows few words, go to step 3.
- Or render the public pages in code. Ask Bolt for the smallest change that puts your text in the HTML: prerendering the public routes at build time, or a framework that renders on the server. Keep the logged-in screens as they are.
- Make one domain primary. Bolt says aliases forward visitors to the primary domain, “helping with SEO and avoiding duplicate content” (Bolt Help, “Domain aliases”, read 15 Oct 2026). Add a canonical tag with that domain on every page too.
- Return real 404s for unknown public paths, so Google doesn’t log soft 404s.
A prompt for Bolt’s chat, as an example:
Our public pages (/, /pricing, /faq and the pages in the footer) must
show their headings and paragraphs in the HTML before JavaScript runs.
Pick the smallest change for this project and explain it. Leave the
logged-in screens alone. Unknown public paths return 404. Accept when:
curl -s https://yoursite.com/pricing | sed 's/<[^>]*>/ /g' | wc -w
prints more than 200.
Then: pages an assistant can quote
Readable pages are the entry ticket. What gets a site named is a page whose first two sentences answer the question a buyer typed, and the same facts on every page. Write one page per buyer situation, then ask those questions every 14 days and note who is named: how to check. The other traps that hide vibe-coded sites are on this checklist.
What Katman does on a Bolt project
Connect GitHub from Bolt (it syncs on every change; only the project owner can manage the connection), clone the repo and open it in Cursor, Claude Code or another MCP client. katman_scan_code reports the Bolt signature, the framework and whether pages render on the server or only in the browser; katman_audit_site reads the live site as AI crawlers do; katman_prompt returns P2 with prerender options for your framework and an acceptance check. Katman doesn’t edit the project: Bolt or your coding tool makes the change, and Katman checks it. It can’t turn on Bolt’s settings for you, and nobody can promise an assistant will recommend you. Katman Pro is $99 a month for up to 3 sites, with fix prompts and page briefs uncapped. Or have us do it: Growth writes 30 pages a month for you. How Katman works.
Written by the Katman team, Rnify Limited. Bolt and Vercel pages read 15 October 2026.
Who this is not for
- Bolt projects published as private sites: they are meant to stay out of search.
- Mobile apps built with Bolt and Expo: app stores, not search engines, list those.
- Anyone looking for a switch that makes ChatGPT recommend a site: no setting does that.
Frequently asked questions
Does Bolt pre-render pages for search engines?
On paid plans, yes: Bolt’s pricing page lists SEO boosting next to custom domain support on Pro, and its Bolt Cloud launch post describes automatic SEO pre-rendering. Check with curl that your text is really in the HTML.
Why is my Bolt site fine in my browser but empty to ChatGPT?
Because your browser runs JavaScript and AI crawlers don’t. If Bolt built a single-page React app, the raw HTML can be almost empty until the scripts run.
Do private Bolt sites show up on Google?
No. Bolt says private sites aren’t generally accessible and search engines can’t find or list them. Public is the default when you publish.
What happens to my Bolt site if it hits the hosting limit?
Bolt says the site stops displaying publicly until usage resets at the start of the next billing cycle. Crawlers then get nothing either, so keep an eye on usage around launches.
Can I host a Bolt project somewhere other than Bolt?
Yes. With the project synced to GitHub, Bolt says you can publish with Bolt hosting, its Netlify integration or another service of your choice.