QAlaunch

Bolt.new site not showing on Google: causes and fixes

A Bolt.new site often stays out of Google because the default React + Vite build sends an almost empty HTML file and fills it with JavaScript, the pages have no individual titles or descriptions, there is no sitemap, and the site still lives on a .bolt.host address. Find out whether your Bolt hosting plan pre-renders pages, add per-page metadata, generate sitemap.xml and robots.txt, move to a custom domain and submit it in Search Console.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

Searching for your business name finds nothing from your site. When you right-click and choose View Page Source, you see a short file with a single empty div and some script tags instead of your text. Link previews in social apps are blank or generic.

Why it happens

1. Content arrives only after JavaScript runs

Bolt generates React and Vite apps by default. The first HTML is nearly empty and the content appears when scripts run, which Google can usually handle with delay but many other crawlers and preview bots cannot.

2. Unclear pre-rendering on Bolt hosting

Bolt's August 2025 launch post promised automatic SEO pre-rendering on Bolt Cloud, while a September 2026 review describes pre-rendering as a paid "SEO Boosting" feature. Bolt's help center does not settle it, so check what your plan includes.

3. No per-page metadata or crawler files

Bolt's help center does not document meta tags, sitemaps or robots.txt as features it generates. Unless you prompted for them, every page may share one title and there may be no sitemap at all.

4. A temporary-looking address

A .bolt.host subdomain works, but a custom domain gives Google a stable home to rank and lets you verify it properly in Search Console.

How to fix it

  1. View the source of your homepage (Ctrl+U). If your headline text is not in there, crawlers that skip JavaScript see an empty page.
  2. Check your Bolt plan and hosting settings for pre-rendering or "SEO Boosting", and ask Bolt support whether it is active for your project, since public sources disagree.
  3. Ask Bolt to add a unique title, meta description, canonical URL and Open Graph tags to every page.
  4. Have it generate /sitemap.xml with absolute URLs on your custom domain and a robots.txt that allows crawling and names the sitemap.
  5. Connect a custom domain, verify it in Google Search Console, submit the sitemap and use URL Inspection > Request indexing on the main pages.
  6. For pure marketing pages that never change, consider plain static HTML pages, which need no rendering help at all.

Prompt to paste into Bolt.new

Add a unique title, meta description, canonical URL and Open Graph tags to every page, generate sitemap.xml and robots.txt for https://example.com, and make sure the main text of each page is present in the HTML that is served before JavaScript runs if the setup allows it. Do not change the design.

How to check it's fixed

  • View page source on the homepage and one inner page; the main text and a page-specific title should be in the raw HTML.
  • Open /robots.txt and /sitemap.xml on your domain; both should load.
  • In Search Console, URL Inspection > View crawled page should show your real content, not an empty shell.

What a QAlaunch scan shows for this

  • Missing title, meta description or canonical in the rendered homepage.
  • A noindex tag, or Open Graph tags that are absent.
  • Console errors that would leave crawlers with nothing to render.
  • It does not check Google's index itself; it shows whether the page gives Google what it needs.

See exactly what a full report contains in the sample report.

Frequently asked questions

Does Bolt.new pre-render pages for SEO?

Sources conflict. Bolt's 2025 Bolt Cloud announcement described automatic SEO pre-rendering, and a 2026 independent review describes it as a paid feature. Ask Bolt support what applies to your plan and confirm with View Source or Search Console's crawled page.

Can Google index a JavaScript app anyway?

Google can render JavaScript, but it does so later and less reliably than plain HTML, and many other search and AI crawlers do not run scripts at all. Content in the initial HTML is the safer bet.

Is a .bolt.host address bad for SEO?

It can be indexed, but you do not own it and it is harder to build trust on. Move to your own domain before you start promoting the site.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Bolt.new-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Bolt.new: all Bolt.new fixes · Bolt.new testing · 9 bugs every AI-built site ships with

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Bolt blog: Bolt Cloud launch · J.A. Watte: bolt.new SEO, AEO and GEO