BlackFriday

50% offon all annual plans

00d00h00m00s
Explore plans
Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Bolt logo

Get client feedback on your published Bolt app

Paste the public bolt.host URL or custom domain, send one review link, and collect contextual comments on the website your visitors will actually open.

https://

Use a public published site for browser review. Bolt project-share links and private published sites have separate account and access rules.

Knauf
Radancy
Frontier
City of Boroondara
Berlin Heart
GVBOCES
Bville
Frost Collective
Mediapilote
Medwiki
Musaffa
Sharp Guys Web Design

Loved by1,250+Agenciesand companies in 100+ countries

Bolt project sharing and published-site review are different workflows.

Bolt provides project collaboration and built-in hosting. The right review URL depends on whether stakeholders need the project workspace or the deployed website.

Four documented boundaries matter before you share a review:

  1. Free Bolt sites publish publicly.

    Bolt publishes every Free-plan site as public. Paid plans can publish a site publicly or privately for the team and invited viewers.

  2. Published changes are controlled.

    After publishing, project changes aren't automatically applied to the live site. The owner or a Co-owner uses Publish for the first release and Update for later changes.

  3. Project sharing grants workspace roles.

    Bolt project collaboration uses Viewer, Editor and Co-owner roles. Collaborators must have a Bolt account and sign in; this link opens the project, preview and code rather than only the visitor-facing site.

  4. Custom domains are public-only.

    Bolt says a site with a custom domain can only be published publicly. The domain must be disconnected before that site can be published privately.

BugSmash keeps feedback on the rendered release:
share the public browser URL, keep Bolt project permissions with the build team, and use the Feedback Widget when the deployed experience is gated or stateful.

How it works

Three steps to a reviewed Bolt app

1

Publish the website

Use Bolt hosting to create the bolt.host site, or attach a custom domain on a paid plan. Confirm the release has the visibility intended for the review.

2

Send one BugSmash link

Paste the public visitor-facing URL into BugSmash and share the resulting review link instead of granting access to the Bolt project.

3

Update and verify the release

Resolve the comments in Bolt, use Update to publish the changes, and review the same live URL again before approval.

Review the published Bolt app, not the project workspace

Comment on the public release

Attach feedback to the rendered bolt.host site or custom domain visitors will use.

Keep project roles private

External reviewers do not need Viewer, Editor or Co-owner access when the published site is public.

Check responsive layouts

Review desktop, tablet and mobile presentation from the same browser-accessible release.

Capture technical context

Keep the page URL, browser, operating system, viewport and screenshot with each website comment.

Review deliberate releases

Bolt leaves live content unchanged until an owner or Co-owner publishes or updates the site, so each round can target an intentional release.

Use the widget for gated states

Install the BugSmash Feedback Widget when feedback must be collected inside an authorized or stateful app experience.

Which Bolt link should I review?

Use the deployed visitor-facing site whenever possible. Project sharing controls access to the Bolt workspace, while publishing controls access to the website.

Your URLReview by URLWhat to do
Public site on a bolt.host address WorksPaste the published URL and start the review.
Public site on a custom domain WorksPaste the connected domain after the latest release is published.
Private Bolt-hosted site Access-dependentOnly team members and invited viewers can open it. Verify the reviewer can complete Bolt access inside the review, or use a public review release or the widget.
Bolt project-share link Use the published siteThe project link exposes collaboration access, preview and code according to the assigned role. Use the visitor-facing deployment for website review.
Unpublished project preview Not a public releasePublish an appropriate site before collecting external browser feedback.
App behind application login or SSO Use the widgetA pasted URL does not bypass application login or SSO. Install the Feedback Widget inside the authorized app experience.

Installing the Feedback Widget on a Bolt app

Add the BugSmash script to the deployed app when reviewers must comment inside a logged-in, role-specific or stateful flow. Bolt project roles and private-site invitations remain separate from the frontend feedback workflow.

Turn Bolt app feedback into trackable work

Route an actionable website comment to the delivery team with its page, selected location, screenshot, browser, operating system and viewport context preserved.

Context stays attached from comment to completion.

Send to your workflow

The destination changes. The context does not.

Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks

The Bolt app is one deliverable. Review the complete launch together.

Keep the published app beside product PDFs, videos, images, presentations and other launch assets, with feedback and approval in one project.

  • Website
  • HTML
  • Widget
  • Video
  • Audio
  • Image
  • PDF
  • PPT
  • Doc
  • Email
  • 3D Model
  • CAD
  • Mobile App
  • Canvas

Bolt app feedback, answered

Which Bolt URL should I send for review?

Send the public bolt.host address or connected custom domain that opens the visitor-facing release. A Bolt project-share link opens a collaboration surface with role-based access.

Ship Bolt apps without chasing feedback

Paste the public Bolt site URL and send a focused review link without opening the project workspace to every reviewer.

BugSmash website review interface with comment controls