Bolt.new builds beautiful React apps in minutes — but they ship with almost no SEO. These are the five problems we find on nearly every Bolt site, and the exact prompts to fix them.
Each one comes with a prompt you can paste straight into Bolt to fix it.
Bolt projects are usually Vite + React single-page apps. If your titles are set from React code after the page loads, Google often sees the default "Vite + React" title instead of yours — and your search listing looks broken.
The fix: Put your real title and meta description in the served HTML (index.html head), not only in React state.
Open index.html and make sure the <head> contains a real, server-served <title> (max 60 characters, describing what this site does) and a <meta name="description"> (max 155 characters). These must exist in the HTML file itself, not be injected by JavaScript after load. Use the site's actual purpose and language for the text.
Bolt doesn’t generate a sitemap for you. With no sitemap and few external links, Google may only ever find your homepage.
The fix: Generate a sitemap.xml listing every page, serve it at /sitemap.xml, and reference it from robots.txt.
Add a sitemap.xml to the public folder listing the full URL of every page/route on this site, and a robots.txt containing "User-agent: *", "Allow: /" and "Sitemap: https://MYDOMAIN/sitemap.xml" (replace MYDOMAIN with the real domain). Make sure both files are served at the site root after deploy.
AI builders love single-page sites: all your offers, features and topics on one URL. Google gives each page one title and one shot — a page that targets ten searches usually wins none.
The fix: Give each important topic its own route with its own title, heading and content.
Split this single-page site into separate routes: keep the homepage focused on the main offer, and create a dedicated page for each distinct topic/service currently crammed onto the homepage. Each new page needs its own served <title>, meta description, one clear <h1>, and genuinely useful content. Add links to each new page from the homepage navigation.
If navigation happens only in JavaScript (or routes 404 when loaded directly), Google can’t reach your inner pages. Netlify-hosted SPAs need a redirect rule — and each route still serves the same head tags.
The fix: Make every route load directly (SPA redirect rule) and consider pre-rendering so each route serves its own tags.
Ensure every route on this site can be loaded directly by URL (add the SPA fallback redirect for the host, e.g. Netlify _redirects with "/* /index.html 200"). Then add pre-rendering or per-route head management so each route serves its own <title> and meta description in the HTML response.
Even when Bolt sites have several pages, they rarely link to each other in the body content. Internal links are how Google understands which pages matter.
The fix: Link related pages to each other inside the content, with descriptive anchor text.
Go through each page of this site and add 1-3 in-body links to related pages (not just the nav), using descriptive anchor text that says what the target page is about. Every important page should have at least 2-3 other pages linking to it.
Run the free scan — it checks your Bolt site's foundations in 15 seconds and tells you what to fix first. Then connect Search Console for the full picture: which searches you're almost winning, and exactly what's holding you back.
No. Bolt builds fast, working apps, but SEO basics — server-served titles, meta descriptions, sitemap, robots.txt, per-route tags — are your responsibility. The good news: you can fix all of it by prompting Bolt, and this guide gives you the prompts.
Most often: the site is new and has no sitemap, so Google hasn’t discovered it; or the pages are client-rendered so Google sees an empty shell. Submit a sitemap in Google Search Console and make sure your titles exist in the served HTML.
Google can render JavaScript, but it’s slower, less reliable, and often skipped for small new sites. Server-served titles and pre-rendered content remove the risk entirely — which is why every fix in this guide pushes that way.
View your page source (right-click → View Page Source): what you see there is what Google reliably gets. If your title and content aren’t in the raw HTML, that’s your problem. OptiSearch’s free scanner checks this automatically.