Get a Bolt site indexed: check which framework it uses, publish publicly on your own domain, add robots.txt and a sitemap, then verify in Search Console.
LLaunchScaler·Published ·7 min read
To get a Bolt-built site indexed, first check which framework your project uses, because Bolt supports any frontend JavaScript framework and a client-rendered Vite and React app shows crawlers an empty page until JavaScript runs. Then publish it publicly on your own domain rather than the bolt.host or netlify.app address, add robots.txt and sitemap.xml, prerender or server-render the public pages if needed, and confirm the result with URL Inspection in Search Console.
Bolt's hosting changed in 2025, so some advice online describes a setup your project may not use. The steps below follow Bolt's own documentation as read in September 2026.
What framework does your Bolt project use?
Open package.json and read the dependencies. Bolt's docs say it supports "any JavaScript framework that runs on the frontend," with Node.js for the backend, and they don't name a single default, so the answer is in your project rather than in Bolt's marketing. What you find decides whether crawlers can read your pages without running JavaScript.
What package.json contains
How pages render
What crawlers that skip JavaScript see
vite and react, no server framework
In the browser (a single-page app)
An almost empty
Questions, answered
What people ask about this
01
Are Bolt.new sites good for SEO?
They can be, depending on how the project renders and where it's published. Bolt supports any frontend JavaScript framework, so check your package.json: a client-rendered Vite and React app needs prerendering or server rendering for crawlers that don't run JavaScript, while a server-rendering framework already sends full HTML.
If you're not sure, ask Bolt in the chat what framework and rendering mode the project uses, then confirm it yourself with the curl test below. Google renders JavaScript in a deferred queue, so a single-page app can still reach Google, only later; OpenAI's, Anthropic's and Perplexity's crawlers don't run JavaScript at all, according to Vercel's measurements.
Where is your Bolt site published?
Bolt hosting is the default. Bolt says all new projects publish with Bolt hosting, introduced on August 14, 2025, to a free address ending in bolt.host, and custom domains need a paid plan. Netlify is an option you choose before first publishing a project; projects published to Netlify before Bolt hosting existed can stay there.
Three settings decide whether search engines can find it at all:
Visibility. In the Publish menu, a public site "can be found and listed in search results"; a private site, visible only to your team and invited users, cannot. Public is the default, but check it.
The domain. A site on yourapp.bolt.host can be crawled, but links and rankings build up on an address you don't own. Bolt gives the site a random bolt.host name on first publish, which you can rename afterwards, but a readable subdomain is still not your domain. Connect your own domain before you share the site widely.
Publishing. Bolt says changes in your project don't reach the live site until you publish again from the Publish menu, so an SEO fix made in the editor doesn't exist for Google until you republish.
How do you connect a custom domain on Bolt or Netlify?
Connect the domain, make it primary, and make every other address redirect to it. Bolt calls those other addresses domain aliases: in project settings under Domains & Hosting, click Add domain alias, and Bolt forwards alias visitors to your primary domain, which its docs say helps SEO and avoids duplicate content issues.
On Bolt hosting:
Click the gear icon, then All project settings, then Domains & Hosting.
Buy a domain through Bolt, or connect one you own and add the DNS records Bolt shows (an ALIAS record for aliases).
Wait for the green shield next to each domain, which Bolt uses to show the domain is connected with a working SSL certificate. Most connect within a few hours; Bolt says it can take up to 24.
Point every canonical tag and sitemap URL at the primary domain.
On Netlify:
Add your domain in Domain management and set it as primary. Netlify redirects between the apex and www automatically, whichever one you choose as primary.
Netlify's docs describe that automatic redirect only between the apex and www, and say it doesn't apply to other subdomains; they don't say your yoursite.netlify.app address redirects. Check with curl -sI https://yoursite.netlify.app: if it answers 200 rather than a redirect, add a domain-level rule to _redirects: https://yoursite.netlify.app/* https://www.yourdomain.com/:splat 301!.
Set canonical tags and sitemap URLs to the primary domain.
How do you add robots.txt and sitemap.xml to a Bolt project?
Create both as static files served from the site root. In a Vite project, files in the public/ folder are copied to the root of the build as-is, so public/robots.txt is served at /robots.txt. In a Next.js project, generate them from app/robots.ts and app/sitemap.ts instead.
Then check that the files are real. In a single-page app, a missing file often isn't a 404: the app's router answers /sitemap.xml with your homepage. curl -s https://www.yourdomain.com/sitemap.xml | head -3 should print XML, not HTML. Submit the sitemap in Search Console under Sitemaps once it does.
Does Bolt have built-in SEO tools?
It has two, both of which work through the chat rather than as a separate audit. Bolt's Prompt Library includes built-in prompts in an SEO category, which you open from the plus icon in the chatbox under Open Prompt Library. And Bolt maintains a set of curated skills, one of which is SEO/GEO; curated skills other than Skill Creator are off by default, so turn it on in your project before you ask Bolt for SEO changes.
Treat both as ways to get Bolt to write the fixes, not as proof they worked. A prompt can add a <title> to a component in a single-page app, and the tag will still appear only after JavaScript runs. After any SEO change, publish, then run the curl checks in the last section against the live URL.
What to ask Bolt for, in order:
"List the framework, rendering mode and hosting target this project uses."
"Add public/robots.txt and a public/sitemap.xml listing every public route on https://www.yourdomain.com."
"Give every public route its own title, meta description, canonical URL and Open Graph tags, and make sure they appear in the HTML served for that route, not only after JavaScript runs."
"Prerender the public routes at build time so each one is a separate HTML file."
How do you make a Vite and React Bolt app crawlable?
Put each public page's content and tags into the HTML the server sends, either by prerendering those routes at build time or by moving the public pages to a framework that renders on the server. Keep the signed-in parts of the app as they are; they don't need to rank.
web.dev defines prerendering as running a client-side app at build time to capture its initial state as static HTML, and recommends server or static rendering over a fully client-rendered approach. In practice:
Option
What changes
Good fit
Prerender the marketing routes
The build writes /, /pricing and /features as separate HTML files with their own titles and content
A small, fixed set of public pages
Move public pages to a server-rendering framework
Marketing pages live in a Next.js or similar project; the app stays a Vite SPA
A product with a separate app behind a sign-in
Rebuild the project on a server-rendering framework
Every page renders on the server
Content-heavy sites: blogs, directories, docs
Leave it client-rendered
Google indexes after rendering; most AI crawlers and link-preview bots see little
Internal tools that don't need search traffic
You can ask Bolt to make these changes, but verify the result with curl rather than trusting the chat summary. The client-side rendering SEO guide explains what each crawler sees, and the Lovable SEO guide shows how another builder solved the same problem with server rendering.
How do you verify the fix?
Test the raw HTML first, then Google's view. The raw HTML tells you what crawlers that skip JavaScript receive; URL Inspection tells you what Google renders.
curl -s https://www.yourdomain.com/pricing | grep -i "your pricing headline" should print a match.
curl -s https://www.yourdomain.com/pricing | grep -i "<title>" should print the pricing page's own title, not the homepage's.
curl -sI https://www.yourdomain.com | grep -i x-robots-tag should print nothing.
In Search Console, inspect the URL, click Test live URL, then View tested page. The Screenshot tab shows the page as Google's inspection tool rendered it; a blank or half-built screenshot means JavaScript content failed for Google too.
If the live test looks right, click Request indexing for your most important pages.
The same checks apply to any AI-built project; the AI-built app indexing guide covers Lovable, v0 and Cursor alongside Bolt.
To run these checks against your published Bolt site at once, run the free scan on LaunchScaler. It needs only your URL and no account, and its free checks read your robots.txt, sitemap, noindex directives, titles, descriptions and canonicals from the HTML as served, and compare the raw page with a real browser render to flag content that only appears after JavaScript, among 156 checks across 6 of its 7 categories.
02
Why isn't my Bolt site showing on Google?
Common causes are a site published as private, a site still on its bolt.host or netlify.app address, no sitemap or robots.txt, content that only appears after JavaScript runs, and the same title on every page. Check each, then request indexing in Search Console.
03
Can I use a custom domain with Bolt?
Yes. Bolt hosting publishes to a free bolt.host address, and custom domains need a paid plan. Add your domain in project settings under Domains & Hosting, make it primary, and add any other domains as aliases, which forward visitors to the primary.
04
Does Bolt host on Netlify?
Not by default any more. Bolt says new projects publish with Bolt hosting, introduced on August 14, 2025, and that you can choose Netlify instead for a project you have not yet published to Bolt hosting. Projects published to Netlify before then can stay there.
05
How do I check what Google sees on my Bolt site?
In Search Console, use URL Inspection on the live URL, click Test live URL, then View tested page. The screenshot shows how Google's inspection tool rendered the page, which tells you whether JavaScript-built content made it into Google's view.
Consent Mode v2 sends ad_storage, analytics_storage, ad_user_data and ad_personalization. Set all four to denied before tags load, then update on consent.
