Bolt SEO after you publish: getting found on Google and in AI answers

Short answer: after publishing a Bolt app, connect a custom domain (a Pro feature) and turn on SEO Boost under project settings, Domains and Hosting, so crawlers get pre-rendered HTML instead of an empty shell. Then ask Bolt for a unique title and meta description per page, Open Graph tags, a sitemap and robots.txt, check in Google Search Console what Google renders, and give each main use case its own page with real text. AI assistants that search the web read the same pages, so the same work helps there.

Why Bolt apps can be invisible

Most Bolt projects are client-side apps: the HTML a crawler downloads is nearly empty, and JavaScript fills it in. Google can often render it, with a delay; many other crawlers, including AI ones, do not run JavaScript. Check it: on your live site, choose View page source. If your headline is not in the HTML, crawlers that do not run scripts cannot see it.

Step 1: custom domain and SEO Boost

Per Bolt's docs, custom domains are a Pro feature, and SEO Boost, which pre-renders each page into HTML for crawlers, is off by default and only appears for projects with a connected custom domain. Turn it on from the project settings (the gear icon, All project settings, Domains and Hosting). Then view the page source again from a crawler's view, or use Search Console's live test.

Step 2: titles, descriptions and previews

Prompt for Bolt: "Give every route a unique title under 60 characters and a meta description that says what the page offers and for whom. Add Open Graph and Twitter card tags with a share image, and a canonical URL on our custom domain."

Step 3: sitemap and robots.txt

Prompt: "Add sitemap.xml with absolute URLs for every public route on our custom domain, and robots.txt that allows crawlers on public pages and has a Sitemap line." Open both on the live domain. Check robots.txt does not block OAI-SearchBot; OpenAI's docs say sites that block it are not shown in ChatGPT search answers.

Step 4: Google Search Console

Verify your domain, submit the sitemap, inspect the home page with a live test and request indexing. New sites can take days to weeks to appear.

Step 5: content an answer can quote

One landing page with a slogan gives search engines and assistants little to work with. Add:

• A first paragraph that says what the app does, for whom and the price.
• A page per main use case, each with its own title.
• A pricing page in text and a short FAQ.
• Real text instead of words baked into images.

Step 6: watch for hosting pauses

Bolt's docs say free sites go offline when they hit monthly hosting limits, and Pro sites pause at your spending cap. A site that is offline when Google visits is a site Google cannot index. See Bolt app works in preview but not live for the rest of the live checks.

Where Persqo helps

You can do all of this in Bolt and Search Console. Persqo checks the live result:

• Paste the Persqo prompt into your Bolt project's chat and your app gets a Persqo admin page at /admin/persqo.
• An AI visitor tests the live app, checks what crawlers can read, and every finding comes with a fix prompt you paste into Bolt.
• One click: the Persqo fix runtime the prompt adds to your Vite build applies the home page title and description, business and FAQ schema, the viewport tag and llms.txt, each with Undo, live the next time you publish.
• With GitHub connected, Persqo opens a pull request for llms.txt and robots.txt; Bolt pulls in the change after you merge. Persqo never merges.
• A Persqo GEO scan asks AI engines your buyers' questions and shows whether they name you. The first scan is a one-time $5.

More on Persqo for Bolt.

Sources

• SEO for Bolt hosting, Bolt support, checked November 6, 2026
• Hosting plans, Bolt support, checked November 6, 2026
• Understand the JavaScript SEO basics, Google Search Central, checked November 6, 2026
• Overview of OpenAI crawlers, OpenAI docs, checked November 6, 2026

Last updated: November 6, 2026.

Questions people ask